Schema | Branch Diagnostics MCP

Branch Diagnostics MCP

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

Features and capabilities supported by this server

Capability	Details
`tools`	{ "listChanged": true }
`logging`	{}
`prompts`	{ "listChanged": false }
`resources`	{ "subscribe": false, "listChanged": false }
`extensions`	{ "io.modelcontextprotocol/ui": {} }
`experimental`	{}

Functions exposed to the LLM to take actions

Name	Description
diagnostic_categorizeA	Step 1 of the funnel: classify a free-text symptom into the most likely diagnostic category, with a confidence score and the scores for every category.
find_metricsA	Step 2 of the funnel: for a symptom and category, return the cURL metrics most worth collecting, each with its definition and why it is relevant.
get_data_metricsA	Step 3 of the funnel: fetch current values, rolling averages, and thresholds for the given metrics at a location. Data is simulated by default (`simulated` is true); swap the data source for a real backend in production.
analyseA	Step 4 of the funnel: evaluate collected metric data against thresholds, surface anomalies with severities, and return recommendations and next steps.

Interactive templates invoked by user choice

Name	Description
`branch_diagnostics_guidance`	Reusable system guidance that teaches a client how to drive the funnel.

Contextual data attached and managed by the client

Name	Description
`get_categories`	All diagnostic categories with their metrics and typical symptoms.
`get_metrics`	All cURL (CURLINFO_*) metric definitions.

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Fromzy1/branch_mcp_v2'

If you have feedback or need assistance with the MCP directory API, please join our Discord server