VS Code
Use VS Code’s built-in MCP setup with an agent that supports remote servers. The official VS Code guide describes the current configuration targets. The Claude Code extension uses its own setup.
Prepare WordPress
Section titled “Prepare WordPress”Open EMCP Tools → Connection → MCP. Check Server status and copy its endpoint. There is no VS Code card in the four-step wizard.
For browser sign-in, use an HTTPS site and enable OAuth sign-in in Advanced settings, then save. The approving WordPress user must be an administrator. See OAuth.
Add the connection
Section titled “Add the connection”- Open VS Code’s Command Palette and run MCP: Add Server.
- Choose HTTP, paste the copied endpoint and enter a unique server name.
- Choose the user or workspace target offered by your current agent session. Let the guided flow create its configuration file.
- Start the server and complete WordPress browser approval.
Do not paste the old extension-specific mcp.servers example into settings.json for this native flow. Configuration formats vary by agent and scope; preserve existing server entries.
Verify
Section titled “Verify”Run MCP: List Servers, inspect the connection, and enable its needed tools in the chat tool picker. Ask:
Identify the connected WordPress site URL and list accessible pages with titles, IDs and status. Do not change anything.
Compare the returned site and records with WordPress. A saved configuration alone is not a successful connection. If it fails, inspect server output and follow missing-tool diagnosis.
End access
Section titled “End access”Use Connection → Connected apps in WordPress to sign out the OAuth app. Removing its registration is a separate action. Application-password connections instead use the password revocation controls under Users → Profile.
