Claude WordPress MCP Setup
Claude supports custom remote MCP connectors. Studio now provides an exact callback allowlist for a separate Claude connection; this release still needs a live Claude trial.
Set up the connection
- Install Studio and enable direct mode on an HTTPS WordPress site.
- Add https://claude.ai/api/mcp/auth_callback to Studio’s additional client callbacks.
- In Claude’s custom connector settings, enter the MCP URL shown by Studio.
- Complete OAuth while signed into WordPress as an administrator.
- Call site_status and wordpress_read against a known draft before enabling changes.
Reference: Claude’s official remote connector guide. Confirm connector availability for your account.
What can Claude do through Studio?
The connection exposes site identity, REST route discovery, reads and permission-controlled requests. The installed REST APIs define what plugin-specific tasks are available. Studio does not include arbitrary PHP execution or a dedicated theme-file editor.
Keep ChatGPT and Claude grants separate. If the OAuth screen names another bridge or domain, cancel it and select the intended Studio connection.
Before connecting Claude to WordPress
Direct answer: Claude can use a compatible remote MCP connector to request WordPress operations through WPBridge Studio, subject to authorization and the WordPress user’s permissions. The steps below are a configuration guide, not a claim that this exact Studio–Claude connection has completed a live end-to-end trial.
- Use an HTTPS WordPress site with the Studio companion installed and direct mode enabled, or use a separately configured hosted Studio workspace.
- Have access to Claude’s custom connector feature and confirm its current availability in your account.
- Copy the MCP URL shown by the particular Studio mode you selected; do not interchange the direct and hosted URLs.
- Choose a WordPress identity with only the permissions needed for your workflow, where feasible.
Configure a custom remote connector in Claude
- In Claude, open the connector management interface and add a custom remote MCP connection.
- Name it clearly, such as “WPBridge Studio — Editorial Site,” so that it is not confused with another WordPress connection.
- Paste the exact HTTPS MCP endpoint supplied by the Studio setup screen. Use the direct site’s endpoint only when direct mode is enabled.
- Review the detected OAuth options, consent details and connector identity. For direct WordPress mode, use the supported callback allowlist detailed above. Do not insert an arbitrary wildcard redirect.
- After authorization, request
site_status, confirm the correct site address, then run a read-only request such aswordpress_readon/wp/v2/users/me. - Keep changes disabled until the returned site identity and user permissions match the intended target.
Claude’s interface and eligibility can change. See the current official connector instructions.
What successful verification looks like
| Test | Expected evidence |
|---|---|
| Connector authorization | Claude lists the intended remote connector and its available tools. |
| Site identity | site_status returns the actual authorized WordPress URL. |
| WordPress identity | /wp/v2/users/me returns a user ID consistent with the configured connection. |
| Editorial read | A known page or draft is returned with its correct ID, title and status. |
| Content change | Only when explicitly enabled: a disposable staging draft is saved and read back. |
These are acceptance criteria, not recorded test results for the Claude client. If they fail, follow the troubleshooting sequence.
Claude and WordPress connector questions
Does connecting Claude give it full WordPress administrator access?
No. REST requests are checked against the authorized WordPress user and Studio’s access settings. Limit the selected user’s capabilities whenever practical; see the security model.
Can Claude edit plugin settings through Studio?
Only if the installed plugin exposes a supported REST route and the authenticated user may call it. A WordPress dashboard screen alone is not evidence of remote edit support. See plugin compatibility.
Is a live Claude integration guaranteed?
No. This page documents a supported client-side connection approach while an end-to-end Studio–Claude trial remains pending. Client plans, security policies and OAuth behavior may affect availability.