AI Client Setup

Copy-paste configurations for connecting AI assistants to your Statamic MCP endpoint. Replace your-site.test with your actual domain and <your-token> with the token created in the Control Panel.

Claude Desktop

Option A: OAuth Connectors (recommended)

1. Open Claude Desktop and go to Settings → Connectors.
2. Click Add custom connector.
3. Enter a name (e.g. "Statamic") and your MCP server URL: https://your-site.test/mcp/statamic
4. Click Add — Claude will start the OAuth flow automatically.
5. Approve access in your Statamic Control Panel.

Your server must be publicly accessible (use ngrok for local development).

Option B: Config file with mcp-remote bridge

Claude Desktop's config file only supports stdio transport. Use mcp-remote as a bridge to connect to the streamable HTTP endpoint.

Requires Node.js installed.

Config file location:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

{
    "mcpServers": {
        "statamic": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://your-site.test/mcp/statamic",
                "--header",
                "Authorization: Bearer <your-token>"
            ]
        }
    }
}

Restart Claude Desktop after editing the config file.

Note: The url-based config format does not work in Claude Desktop — it is only supported by Claude Code and other CLI-based clients.

Claude Code

Add to .mcp.json in your project root or ~/.claude.json for global access:

{
    "mcpServers": {
        "statamic": {
            "url": "https://your-site.test/mcp/statamic",
            "headers": {
                "Authorization": "Bearer <your-token>"
            }
        }
    }
}

Cursor

Add to .cursor/mcp.json in your project root:

{
    "mcpServers": {
        "statamic": {
            "url": "https://your-site.test/mcp/statamic",
            "headers": {
                "Authorization": "Bearer <your-token>"
            }
        }
    }
}

ChatGPT

Add to your ChatGPT MCP configuration:

{
    "mcpServers": {
        "statamic": {
            "url": "https://your-site.test/mcp/statamic",
            "headers": {
                "Authorization": "Bearer <your-token>"
            }
        }
    }
}

Windsurf

Add to .windsurf/mcp.json in your project root or via the Command Palette:

{
    "mcpServers": {
        "statamic": {
            "url": "https://your-site.test/mcp/statamic",
            "headers": {
                "Authorization": "Bearer <your-token>"
            }
        }
    }
}

Generic / Other MCP Clients

Any MCP-compatible client can connect using the streamable HTTP transport:

{
    "mcpServers": {
        "statamic": {
            "url": "https://your-site.test/mcp/statamic",
            "transport": "streamable-http",
            "headers": {
                "Authorization": "Bearer <your-token>",
                "Accept": "application/json"
            }
        }
    }
}

You can also test the endpoint directly with curl:

curl -X POST https://your-site.test/mcp/statamic \
  -H "Authorization: Bearer <your-token>" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"tools/list","id":1}'

Self-Signed Certificates (Laravel Herd / Valet)

If you use Laravel Herd or Laravel Valet with HTTPS enabled on your local site, Node.js will not trust the self-signed certificate by default. This affects any client that uses npx mcp-remote as a bridge (e.g. Claude Desktop Option B) and may also affect other Node.js-based MCP clients.

The fix is to tell Node.js where to find the certificate authority (CA) file by setting the NODE_EXTRA_CA_CERTS environment variable in your MCP config.

Laravel Herd (Windows)

{
    "mcpServers": {
        "statamic": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://your-site.test/mcp/statamic",
                "--header",
                "Authorization: Bearer <your-token>"
            ],
            "env": {
                "NODE_EXTRA_CA_CERTS": "C:\\Users\\<your-username>\\.config\\herd\\config\\valet\\CA\\LaravelValetCASelfSigned.crt"
            }
        }
    }
}

Laravel Herd (macOS)

{
    "mcpServers": {
        "statamic": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://your-site.test/mcp/statamic",
                "--header",
                "Authorization: Bearer <your-token>"
            ],
            "env": {
                "NODE_EXTRA_CA_CERTS": "/Users/<your-username>/Library/Application Support/Herd/config/valet/CA/LaravelValetCASelfSigned.crt"
            }
        }
    }
}

Laravel Valet (Linux)

{
    "mcpServers": {
        "statamic": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://your-site.test/mcp/statamic",
                "--header",
                "Authorization: Bearer <your-token>"
            ],
            "env": {
                "NODE_EXTRA_CA_CERTS": "/home/<your-username>/.config/valet/CA/LaravelValetCASelfSigned.crt"
            }
        }
    }
}

Tip: If you're unsure where the CA certificate is located, look for a file named LaravelValetCASelfSigned.crt in your Herd or Valet configuration directory. The NODE_EXTRA_CA_CERTS variable works with any self-signed CA — not just Herd/Valet.

Troubleshooting