mcpbeat

Branch Docs MCP Server

io.github.branch-docs/ai
answering

Branch Docs is answering right now. Last checked 14 min ago. It exposes 8 tools.

Access and search Branch's official API documentation directly within any AI agent or client.

Uptime history 44 hours of history
44 hours agonow
100.0%
Uptime 24h
91 of 91 checks
8
Tools
read from the server
673 ms
Response time
average over 24h
open, no key
Access
sse

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

run in your terminal
claude mcp add ai --transport http https://docs.branchapp.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "ai": {
      "url": "https://docs.branchapp.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.ai]
url = "https://docs.branchapp.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "ai": {
      "url": "https://docs.branchapp.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "ai": {
      "url": "https://docs.branchapp.com/mcp"
    }
  }
}

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

endpoints
list-endpoints
Lists all API paths and their HTTP methods with summaries, organized by path. Results can be passed directly into 'get-endpoint'.
search-endpoints
Performs a deep search through paths, operations, and parameters to discover relevant API endpoints. Use this tool to find specific API capabilities, required parameters, or data models based on search keywords. Results can be passed directly into 'get-endpoint'.
branch
branch-overview
Call this when the user is new to Branch or is asking what Branch is, what it does, how its core objects relate (organizations, workers, wallets, payment profiles, disbursements), or where to begin an integration. Returns a one-page orientation: the object model, the worker lifecycle from onboarding through payment, the two integration approaches, and the sandbox and production environments. For specific procedures or API details, use search, fetch, and get-endpoint instead — this tool is orientation only.
endpoint
get-endpoint
Gets detailed information about a specific API endpoint, including security schemes and servers
fetch
fetch
Gets detailed content for documentation by ID returned from the `search` tool.
search
search
Searches through documentation with the given search query, returning a list of results with ID, title, and URL.
server
get-server-variables
Gets the server variables for each server within a specific OpenAPI spec.
webhook
list-webhook-events
Call this when the user asks about Branch webhooks, events, notifications, or callbacks — including which events exist, what data an event contains, or which event fires at a given point in worker onboarding or payment. Returns the complete catalog of all 22 Branch webhook events with their payload fields. Use the fetch tool with a listed doc id to get full details and a JSON example for a specific event.

Endpoints

URLTransportStateLatencyChecked
https://docs.branchapp.com/mcp sse answering 686 ms 14 min ago

Branch Docs — questions

Answers built from our own checks of this server.

What can Branch Docs do?
It exposes 8 tools, read directly from the server on our last check. Among them: branch-overview, fetch, get-endpoint, get-server-variables, list-endpoints, list-webhook-events and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Branch Docs working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 673 ms. The bar chart above shows every period we have measured.
How do I connect Branch Docs?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Branch Docs need an API key?
No. Branch Docs completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Branch Docs?
It answers our handshake in 673 ms on average, which is faster than 13% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.