Capabilities
- Create a Word, PowerPoint, Excel or PDF file, or an artifact, from a request or from Markdown the agent wrote.
- Edit a file: only what is asked changes, and
get_reportlists every change. - Convert a file to another format with no AI, for example any file to Markdown so the agent can read it.
- Read what people saved in an artifact, such as poll votes.
Setup
The local server uses a Doconda API key inDOCONDA_API_KEY. The remote server takes the same key as a header, or
signs you in with OAuth. Create keys in the dashboard (API keys).
Local
Any client that launches servers over stdio. The typical configuration:upload_file can read a file by its
absolute path.
Remote
Any client with Streamable HTTP transport, athttps://api.eu.doconda.com/mcp. There are two ways to authenticate:
- Sign in (OAuth) — Add the URL and nothing else. The client opens Doconda in your browser; you sign in, choose the organization and project it works in (and whether it may only read) and approve. Clients that support MCP authorization do this on their own: Claude, Claude Code, Cursor, VS Code, MCP Inspector.
- API key — Send
Authorization: Bearer ak_eu_…on every request. Use it for clients without OAuth and for your own backend.
Specific clients
Claude Desktop and Claude Code
Cursor
OpenAI Codex
LangChain
CrewAI
n8n
Hugging Face (smolagents)
Cursor
In.cursor/mcp.json (this project) or ~/.cursor/mcp.json (all projects):
"doconda": { "url": "https://api.eu.doconda.com/mcp" }.
With an API key instead: "doconda": { "url": "https://api.eu.doconda.com/mcp", "headers": { "Authorization": "Bearer ${env:DOCONDA_API_KEY}" } }.
OpenAI Codex
In~/.codex/config.toml (used by the CLI and the editor extension):
Your own server
If you already run an MCP server,createServer from @doconda/mcp returns a Server from the official MCP SDK with
Doconda’s tools, ready to connect to your transport:
{ localFiles: true } as the second argument to let upload_file read files from disk, and waitSeconds to
change how long create_document and edit_document wait for the document (240 s by default).
Tools
The server exposes the eight Doconda tools; see the tools for what each one does. A failed call comes back withisError: true and { "error": "<code>", "message": "…" } as its text, so the agent can
read the code and correct itself.
What a connected app can do
An app connected with OAuth gets one of two permissions, chosen when you approve it:
A read-only app gets
403 with insufficient_scope on a tool that writes, and the client can ask you to approve more.
A connected app uses its project’s documents and balance. You can see and disconnect apps in the dashboard under
Connected apps. A connection also ends when the person who approved it leaves the organization, when the
organization is blocked (lifting the block doesn’t restore it), or after 30 days
without use.
For MCP client developers
- Without a token, every request (
initializeandtools/listincluded) gets401withWWW-Authenticate: Bearer resource_metadata="https://api.eu.doconda.com/.well-known/oauth-protected-resource/mcp". - The authorization server is
https://api.eu.doconda.com(metadata at/.well-known/oauth-authorization-server): authorization code with PKCES256; theresourceparameter is required and must be the server URL; Client ID Metadata Documents or dynamic registration (/oauth/register); redirects over HTTPS or to localhost (any port);issin the authorization response. - Access tokens last 1 hour, and refresh tokens rotate on every use. Reusing a spent refresh token disconnects the app, except for a retry: for 30 seconds, the same client can redeem its last refresh token again and gets a new pair.
- With an OAuth token, a request carries at most one
tools/call; a batch with more gets400. - Tokens issued for the MCP server only work there: the REST API (
/v1) refuses them and takes API keys. - The tool list without signing in:
https://api.eu.doconda.com/.well-known/mcp/server-card.json. - Only
POSTis accepted;GETandDELETEget405.
Troubleshooting
- The call times out before the document is ready —
create_documentandedit_documentwait up to about 4 minutes, then return the document’sidandstatusforget_documentto check later. Set the client’s per-call timeout to 300 s. Claude’s connector gives up after about a minute, so with it they return after about 50 s and Claude callsget_documentlater. 401on every request — The remote server needs a token: sign in through the client, or sendAuthorization: Bearer ak_eu_….upload_fileanswersGive url or content_base64.— Only the local server reads files from disk. With the remote server, pass a publicurl, orcontent_base64withfilename.- The download link stopped working — File links expire after 5 minutes; the agent calls
get_documentfor fresh ones.
Useful links
- Doconda in your agent: every stack and the tools.
- doconda-examples on GitHub: ready-to-run scripts.
- Model Context Protocol: the protocol and its clients.
- API reference: the endpoints behind each tool.