Diadoc MCP: 114 document-flow methods
diadoc-mcp-ru
An MCP server for the Diadoc (Kontur) API: documents, counterparties, signing and power of attorney, with confirmation before writes
- 3 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Can sign and send documents on behalf of the organization
- 7 methods are irreversible, such as the final dispatch of a document to a counterparty
Install
- Works in
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/diadoc-mcp-ruDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Can sign and send documents on behalf of the organization
- 7 methods are irreversible, such as the final dispatch of a document to a counterparty
This is third-party code. Review the repository files before installing.
What it does
The server compiles all 114 Diadoc methods from Kontur's official docs into a single endpoints.yaml file and gives the agent three tools instead of a hundred separate functions: search a method by keywords, view its parameter card and access class, and call it. It covers incoming and outgoing documents, document-flow statuses, counterparties and EDF invitations, signing, machine-readable power of attorney and printable forms. Of the 114 methods, 78 read-only ones run immediately, while 29 write and 7 irreversible ones require confirmation. Keys are stored locally in ~/.ru-mcp/cabinets.json with 600 permissions, not only in environment variables.
Who it is for. For accountants, lawyers and developers running electronic document flow through Diadoc who want to do it from a chat with an agent.
Good fit when
- You need to reconcile document flow with a counterparty for a period or find documents needing action
- You need to check a counterparty by INN and KPP and their EDF connection
- You need to download a document's printable form for accounting
Not a fit when
- You do not have a Diadoc application ID and a production license: real use needs a separate request to Kontur
- You do not want the agent to be able to sign or send documents: even with confirmation, these are sensitive operations
Example request
Show incoming Diadoc documents that need action on my sideMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
DIADOC_CLIENT_IDrequired- Diadoc application ID, issued by Kontur
DIADOC_TOKENrequired, secret- User token, issued by the Authenticate method
Limitations
Production use needs a Kontur license and an application ID issued by request. The user token comes from a separate Authenticate call using login and password or a certificate. All 114 methods are available, but 7 of them are irreversible (for example, final document dispatch).
How to disable. Remove the diadoc-mcp entry from claude_desktop_config.json or another MCP client's config, and delete ~/.ru-mcp/cabinets.json if needed.
FAQ
Does the agent need to know all 114 methods?
No, there are three tools: search by keywords, a method card, and a call; the agent finds the right one itself.
Can the agent send a document without confirmation?
No, write and irreversible actions require explicit confirmation, only reads run immediately.
Discussion
No questions or reviews yet.
Related
MCP serversKontur.Diadoc MCP
kontur-diadoc-mcp
MCP server for Kontur.Diadoc EDI: organization lookup by INN, document lists and contents, sending and signing
A local document base for your agent: hybrid semantic and keyword search plus a web UI for browsing and uploads
An MCP server built on Docling: converts PDFs into structured documents, builds new ones and feeds them to RAG
MCP PDF for large documents: the agent searches by meaning and keyword across one file or a folder and reads only the pages, tables and scans it needs
The MCP server connects an agent to a learning canvas where a question about a passage opens a linked document.
PageIndex MCP: long PDFs for an agent
PageIndex MCP
An MCP server that lets an agent read long PDFs through a document tree: retrieval by reasoning instead of a vector database
README in short
The README explains that the method catalog is compiled from Kontur's official docs and lives in the repo as endpoints.yaml, so the table cannot drift from the code. It shows installation via a no-terminal .mcpb file and via uvx, an environment variable table, a method breakdown by section with read, write and irreversible counts, a sample dialogue finding a method, and a security and privacy section stating the server collects and sends no data.