Model Context Protocol (MCP)

The ReachFive documentation MCP server is in limited internal use today. General availability for customers is coming soon.

The ReachFive Model Context Protocol (MCP) server lets AI coding agents search official developer documentation from your IDE or CLI. Agents retrieve the same indexed content that powers the Ask AI assistant on this site, with citations back to canonical guides and API references.

This is a documentation retrieval service. It does not call your ReachFive tenant APIs, change console settings, or perform actions on end-user accounts.

How this compares to Ask AI on the docs site

Capability Ask AI (docs site widget) MCP server

Capability	Ask AI (docs site widget)	MCP server
Where it runs	In your browser (`developer.reachfive.com`)	In your agent client (Cursor, Claude Code, VS Code, and other MCP hosts)
What you get	Full conversational answers generated by the docs assistant	Structured doc chunks for your agent to reason over and cite
Best for	Quick questions while browsing documentation	Day-to-day integration work inside your repository

Where it runs

In your browser (developer.reachfive.com)

In your agent client (Cursor, Claude Code, VS Code, and other MCP hosts)

What you get

Full conversational answers generated by the docs assistant

Structured doc chunks for your agent to reason over and cite

Best for

Quick questions while browsing documentation

Day-to-day integration work inside your repository

Prerequisites

Before you connect:

An MCP-compatible agent client (see Connect to the ReachFive MCP server).
An MCP API key issued by ReachFive.
Network egress to the MCP host and to developer.reachfive.com (for the live documentation index).

Do not commit API keys to git. Store them in your password manager, shell profile, or client secret store.

Connect to the ReachFive MCP server

The hosted endpoint uses Streamable HTTP MCP transport.

Server URL: https://mcp.developer.reachfive.com/mcp
Health check (no auth): https://mcp.developer.reachfive.com/health

Prefer environment variable expansion if your client supports it, rather than pasting secrets into tracked files.

Cursor

Add the following to .cursor/mcp.json in your project, or to your global Cursor MCP settings. Restart Cursor after saving.

{
  "mcpServers": {
    "reachfive-docs": {
      "url": "https://mcp.developer.reachfive.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_MCP_API_KEY" (1)
      }
    }
  }
}

1	Replace `YOUR_MCP_API_KEY` with your actual API key.

See the Cursor MCP documentation for troubleshooting.

VS Code

Add a .vscode/mcp.json file in your workspace (or use your user-level MCP config, depending on your VS Code build).

{
  "servers": {
    "reachfive-docs": {
      "type": "http",
      "url": "https://mcp.developer.reachfive.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_MCP_API_KEY" (1)
      }
    }
  }
}

1	Replace `YOUR_MCP_API_KEY` with your actual API key.

See the VS Code MCP documentation.

Claude Code

From your project directory:

claude mcp add --transport http reachfive-docs \
  https://mcp.developer.reachfive.com/mcp \
  --header "Authorization: Bearer $REACHFIVE_MCP_API_KEY" (1)

1	Replace `REACHFIVE_MCP_API_KEY` with your actual API key.

See the Claude Code MCP documentation.

Other MCP clients

Many editors and agent frameworks support remote HTTP MCP. Use:

URL: https://mcp.developer.reachfive.com/mcp
Authorization: Bearer YOUR_MCP_API_KEY (or X-API-Key: YOUR_MCP_API_KEY)
Accept header: application/json, text/event-stream (required by the MCP HTTP specification; most clients add this automatically)

Consult your client’s documentation for the exact JSON shape. The type value streamable-http is an alias for http in several clients.

Verify the connection

Health check

curl https://mcp.developer.reachfive.com/health (1)

1	JSON response with `"status":"ok"` and `"service":"reachfive-docs-mcp"` means the server is reachable.

MCP handshake

curl -X POST https://mcp.developer.reachfive.com/mcp \
  -H "Authorization: Bearer YOUR_MCP_API_KEY" \ (1)
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"smoke-test","version":"1.0.0"}},"id":1}'

1	Replace `YOUR_MCP_API_KEY` with your actual API key.

You should receive a response with the server information and the capabilities of the server.

Agent smoke test

In your connected client, ask a normal integration question, for example:

How do I implement passkeys on web with ReachFive?
What is refresh token rotation in ReachFive?
Where is SSO logout documented?

Pass: The agent searches documentation and answers with links to developer.reachfive.com pages. You do not need to name MCP tools in your prompt.

How to use it day to day

Once connected, treat the MCP server as always-on documentation context for your agent.

Ask questions in plain language while you work in your repository. The agent chooses the right search tool based on your question and the tool descriptions exposed by the server.

Typical flows:

Implementing a feature: "What does the docs recommend for PKCE in a SPA?"
Debugging: "We’re seeing invalid refresh token errors; what does the official guide say?"
API discovery: "What parameters does passwordless OTP expect?"
Release awareness: "Any breaking changes in the latest release notes?"

Optional: add a project rule in your client telling the agent to prefer ReachFive MCP results over training data for integration facts.

Tools

The server exposes the following MCP tools (v0.5). Your agent calls them automatically; you rarely need to reference them by name.

Tool Description

Tool	Description
`get_docs_index`	Fetches the live `llms.txt` documentation map. Useful for discovering canonical URLs and module layout.
`search_docs`	Semantic vector search over developer documentation. Best for conceptual and integration questions. Supports optional `context_query` for follow-up questions.
`search_docs_keyword`	Full-text keyword search (natural language, stemmed terms). Good for multi-word queries such as refresh token.
`search_docs_exact`	Literal case-insensitive substring search. Best for exact API names, hyphenated terms, and precise strings such as `authorizeUser`.

get_docs_index

Fetches the live llms.txt documentation map. Useful for discovering canonical URLs and module layout.

search_docs

Semantic vector search over developer documentation. Best for conceptual and integration questions. Supports optional context_query for follow-up questions.

search_docs_keyword

Full-text keyword search (natural language, stemmed terms). Good for multi-word queries such as refresh token.

search_docs_exact

Literal case-insensitive substring search. Best for exact API names, hyphenated terms, and precise strings such as authorizeUser.

Authentication and security

API key

POST /mcp requires an API key via one of:

Authorization: Bearer YOUR_MCP_API_KEY
X-API-Key: YOUR_MCP_API_KEY

GET /health does not require authentication.

Troubleshooting

Symptom Likely cause and fix

Symptom	Likely cause and fix
HTTP `401` on `/mcp`	Missing or invalid API key. Check the `Authorization` or `X-API-Key` header.
HTTP `406` on `/mcp`	Missing `Accept: application/json, text/event-stream` header. Add it for raw `curl` tests; IDE clients usually handle this.
HTTP `429`	Rate limit exceeded. Wait one minute or contact support if you need a higher quota.
Agent does not search docs	MCP server not connected in client settings, or client did not reload after config change. Restart the client and confirm the server shows as connected with four tools.

HTTP 401 on /mcp

Missing or invalid API key. Check the Authorization or X-API-Key header.

HTTP 406 on /mcp

Missing Accept: application/json, text/event-stream header. Add it for raw curl tests; IDE clients usually handle this.

HTTP 429

Rate limit exceeded. Wait one minute or contact support if you need a higher quota.

Agent does not search docs

MCP server not connected in client settings, or client did not reload after config change. Restart the client and confirm the server shows as connected with four tools.

Get access

Currently, MCP access is limited to internal ReachFive employees.