start•Last updated: 2026-09-02

AI Client Setup

Step-by-step configuration snippets for Claude Desktop, Claude Code CLI, Cursor IDE, Codex CLI, and custom agents.

Supported Clients

More MCP implements the standard Model Context Protocol specification (2025-11-25). It works with any client that speaks JSON-RPC 2.0 over Streamable HTTP or through an MCP bridge.

1. Claude Desktop

To connect Claude Desktop on macOS or Windows:

1. Open your Claude Desktop settings file:
   • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
   • Windows: %APPDATA%\Claude\claude_desktop_config.json
2. Add the server entry:

{
  "mcpServers": {
    "mordenhost-wp": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-fetch",
        "https://yourdomain.com/wp-json/more-mcp/v1/mcp"
      ],
      "env": {
        "HTTP_HEADER_MMCP_KEY": "YOUR_API_KEY"
      }
    }
  }
}

Restart Claude Desktop. You will see 107+ tools loaded under the integration menu.

2. Claude Code (CLI)

Claude Code supports HTTP MCP servers natively:

Run this command in your project directory or terminal:

claude mcp add wordpress https://yourdomain.com/wp-json/more-mcp/v1/mcp --header "MMCP-Key: YOUR_API_KEY"

Or add it to your .claude/settings.json project configuration:

{
  "mcpServers": {
    "wordpress": {
      "url": "https://yourdomain.com/wp-json/more-mcp/v1/mcp",
      "headers": {
        "MMCP-Key": "YOUR_API_KEY"
      }
    }
  }
}

Verify the tools are visible:

claude mcp list

3. Cursor IDE

In Cursor (Settings -> Features -> MCP Servers):

1. Click + Add New MCP Server.
2. Name: wordpress
3. Type: command
4. Command:

   npx -y @modelcontextprotocol/server-fetch https://yourdomain.com/wp-json/more-mcp/v1/mcp

5. Pass your authentication key via the environment variable configuration or within the header flags.

Cursor Composer and Chat can now create files, inspect theme structures, and manage posts directly.

4. Codex CLI

OpenAI Codex CLI reads its MCP servers from ~/.codex/config.toml rather than a JSON file. Add one [mcp_servers.<name>] table per server:

[mcp_servers.wordpress]
command = "npx"
args = [
  "-y",
  "@modelcontextprotocol/server-fetch",
  "https://yourdomain.com/wp-json/more-mcp/v1/mcp",
]

[mcp_servers.wordpress.env]
HTTP_HEADER_MMCP_KEY = "YOUR_API_KEY"

Restart Codex afterwards and run /mcp inside the session to confirm the wordpress server is listed and its tools have loaded.

Keep the key in the env table rather than inlining it into args. Values passed as arguments show up in the process list, where any other local user can read them.

5. Custom Python / Node.js Agents

Connecting programmatically using the official @modelcontextprotocol/sdk in TypeScript:

import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { SSEClientTransport } from "@modelcontextprotocol/sdk/client/sse.js";

const transport = new SSEClientTransport(
  new URL("https://yourdomain.com/wp-json/more-mcp/v1/mcp"),
  {
    eventSourceInit: {
      headers: {
        "MMCP-Key": "YOUR_API_KEY"
      }
    }
  }
);

const client = new Client({ name: "my-agent", version: "1.0.0" });
await client.connect(transport);

const tools = await client.listTools();
console.log(`Connected to WordPress! Available tools: ${tools.tools.length}`);