<strong>Know What Your AI Agents Are Doing. Before They Do It.</strong>
If you already use Cordum, the cordum mcp server is the piece that lets your assistant work with it directly. Know What Your AI Agents Are Doing. Before They Do It..
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Image — GHCRapi-gateway — ghcr.io/cordum-io/cordum/api-gatewayscheduler — ghcr.io/cordum-io/cordum/schedulersafety-kernel — ghcr.io/cordum-io/cordum/safety-kernelworkflow-engine — ghcr.io/cordum-io/cordum/workflow-enginecontext-engine — ghcr.io/cordum-io/cordum/context-enginemcp — ghcr.io/cordum-io/cordum/mcpdashboard — ghcr.io/cordum-io/cordum/dashboardPorts — The Ports tool exposed by this serverTroubleshooting — For detailed troubleshooting, see docs/troubleshooting.mdInstallation goes through your MCP client rather than a global install: point it at cap-sdk-node on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Configuration is passed through the environment: CORDUM_API_KEY, REDIS_PASSWORD, CORDUM_GATEWAY, CORDUM_TENANT_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Cordum's toolset — Image, api-gateway, scheduler and 7 more — is a fair guide to whether it matches your workflow. It is maintained by cordum-io; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Image | GHCR |
| api-gateway | [ghcr.io/cordum-io/cordum/api-gateway](https://github.com/cordum-io/cordum/pkgs/container/cordum%2Fapi-gateway) |
| scheduler | ghcr.io/cordum-io/cordum/scheduler |
| safety-kernel | ghcr.io/cordum-io/cordum/safety-kernel |
| workflow-engine | ghcr.io/cordum-io/cordum/workflow-engine |
| context-engine | ghcr.io/cordum-io/cordum/context-engine |
| mcp | ghcr.io/cordum-io/cordum/mcp |
| dashboard | ghcr.io/cordum-io/cordum/dashboard |
| Ports | The Ports tool exposed by this server. |
| Troubleshooting | For detailed troubleshooting, see [docs/troubleshooting.md](docs/troubleshooting.md). |
{
"mcpServers": {
"cordum": {
"command": "npx",
"args": ["-y", "cap-sdk-node"],
"env": {
"CORDUM_API_KEY": "your-value",
"REDIS_PASSWORD": "your-value",
"CORDUM_GATEWAY": "your-value",
"CORDUM_TENANT_ID": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| CORDUM_API_KEY | Credential the server authenticates with. | Yes |
| REDIS_PASSWORD | Configuration value read at startup. | Optional |
| CORDUM_GATEWAY | Configuration value read at startup. | Optional |
| CORDUM_TENANT_ID | Configuration value read at startup. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.