AI and MCP
MCP server
Let your AI read this documentation and the catalogue of 6,500+ endpoints itself — no copy-paste.
Blesyum publishes a Model Context Protocol (MCP) server. An AI assistant connected to it searches this documentation, reads the endpoint catalogue, and grounds the integration code it writes in real endpoints.
https://apidocs.blesyum.com/mcpTransport: Streamable HTTP. No credentials needed — every tool is read-only and the documentation is public anyway.
Connecting
Claude Code
claude mcp add --transport http blesyum https://apidocs.blesyum.com/mcpThen verify with /mcp.
Claude (desktop / web)
Settings → Connectors → Add custom connector → URL: https://apidocs.blesyum.com/mcp
Cursor, VS Code and others
{
"mcpServers": {
"blesyum": { "url": "https://apidocs.blesyum.com/mcp" }
}
}Tools
| Tool | What it does |
|---|---|
search_docs | Search guides and 6,500+ endpoints. GET /contacts and crm:webhook shortcuts work. |
get_guide | Full text of a guide page |
list_guides | All guide pages |
list_modules | Eight modules, base paths, address templates, endpoint counts |
list_endpoints | A module's resource families, or every endpoint in one family |
get_endpoint | Full record for one endpoint + a working cURL example |
list_scopes | API key scopes |
list_webhook_events | Subscribable events |
Why it works
Ask a language model to "write code that creates a contact in Blesyum" and, without MCP, it invents: a plausible-looking endpoint path that doesn't exist, the wrong auth header, a field name that was never there. The code compiles, fails, and gives no clue why.
With MCP the model calls search_docs first, then confirms with get_endpoint. The path it writes is real, because it is derived from source.
Telling your assistant this speeds things up: "Use the Blesyum MCP server. Don't invent endpoint paths or scope names; confirm with search_docs and get_endpoint first."
Limits of the tools
Today every tool is read-only. That is deliberate: an unauthenticated write tool would turn this server into a proxy acting on everyone's behalf. If write tools are ever added, they will require the user's own API key.
Discovery
Some clients recognise a server from its manifest rather than its URL:
https://apidocs.blesyum.com/.well-known/mcp.jsonVerifying
To check the connection by hand:
curl -X POST https://apidocs.blesyum.com/mcp \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'You should see eight tools in the response.