At https://platform.trylath.com/mcp
The server speaks the Model Context Protocol over streamable HTTP, authenticated with Authorization: Bearer <key>. tools/list returns every operation the key is allowed to call; tools/call runs one.
Tool names are the operation with dots replaced by underscores, because MCP names allow [A-Za-z0-9_-] only — sms.send is sms_send, developers.key.create is developers_key_create.
An agent does not need to be told what exists. It reads the tool list, gets each schema, and calls. A refusal comes back as a tool result carrying code, message and fix, so the agent reads the next step rather than a protocol error.
For a client that runs local servers instead, npx -y @trylath/cli mcp serves the same tools over stdio. For agents has the exact setup for each client Lath supports.
A tools/call, exactly as the live server accepts it.
Last modified on September 23, 2026
