Connect your AI agent to WP Engine docs

The WP Engine docs MCP server lets an AI agent search and read WP Engine Product Documentation while it works. Answers come from the current docs, each with a link to the section it came from, rather than from what the model remembers.

It covers every product on this site, including Headless Platform, Managed Hosting and its API, Smart Search, AI, Local, and Advanced Custom Fields.

Server details

Setting	Value
URL	https://api.prd.sdp.wpesvc.net/docs-mcp/mcp
Transport	Streamable HTTP
Authentication	None

You don’t need a WP Engine account or an API key. The server is read-only: it can only read public documentation, and it can’t see or change your sites.

Claude Code

Run this once:

claude mcp add --transport http --scope user wpe-docs https://api.prd.sdp.wpesvc.net/docs-mcp/mcp

--scope user makes the server available in every project. Leave it out to add the server to the current project, for you only. Start a new session to pick it up, and run /mcp to check that it’s connected.

To share the server with everyone working in a repository, see Share with your team.

Claude and Claude Desktop

Connectors you add on claude.ai are also available in Claude Desktop.

1. Go to Customize > Connectors.
2. Select + Add, then Add custom connector.
3. Enter WP Engine docs as the name and https://api.prd.sdp.wpesvc.net/docs-mcp/mcp as the URL, then select Continue.
4. Under Authentication, choose No sign in, then select Add.

To use it in a chat, select + at the bottom left, choose Connectors, and turn on WP Engine docs.

On Team and Enterprise plans, an owner adds the connector under Organization settings > Connectors (Add > Custom > Web). Members then turn it on from Customize > Connectors.

See Claude’s guide to custom connectors for plan limits.

ChatGPT

1. Open ChatGPT Plugins.
2. Select +, then Add custom MCP server.
3. Enter WP Engine docs as the name and a short description.
4. Under Connection, choose Public endpoint and enter https://api.prd.sdp.wpesvc.net/docs-mcp/mcp.
5. Set authentication to none, review the warning, and select I understand and want to continue.
6. Select Create as a plugin.

To use it, start a new chat, type @, and choose WP Engine docs.

In Business and Enterprise workspaces, an admin may need to allow creating plugins with MCPs first.

Cursor

Add the docs server to Cursor, then confirm the install when Cursor asks.

Or add it by hand to ~/.cursor/mcp.json for every project. To add it to one project only, use .cursor/mcp.json in the project root instead. This command opens the file in Cursor, creating the folder if needed:

mkdir -p ~/.cursor && cursor ~/.cursor/mcp.json

If the file already has an mcpServers object, add the wpe-docs entry to it.

~/.cursor/mcp.json

{
  "mcpServers": {
    "wpe-docs": {
      "url": "https://api.prd.sdp.wpesvc.net/docs-mcp/mcp"
    }
  }
}

VS Code with GitHub Copilot

Run this to add the server to your VS Code user profile:

code --add-mcp '{"name":"wpe-docs","type":"http","url":"https://api.prd.sdp.wpesvc.net/docs-mcp/mcp"}'

To share it with everyone working in a repository, use a .mcp.json file, which Claude Code reads too. See Share with your team.

If your team only uses VS Code, you can use VS Code’s own .vscode/mcp.json instead. From the repository root, run:

mkdir -p .vscode && code .vscode/mcp.json

If the file already has a servers object, add the wpe-docs entry to it.

.vscode/mcp.json

{
  "servers": {
    "wpe-docs": {
      "type": "http",
      "url": "https://api.prd.sdp.wpesvc.net/docs-mcp/mcp"
    }
  }
}

This file uses servers as its top-level key, not mcpServers like .mcp.json, so rename the key if you copy entries between them.

You can also run MCP: Add Server from the Command Palette and choose HTTP. Use Copilot Chat in agent mode to call the tools.

Codex

Codex CLI and the Codex IDE extension share one configuration, so you only add the server once:

codex mcp add wpe-docs --url https://api.prd.sdp.wpesvc.net/docs-mcp/mcp

Or add it by hand to ~/.codex/config.toml, which this command opens in your default editor:

mkdir -p ~/.codex && ${EDITOR:-nano} ~/.codex/config.toml

~/.codex/config.toml

[mcp_servers.wpe-docs]
url = "https://api.prd.sdp.wpesvc.net/docs-mcp/mcp"

Gemini CLI

gemini mcp add --transport http --scope user wpe-docs https://api.prd.sdp.wpesvc.net/docs-mcp/mcp

Without --scope user, Gemini CLI adds the server to the current project only.

To edit settings by hand, open ~/.gemini/settings.json in your default editor:

mkdir -p ~/.gemini && ${EDITOR:-nano} ~/.gemini/settings.json

Use httpUrl, not url, which Gemini CLI uses for the older SSE transport. If the file already has an mcpServers object, add the wpe-docs entry to it.

~/.gemini/settings.json

{
  "mcpServers": {
    "wpe-docs": {
      "httpUrl": "https://api.prd.sdp.wpesvc.net/docs-mcp/mcp"
    }
  }
}

Share with your team

To give everyone working in a repository the docs server, commit a .mcp.json file to the repository root. Claude Code and VS Code with GitHub Copilot both read it.

In Claude Code, this command creates or updates the file for you:

claude mcp add --transport http --scope project wpe-docs https://api.prd.sdp.wpesvc.net/docs-mcp/mcp

Or create it by hand. From the repository root, run:

${EDITOR:-nano} .mcp.json

If the file already has an mcpServers object, add the wpe-docs entry to it. Keep "type": "http": Claude Code treats an entry without a type as a local server and reports an error.

.mcp.json

{
  "mcpServers": {
    "wpe-docs": {
      "type": "http",
      "url": "https://api.prd.sdp.wpesvc.net/docs-mcp/mcp"
    }
  }
}

The first time each teammate starts Claude Code in the repository, it asks them to approve the server.

The other clients don’t read .mcp.json. Each keeps project servers in its own file, so add the server to that file too if your team uses them:

Client	Project file	Setup
Cursor	.cursor/mcp.json	Cursor
Codex	.codex/config.toml, read only in trusted projects	Codex
Gemini CLI	.gemini/settings.json	Gemini CLI

Other clients

Any client that supports remote MCP servers over Streamable HTTP can connect with the server details above.

If your client only starts local (stdio) servers, connect through the mcp-remote bridge, which needs Node.js. Add a local server in your client’s settings and set the command it starts to:

npx -y mcp-remote https://api.prd.sdp.wpesvc.net/docs-mcp/mcp

Try it

Ask your agent a question about a WP Engine product. For example:

Using the WP Engine docs, how do I add custom fields to Smart Search results?

The agent searches the docs, answers from the most relevant sections, and links to its sources. If it answers without searching, name the server in your prompt, or select it first in clients that let you (@ in ChatGPT).

Available tools

Tool	What it does
search_docs	Searches the docs and returns the best-matching pages, each with an excerpt from its most relevant section and a link to that section. Can be limited to one product.
get_doc	Reads a page from a search result. Short pages come back whole. Long pages come back as an introduction and table of contents, so the agent can then ask for just the section it needs.

Your agent decides when to call these tools. You don’t need to call them yourself.