https://api.eu.doconda.com/mcp, with the
Authorization: Bearer header and your API key. The agent gets Doconda’s tools (create_document, review_document,
edit_document…) and each call returns the document’s status and its download links.
Steps
-
Create an API key in the dashboard, under API keys (it starts with
ak_eu_), and put it inDOCONDA_API_KEY. -
Point your client at the remote server:
- If your client has a per-call timeout, raise it: a document takes longer to be ready than a normal call.
claude mcp add --transport http doconda https://api.eu.doconda.com/mcp --header "Authorization: Bearer ak_eu_…".
What you get back
Each tool returns a short summary (
id, format, status, links) so the agent can tell the user without spending
context. Errors also come back as results, with a code the agent can act on.
FAQ
Remote or local?
Remote or local?
The remote server is for cloud-hosted agents and n8n, and it can’t read your disk. The local one
(
npx -y @doconda/mcp, stdio) can upload files from your computer; it’s for Claude Desktop, Cursor or Codex.Which clients work?
Which clients work?
Any with Streamable HTTP: Claude, Cursor, LangChain, CrewAI, Google ADK, OpenAI Agents SDK, Mastra, n8n, smolagents,
Le Chat…
How much does it cost?
How much does it cost?
Whatever the agent does counts as if you did it with the API: same project, same price. See
pricing.
Keep reading
- MCP server: local, remote and specific clients.
- Quickstart.