The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Use two separate MCP connections: a browser server such as Microsoft Playwright MCP to inspect and capture a page, and a WordPress MCP connection to access authorized site capabilities. A screenshot shows how a page looks; it does not give an AI agent permission to read or change WordPress content. Connect both in an MCP-compatible client when your workflow needs both kinds of evidence and access.
What a website screenshot MCP server can—and cannot—do
Microsoft describes Playwright MCP as a browser automation server. Its tools include browser_take_screenshot for visual capture and browser_snapshot for an accessibility-oriented view of page structure and controls. The screenshot is evidence of a rendered page state; it is not a WordPress login, content editor, or write permission.
As an Amazon Associate I earn from qualifying purchases.
WordPress access is a separate capability. WordPress.com provides a hosted MCP endpoint, while the WordPress MCP Adapter can expose registered WordPress Abilities on a self-hosted site. An agent can use a browser server and a WordPress server in the same workflow only if its MCP client is configured and authorized for both. The cited documentation describes these components separately; it does not establish a single bundled integration or prove a particular end-to-end connection.
Choose visual evidence or structured page information
| Need | Use | Why |
|---|---|---|
| Check layout, styling, image placement, or a visual defect | Screenshot | It records the page’s rendered appearance at the time of capture. |
| Understand text, labels, controls, or interactive elements | Accessibility snapshot | Playwright MCP documentation recommends snapshots over screenshots for many interaction tasks. |
These outputs answer different questions. A screenshot can help diagnose a visual issue, but it may not reliably communicate control names or page structure. A snapshot can expose structured interaction information, but it is not a pixel-level record of styling.
Choose how the AI agent connects to WordPress
WordPress.com hosted MCP
WordPress.com documents its MCP endpoint as https://public-api.wordpress.com/wpcom/v2/mcp/v1 and uses OAuth 2.1 authorization. Authorization takes place in a browser, and connected apps can be managed in account settings. As documented on October 7, 2026, all paid plans have access; a free site has access during its first 30 days. A self-hosted WordPress site connected through Jetpack needs Jetpack AI or Jetpack Complete. These eligibility rules can change, so check the current WordPress.com MCP documentation before setting up access.
Self-hosted WordPress MCP Adapter
The WordPress MCP Adapter is a different route: it maps registered WordPress Abilities to MCP tools, resources, or prompts, depending on their configuration. The adapter describes STDIO and HTTP transport choices and default adapter tools. What an agent can do depends on the abilities registered and exposed by the site; installing an adapter does not automatically grant every WordPress capability.
Do not confuse the Plugin Directory server with site access
WordPress.org’s MCP service is for preparing, validating, and submitting plugins to the Plugin Directory, not for general operation of any WordPress site. WordPress.org’s Plugin Handbook says, “This is a tool to assist your workflow, not a replacement for the review process.” Plugin submissions still go through review. See the WordPress.org MCP server documentation for its scope.
Set up a two-server workflow
- Decide what the agent needs. For a rendering issue, configure browser screenshot capture. For page structure or interactive controls, prefer an accessibility snapshot when available. Use WordPress MCP only if the task also needs authorized site data or an action.
- Pick the WordPress route. Use WordPress.com’s hosted endpoint if your account and site are eligible, or configure the MCP Adapter for the registered abilities on a self-hosted site. For a Jetpack-connected site, verify plan eligibility in the current WordPress.com documentation.
- Configure each server in the MCP client. Follow the client-specific instructions rather than assuming one server’s setup format applies to another. Playwright’s installation guide explains adding its server to a client; WordPress.com authorization uses browser-based OAuth 2.1.
- Ask for browser evidence. Have the agent navigate to the relevant public or authenticated page and capture a screenshot, or request a snapshot if the task is about content and controls. Make sure the browser session has the access the page requires.
- Use WordPress tools for site-side work. Ask the agent to use the separately authorized WordPress MCP connection for the specific content or action needed. Review proposed changes and the resulting page; do not treat the screenshot server as a CMS writer.
The exact client configuration, login sequence, and tools presented to the agent vary by client and server. Use each project’s current setup documentation and grant only the access needed for the task.
Example: inspect a page, then make a WordPress change
For example, an agent might inspect a public landing page with Playwright MCP, capture its appearance, and report that a heading is clipped. If you then want the heading changed, the agent needs a separate WordPress MCP tool that is authorized and exposes the relevant site capability. Ask it to describe the proposed change, make only the requested edit, and inspect the page again in the browser. This is a workflow pattern based on the separately documented capabilities, not a claim that a specific client/server combination has been tested here.
Keep the task boundaries explicit: ask the browser server to gather page evidence, and ask the WordPress connection to perform only authorized site operations. If the agent cannot access a needed WordPress ability, a screenshot does not fill that gap.
Or skip the browser setup: use ScreenshotNeo
If your immediate need is a website screenshot rather than interactive browser automation, ScreenshotNeo offers a screenshot API and MCP server for developers. One GET request can return an image or PDF, and the API accepts common parameter names used by other screenshot APIs. The cURL example below saves a WebP screenshot; see the ScreenshotNeo API documentation for configuration and other output options.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchcurl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://wordpress.org -o shot.webpScreenshotNeo accepts cookie or consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, with response headers identifying the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf for AI agents using Claude, Cursor, or another MCP client. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots.
Sign up free for 1,000 screenshots a month—no card required.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshooting the workflow
- The agent can take a screenshot but cannot edit the site. A browser server provides browser capabilities, not WordPress permissions. Configure and authorize a separate WordPress MCP connection with the required ability.
- The WordPress server connects but lacks the operation you need. On a self-hosted site using the Adapter, inspect which WordPress Abilities are registered and exposed. The adapter does not make unavailable abilities available by itself.
- WordPress.com authorization or access fails. Recheck the OAuth flow, account connected-app settings, and current plan eligibility. Hosted service policies may change; use the current WordPress.com MCP documentation rather than relying on an old setup guide.
- A self-hosted Jetpack site is not eligible. The documentation checked October 7, 2026 says Jetpack AI or Jetpack Complete is required for self-hosted WordPress sites connected through Jetpack. Verify the current requirement for the specific account.
- The agent describes content but misses a visual problem. Ask for a screenshot at the relevant page state and viewport. Conversely, for controls or structured page information, ask for an accessibility snapshot where supported.
- You are trying to manage a WordPress site through the Plugin Directory server. That service is for plugin preparation and submission workflows, not general site administration. Choose WordPress.com MCP or a site-level MCP Adapter route instead.
Performance, reliability, and cost considerations
The cited documentation does not provide a benchmark comparing a local Playwright MCP server with WordPress.com’s hosted MCP endpoint, nor does it establish comparative reliability or speed. Browser capture and WordPress operations also depend on different factors: page load and browser state for the former, and authorization plus exposed WordPress capabilities for the latter.
For WordPress.com MCP, access depends on the account/site eligibility described above. For a self-hosted Adapter setup, the available tools depend on registered abilities and transport configuration. The cited sources do not establish a universal price for MCP use across clients or self-hosted deployments, so check the current terms for each service and any client you use.
Recommended Free Tools
Frequently Asked Questions
Can an AI agent inspect a WordPress page and then update it?
Yes, if its client has both a browser capture connection and a separately authorized WordPress MCP connection that exposes the needed site capability. A screenshot alone cannot authorize or perform the update.
Do I need WordPress.com, or can I use self-hosted WordPress?
Either route is documented: WordPress.com’s hosted MCP endpoint is plan-dependent, while the WordPress MCP Adapter can expose registered abilities on self-hosted sites. Jetpack-connected self-hosted sites have an additional documented eligibility requirement.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
