list-endpoints
List API Endpoints
Lists all API paths and their HTTP methods with summaries, organized by path. Results can be passed directly into 'get-endpoint'.
Takes no parameters.
io.github.branch-docsPublished by GitHub account branch-docsv1.0.2Updated Nov 3, 2026
Access and search Branch's official API documentation directly within any AI agent or client.
Branch Docs's hosted MCP server (docs.branchapp.com); no sign-in required; Streamable HTTP; 8 tools.
No AI overview yet: these facts come from the registry entry and the server itself.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.branch-docs%2Fai/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"branch-docs": {
"type": "http",
"url": "https://docs.branchapp.com/mcp"
}
}
}Welcome to Branch's centralized hub for public AI resources and integrations. This repository bridges the gap between AI assistants and the Branch platform by exposing two distinct integration vectors:
Branch runs a managed cloud-native MCP server directly through our core documentation platform. This server securely exposes read-only tools allowing AI agents to dynamically query, search, and parse the live Branch API reference.
Because this is hosted via the cloud, there is no local environment configuration required—no local runtime dependencies, Node modules, scripts, or manual compilation.
To expose Branch's documentation tools to an MCP-capable client (such as Claude Desktop), add the endpoint to your ecosystem configuration file.
For Claude Desktop, append the following block to your configuration schema (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, or %APPDATA%\Claude\claude_desktop_config.json on Windows) and restart the application:
Once initialized, your AI assistant will programmatically discover, surface, and execute the server's documentation lookups autonomously during active conversations.
The /skills directory contains packaged Claude Skills. These are explicit, highly structured behavioral guardrails that train an AI model to architect Branch integrations safely and correctly (e.g., properly routing sensitive KYC data outside of partner applications, utilizing standard webhooks, and optimizing global payout architectures).
Important Deployment Note
Unlike the MCP Server, Claude Skills do not self-load. Due to the sandboxed, contextual design of LLM workspaces, an AI assistant cannot discover, activate, or persist these instructions simply by reading or crawling this repository. Connecting the MCP server does not import these skills; they operate on a separate infrastructure layer. They must be manually uploaded into your Claude workspace environment using the steps below.
/dist directory in this repository and download the compiled .zip archive for your desired skill..zip file to activate it within your account.
Note: Ensure "Code Execution" is toggled on within your individual Claude workspace settings.To provision a skill globally across an entire enterprise workspace so individual users do not have to configure it manually:
.zip archive from the /dist folder./skills vs /distTo maintain open-source transparency while providing seamless deployment, this repository separates source materials from production assets:
/skills (Source Framework): Contains editable, human-readable markdown manifests (SKILL.md) and contextual reference schemas. This is the development workspace where updates, code contributions, and peer reviews occur./dist (Production Builds): Contains the compiled, ready-to-upload .zip deployment packages. Each archive bundles the corresponding markdown source and linked assets into a single-step upload package compatible with Claude's ingestion engine.When source files in /skills are modified and merged, production artifacts in /dist are compiled automatically via automation workflows to maintain absolute parity.
branch-onboarding-expert Establishes strict guardrails for handling Branch worker onboarding and payout flows. Strategically guides developer models away from high-risk or legacy endpoints that mishandle PII/KYC data, forcing alignment with Branch's secure hosted onboarding screens.
branch-integration-audit An autonomous code review engine. When fed active integration files or code snippets, it runs a structured compliance check, generating a definitive report highlighting structural vulnerabilities, integration warnings, and passing architectural patterns.
The skills provided in this hub are optimized for the SKILL.md syntax native to Anthropic's Claude ecosystem. While the underlying functional logic and compliance guidelines remain universally applicable across any generative AI framework, the explicit setup, ingestion, and execution instructions detailed above are tailored exclusively to Claude workspaces.
Source: README.md at commit aee8909
List API Endpoints
Lists all API paths and their HTTP methods with summaries, organized by path. Results can be passed directly into 'get-endpoint'.
Takes no parameters.
Get Endpoint Details
Gets detailed information about a specific API endpoint, including security schemes and servers
pathrequiredmethodrequiredSearch API 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'.
patternrequiredGet Server Variables
Gets the server variables for each server within a specific OpenAPI spec.
Takes no parameters.
Search Documentation
Searches through documentation with the given search query, returning a list of results with ID, title, and URL.
queryrequiredFetch Documentation Page
Gets detailed content for documentation by ID returned from the `search` tool.
idrequiredList 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.
Takes no parameters.
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.
Takes no parameters.
90% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare a license in the repository or the registry entry.
{ "mcpServers": { "branch-docs": { "type": "http", "url": "https://docs.branchapp.com/mcp" } }}