MCP Server Setup

This puts the Access SDK docs right inside your coding agent. Your agent can search the SDK, pull up any page as Markdown, and see the full outline, all over one endpoint. The point is that it works from the real docs instead of guessing from whatever it picked up in training.

It runs over Streamable HTTP, so any MCP-capable agent can use it. There's no sign-in and no API key. You paste the URL and you're done. Once it's connected your agent gets three tools: search_docs, get_page, and list_sections.

How connecting works

Clients that take the URL directly

These are the easy ones. Paste the endpoint and you're set.

Claude Code

One command, nothing to edit:

claude mcp add --transport http ci-hub-access https://developer.ci-hub.com/access/mcp

Run claude mcp list to check it's there. Claude Code also reads a project-level .mcp.json, so if you commit that file the whole team gets the server.

Claude Desktop

Add it under Settings, Connectors, Add custom connector, with the URL above. Custom connectors work on every plan, and Free accounts can hold one at a time. If connectors are switched off for your workspace, the mcp-remote bridge does the same job:

{
  "mcpServers": {
    "ci-hub-access": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://developer.ci-hub.com/access/mcp"]
    }
  }
}

Cursor

Drop this in ~/.cursor/mcp.json for every project, or .cursor/mcp.json for just this one:

{
  "mcpServers": {
    "ci-hub-access": { "url": "https://developer.ci-hub.com/access/mcp" }
  }
}

You'll see the server and its tools under Settings, MCP. A green dot means it connected.

VS Code

Add this to .vscode/mcp.json in your workspace. Copilot's Agent mode reads it:

{
  "servers": {
    "ci-hub-access": { "type": "http", "url": "https://developer.ci-hub.com/access/mcp" }
  }
}

Open the Chat view in Agent mode and the CI HUB tools show up in the tools picker.

GitHub Copilot

In VS Code, Copilot uses the same .vscode/mcp.json shown above. For the Copilot coding agent on github.com, add the server under Repository, Settings, Copilot, MCP with the same type: "http" and URL.

Windsurf

Add this to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "ci-hub-access": { "serverUrl": "https://developer.ci-hub.com/access/mcp" }
  }
}

Then hit Refresh in the Cascade MCP panel. Heads up: Windsurf uses serverUrl, not url.

Cline, Roo Code, Kilo Code

These VS Code extensions use the same shape. In the extension's MCP settings, add a remote server:

{
  "mcpServers": {
    "ci-hub-access": {
      "type": "streamableHttp",
      "url": "https://developer.ci-hub.com/access/mcp"
    }
  }
}

OpenCode

Add this to opencode.json:

{
  "mcp": {
    "ci-hub-access": {
      "type": "remote",
      "url": "https://developer.ci-hub.com/access/mcp",
      "enabled": true
    }
  }
}

Conductor

Conductor doesn't have its own MCP format. It uses whatever the underlying agent loads for that workspace, so you set it up for Claude Code (or Codex, or Cursor) and Conductor picks it up. For Claude Code, commit a .mcp.json at the repo root and every workspace inherits it:

{
  "mcpServers": {
    "ci-hub-access": {
      "type": "http",
      "url": "https://developer.ci-hub.com/access/mcp"
    }
  }
}

Zed

Register the endpoint as a context server in Zed's settings.json, or add it under Settings, AI, MCP Servers, Add Server, Add Remote Server:

{
  "context_servers": {
    "ci-hub-access": { "url": "https://developer.ci-hub.com/access/mcp" }
  }
}

Zed calls the key context_servers, not mcpServers. Leave the Authorization header out, since this endpoint needs no auth.

Clients that need the bridge

A few clients only speak the local stdio transport. mcp-remote bridges your HTTP endpoint into a stdio process for them. It runs through npx, so there's no install, but it does need Node.js on the machine.

Codex CLI

Codex reads ~/.codex/config.toml. Point a server at the bridge:

[mcp_servers.ci-hub-access]
command = "npx"
args = ["-y", "mcp-remote", "https://developer.ci-hub.com/access/mcp"]

Anything else

If your client only takes a command and args (stdio) server, the same bridge works everywhere. Just drop it into that client's config file:

{
  "command": "npx",
  "args": ["-y", "mcp-remote", "https://developer.ci-hub.com/access/mcp"]
}

Check that it worked

Once the server is added, ask your tool something like:

Search the CI HUB Access SDK docs for the token exchange, then read that page.

It should call search_docs and then get_page. Asking it to "list the CI HUB Access SDK sections" is a quick way to exercise list_sections too.

If something's off

• The tools don't show up. The client cached its config at startup. Restart it or use its refresh action.
• It won't connect at all. Check the URL is exactly https://developer.ci-hub.com/access/mcp with no trailing slash. Opening it in a browser tells you nothing useful, since MCP clients negotiate a session before anything is served. Send a real initialize call instead:

curl -i -X POST https://developer.ci-hub.com/access/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"1"}}}'

A 200 means it's up. A 404 means the URL or path is wrong.

• A stdio client won't start the server. mcp-remote needs Node.js, so make sure node and npx are on your PATH.
• You're getting the wrong docs. This endpoint only serves the Access SDK. The Integration SDK has its own endpoint.