Runtime
Endpoint map
A practical guide to endpoint maps, the routing layer that connects MCP tool names to upstream API operations and SDK methods.
Definition
An endpoint map is the generated routing table that connects MCP tool names and SDK-shaped methods to the upstream operation they represent. It records method, path, parameters, auth requirements, content types, and runtime behavior.
How Astrail Uses It
Astrail uses endpoint maps as the source of truth for generated tools, Code Mode execution, docs search, SDK exports, and runtime dispatch. This keeps the hosted endpoint and owned SDK bundle aligned.
Implementation Checklist
Keep operation IDs stable so regenerated tools do not churn names unnecessarily.
Record auth, path params, query params, body shape, and response expectations.
Use endpoint maps for dispatch instead of evaluating arbitrary model code.
Version or diff endpoint maps when upstream specs change.
FAQ
Is endpoint map an MCP standard term?
No. It is an implementation pattern used by generated MCP runtimes to safely route standard MCP tool calls to concrete upstream operations.
Why does Code Mode need an endpoint map?
The endpoint map lets Astrail translate constrained SDK-shaped calls into known operations without running arbitrary code from the model.