How to Connect an MCP Server to BetterDocs

This is a test doc created to verify the MCP connection between an AI client and BetterDocs.

Overview #

BetterDocs exposes an MCP (Model Context Protocol) server so AI clients can read and manage your documentation directly. The endpoint is:

https://agency17.ca/betterdocs/mcp

Connection steps #

Enable MCP in BetterDocs settings (enable_mcp must be true).
Choose a transport. BetterDocs speaks streamable HTTP, so your client should be configured with transport: http (or equivalent) pointing at the /betterdocs/mcp endpoint.
Authenticate. Two options are supported:
- OAuth — the server returns a sign-in link on first connection; the user opens it, logs into WordPress, and approves access. Best for interactive clients.
- Bearer token / API key — generated in the BetterDocs settings screen and passed as an Authorization: Bearer <token> header. Best when the client can’t complete an interactive OAuth flow.
If your client can’t send custom headers natively on a plain url-based entry, wrap the connection with the mcp-remote CLI helper so the header gets injected:

{
  "mcpServers": {
    "betterdocs": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://agency17.ca/betterdocs/mcp",
        "--header",
        "Authorization: Bearer YOUR_TOKEN_HERE"
      ]
    }
  }
}

Verify the connection by calling bd-get-status. A healthy response reports the BetterDocs and Pro versions, your connected user’s role and capabilities, and the list of available tools.

Confirmed working #

This doc was created via the MCP connection itself, using bd-create-doc, which confirms the round trip (auth → tool call → content write) is functioning end to end.