MCP Server
MCP server for AI agent integrations. Claude, Cursor, and any MCP-compatible client can call tools, read resources, and use prompts against your SEO portfolio.
The Model Context Protocol is an open standard for tool-calling between language models and structured APIs. The Leto SEO MCP server uses the letoseo:// URI scheme and exposes 10 tools, 2 literal resources, 3 resource templates, and 4 prompts.
Connection URLs
| Transport | Endpoint | Method | Notes |
|---|---|---|---|
| Streamable HTTP (recommended) | https://letoseo.com/api/mcp/mcp | POST | Preferred for modern MCP clients including Claude Custom Connectors. |
| SSE — stream | https://letoseo.com/api/mcp/sse | GET | Legacy SSE transport. |
| SSE — messages | https://letoseo.com/api/mcp/message | POST | Companion endpoint to /sse, not standalone. |
Use the Streamable HTTP transport unless your client only supports the legacy SSE transport.
Server info
Clients receive the following server identity on the initialize handshake (see route.ts:496):
{
"name": "letoseo",
"version": "1.0.0"
}Authentication
The MCP server uses the same Bearer sk_live_* token flow as the REST API. Pass your API key in the Authorization header on every request. See the Authentication reference for key generation and rotation instructions.
Error behavior in V1
route.ts:530-545). Clients will receive an authentication error rather than a distinct 429 or 403. See Authentication — MCP errors for details. This will be addressed in a future release.Capabilities
Callable functions for querying portfolio health, keywords, campaigns, alerts, and more.
Fixed-URI snapshots (2) and variable-URI templates (3) that agents can read directly via letoseo:// URIs.
Pre-built prompt templates for common SEO analysis tasks — weekly digest, site health report, content opportunities, and campaign analysis.