Client setup

Configure the client you use once. The server name is yours to choose; the steps below use qnbot_docs throughout. Every client points at the same endpoint, https://docs.qnbot.com/mcp.

Codex

Codex CLI and the Codex desktop app share one user-level configuration. Run:

codex mcp add qnbot_docs --url https://docs.qnbot.com/mcp
codex mcp get qnbot_docs

You can also edit ~/.codex/config.toml directly:

[mcp_servers.qnbot_docs]
url = "https://docs.qnbot.com/mcp"

Restart the Codex CLI session or reopen the desktop app for it to take effect. A session that never asks for approval needs the three read-only tools allowed explicitly; see tool calls that need approval.

Claude Code

claude mcp add --transport http qnbot_docs --scope user https://docs.qnbot.com/mcp
claude mcp list

--scope user makes the server available in every project on this machine. Use --scope project to keep it to the current project: the configuration is written to .mcp.json in the project root so it can be committed with the project. Run /mcp in Claude Code to confirm that qnbot_docs is connected.

Cursor

Create .cursor/mcp.json in the project root; use ~/.cursor/mcp.json instead to make the server available in every project on this machine:

{
  "mcpServers": {
    "qnbot_docs": {
      "url": "https://docs.qnbot.com/mcp"
    }
  }
}

Reopen Cursor or start a new agent session, then check the MCP section of Cursor's settings to confirm that qnbot_docs is connected with its tools enabled.

VS Code

Create .vscode/mcp.json in the project root:

{
  "servers": {
    "qnbot_docs": {
      "type": "http",
      "url": "https://docs.qnbot.com/mcp"
    }
  }
}

Run MCP: List Servers from the Command Palette to confirm the server is running, then enable the qnbot_docs documentation tools in the tool picker of a GitHub Copilot chat.

Confirm the connection

Clients only load a new MCP configuration when they restart or open a new session. Have the agent call list_docs or search_docs: pages or results coming back means the server is connected.

For connection failures, tool approval, and reading a page in full through markdownPath, see Verification & troubleshooting; the three tool inputs and return values are in Available tools.