Branch Docs MCP Server

by branch-docs Your server? Claim it

answering

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

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

Uptime history 91 days of history · worst day 90%

91 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

428 ms

Response time

average over 24h

open, no key

Access

sse

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 29 October 2026. No other catalogue keeps this.

31 Oct a tool changed the parameters it asks for fetch

29 Oct a tool changed the parameters it asks for fetch

Nothing serious here today

Today is the operative word: we check Branch Docs every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add ai --transport sse https://docs.branchapp.com/mcp

Settings → Connectors → Add custom connector, then paste this address

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

{
  "servers": {
    "ai": {
      "type": "sse",
      "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

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

URL	Transport	State	Latency	Checked
https://docs.branchapp.com/mcp	sse	answering	314 ms	3 min ago

Alternatives to Branch Docs

same job, measured the same way

Adobe Commerce Docs MCP

by jigarkkarangiya

MCP server for Adobe Commerce / Magento 2 documentation — search, browse, and read official docs.

73 installs/wk local only

Egnyte MCP Server

by ptyagiegnyte

Official Egnyte MCP Server for AI integration with document search, analysis, and collaboration.

local only

Gitlab Docs

by ozanmutlu

Search and browse 2,900+ official GitLab documentation pages via MCP

501 installs/wk local only

Docs

by empryo

Search and read Empryo's documentation. Read-only, no auth, no local access.

4 tools answering

Google AI Search MCP

by shariqriazz

Google AI search and documentation tools for MCP clients using Vertex AI or the Gemini API.

999 installs/wk local only

MCP Devkit Server

by mapbox

Provides AI assistants with direct access to Mapbox developer APIs and documentation.

959 installs/wk answering

Ref Tools MCP

by ref-tools

Token efficient search for coding agents over public and private documentation.

1 347 installs/wk local only

Ref Tools MCP

by ref

Token-efficient search for coding agents over public and private documentation.

answering

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 428 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 in the form 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 428 ms on average, which is faster than 30% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.