Understand the workspace
Agents can read reports, templates, datasets, metrics, connections, knowledge, Brand DNA, and workspace health.
Model Context Protocol
Connect the AI client or custom agent flow your team already uses. It can discover Donum's typed workspace tools, then work through the same rules your team does.
Your client
Bring the interface where your team already thinks and works.
MCP connection
A workspace API key establishes the connection and identifies every request.
Donum workspace
The agent works through Donum, not around it.
Connect once
Choose the client you already use. Donum supplies one secure MCP endpoint and a typed, workspace-aware tool surface.
01
Settings → MCP
02
SSE + Bearer header
03
Inside your flow
Add Donum to your MCP configuration
Create a workspace API key in Donum, then add this server configuration to Claude Desktop.
{
"mcpServers": {
"donum": {
"type": "sse",
"url": "https://api.donum.club/api/mcp/sse",
"headers": {
"Authorization": "Bearer hlk_your_api_key_here"
}
}
}
}Inside your agentic flow
The server exposes 85 synchronized workspace tools. They are grouped around the work your agent needs to complete, not a made-up demo catalog.
Agents can read reports, templates, datasets, metrics, connections, knowledge, Brand DNA, and workspace health.
Agents can create and generate reports, trigger workflows, run agents, manage projects, and work with recipients and artifacts.
Agent proposal review and application remain separate actions. Existing role checks, validation, governance, and deletion rules still apply.
Your key belongs to one workspace. The raw key is shown once and its stored value is hashed.
Each MCP message must match the workspace and API key used to open the SSE session.
MCP tools call Donum workspace APIs so authorization, validation, and domain rules remain active.
MCP release history