diadoc-mcp

Diadoc (Kontur EDM) via MCP

Installs the server diadoc-mcp from the package diadoc-mcp-ru: 114 methods (79 read, 28 write, 7 irreversible), the catalog is compiled from the documentation developer.kontur.ru/doc/diadoc-api.

Installation

{
  "mcpServers": {
    "diadoc": {
      "command": "uvx",
      "args": ["--from", "diadoc-mcp-ru", "diadoc-mcp"],
      "env": {
        "DIADOC_CLIENT_ID": "<идентификатор приложения>",
        "DIADOC_TOKEN": "<токен пользователя>"
      }
    }
  }
}

Where to get the keys

The application ID is requested from Kontur by letter; for production a license is required. For trials there is a test environment.
The user token is issued by the method Authenticate using a login and password or a certificate.
Both values go in a single header DiadocAuth, the server assembles it itself.

Typical tasks

Show incoming documents that require action.
Reconcile document flow with a counterparty for a period.
Find a counterparty by INN and KPP, check whether it is connected to EDM.
Download the printable form of a document.

Signing and sending is a write operation: the agent must ask for confirmation, and before that show exactly what is being sent to the counterparty.

About this skill

Installation

Where to get the keys

Typical tasks