mcp server
Branch Docs
Access and search Branch's official API documentation directly within any AI agent or client.
Description as published by the maintainer. Source
- version 1.0.0
- active
- documentation
- document understanding
- retrieval
active — Registry entry last updated 2026-06-21. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
8 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
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.
fetch(id)- Gets detailed content for documentation by ID returned from the `search` tool. Required: id.
get-endpoint(path, method)- Gets detailed information about a specific API endpoint, including security schemes and servers Required: path, method.
get-server-variables- Gets the server variables for each server within a specific OpenAPI spec.
list-endpoints- Lists all API paths and their HTTP methods with summaries, organized by path. Results can be passed directly into 'get-endpoint'.
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.
search(query)- Searches through documentation with the given search query, returning a list of results with ID, title, and URL. Required: query.
search-endpoints(pattern)- 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'. Required: pattern.
Last successful function declaration observed on . Source: https://docs.branchapp.com/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://docs.branchapp.com/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-06-21 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-06-21 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 8 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | docs.branchapp.com | |
| mcp endpoint status | ok | The server listed 8 functions when asked. | as of probe | docs.branchapp.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json