DocsMint

Remote (streamable-http)

https://docsmint.com/mcp Requires auth (checked 2026-11-09)

Claude Code:

claude mcp add --transport http docsmint https://docsmint.com/mcp --header "Authorization: <YOUR_VALUE>"

Or add to your MCP client config:

{
  "mcpServers": {
    "docsmint": {
      "url": "https://docsmint.com/mcp",
      "headers": {
        "Authorization": "<YOUR_VALUE>"
      }
    }
  }
}

• Authorization required secret — DocsMint Cloud remote at https://docsmint.com/mcp; no self-hosted server is required. Follow https://docsmint.com/mcp/connect?source=mcp_registry for the currently supported OAuth discovery and client-connection methods. Browser consent binds access tokens to a workspace, optional category, and requested scopes. API-key clients can use Authorization: Bearer <key> with a workspace-bound or category-scoped credential created in the authenticated browser UI. Credential management requires a browser session. For self-hosting, use the stdio package with your own API and API key; it does not install the Cloud authorization server.
• X-Docsmint-Workspace — Canonical workspace slug. Bound workspace keys may omit this header.

Package (npm 2.1.5)

npx -y @hiai-gg/[email protected]

Or add to your MCP client config:

{
  "mcpServers": {
    "docsmint": {
      "command": "npx",
      "args": [
        "-y",
        "@hiai-gg/[email protected]"
      ],
      "env": {
        "HIAI_DOCS_API_KEY": "<YOUR_VALUE>"
      }
    }
  }
}

• HIAI_DOCS_URL — Base URL of your running self-hosted DocsMint REST API, for example http://localhost:50700. For Cloud MCP, use the Streamable HTTP remote below.
• HIAI_DOCS_API_KEY required secret — Create an API key in your self-hosted DocsMint browser UI. The stdio bridge uses it only with your own API; it does not install the Cloud OAuth server. Prefer workspace-bound or category-scoped credentials.

This server takes extra arguments — see its repository.