Skip to main content
Lokutor runs two MCP servers. Both are hosted (Streamable HTTP), so adding one to Claude Code, Cursor, VS Code or any other MCP client is a single line. There is nothing to clone or install.

Lokutor API

Tools

synthesize_speech takes text (up to 1,000 characters), voice, language, speed (0.5–2.0) and steps (1–8, accepted but no effect: the current voice model runs a fixed 4). For longer text, call POST /tts/synthesize directly. Tools run exactly like the REST endpoints behind them, with the same authentication, balance checks and errors. A rejected key or a balance too low to start (billing.insufficient_balance) comes back as a tool error the assistant can read.
The Call Center API (buying numbers, placing outbound calls, bulk-dialing) is deliberately not exposed. Those endpoints spend real money and place real calls to real people, with consent_confirmed as the only built-in gate. The caller is the confirmation step, and an assistant calling a tool on its own is not that. Real-time voice agents run over WebSocket, which MCP tools do not model, so they are not tools either.

Add it

Create an API key in the dashboard and send it as the Authorization header. Without a key, the five discovery tools still work.

Protocol

Streamable HTTP, stateless. Every request is a POST of one JSON-RPC message (or a batch), answered with application/json. There is no session and no server-initiated stream, so GET returns 405. Protocol revisions 2025-11-25, 2025-06-18, 2025-03-26 and 2024-11-05 are supported.

Lokutor Docs

Gives an assistant search_lokutor and a read-only view of every page and the OpenAPI spec, so it answers from the current docs instead of from memory. No key needed.