Skip to content

Your EMCP guide

Answers from our docs

YOUR CHAT, YOUR CHOICE

Before we chat

MSR Builds processes your question and up to four recent messages on our server to answer from the EMCP docs. AI is optional and needs your separate permission.

The chat is kept in this page's memory, not saved as a conversation in our database or browser storage. Our hosting and security services process connection information, such as your IP address, to prevent abuse.

Cloudflare Turnstile checks your browser and connection to prevent automated abuse when you send a question. No login is required.

Please leave out personal, sensitive or confidential information, passwords and API keys.

You can withdraw consent and clear this page's chat at any time. This cannot undo a request already sent or erase provider/security records.

Chat privacy, retention & your rights ↗ · Privacy contact

Starting chat consents to this processing. You can browse our docs without using the chat.

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.

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.

  1. Open VS Code’s Command Palette and run MCP: Add Server.
  2. Choose HTTP, paste the copied endpoint and enter a unique server name.
  3. Choose the user or workspace target offered by your current agent session. Let the guided flow create its configuration file.
  4. 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.

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.

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.