Documentation

MCP server

Cordum exposes MCP over JSON-RPC 2.0 with two transport modes: local stdio and gateway HTTP/SSE. Use MCP inside your autonomous AI agent stack while Cordum keeps governance and policy enforcement at the control-plane layer.

stdio mode

Run `cordum-mcp` as a local process for Claude Desktop/Code. Requests are forwarded to the gateway.

Gateway HTTP/SSE mode

Expose MCP over `/mcp/sse` and `/mcp/message` for remote clients when MCP HTTP transport is enabled.

Run MCP in stdio mode

go run ./cmd/cordum-mcp --addr http://localhost:8081 --api-key "$CORDUM_API_KEY"

# Optional flags:
# --request-timeout 30s

Enable gateway HTTP/SSE mode

# Set via config service (system scope)
{
  "mcp": {
    "enabled": true,
    "transport": "http",
    "port": 3001
  }
}

# MCP routes
GET  /mcp/sse
POST /mcp/message
GET  /mcp/status

Authentication and tenancy

Use X-API-Key and X-Tenant-ID for HTTP/SSE mode.
Cross-tenant access is denied unless the auth provider explicitly grants it.
Enterprise auth provider adds multi-tenant API key + advanced RBAC capabilities.

Built-in tools

cordum_submit_job
cordum_cancel_job
cordum_trigger_workflow
cordum_approve_job
cordum_reject_job
cordum_query_policy

Built-in resources

cordum://jobs/{id}
cordum://jobs?status={status}&limit={n}
cordum://workflows/{id}/runs
cordum://workflows/{id}/runs/{runId}
cordum://audit?limit={n}
cordum://health
cordum://policies

Quick HTTP ping

curl -sS -X POST http://localhost:8081/mcp/message \
  -H "Content-Type: application/json" \
  -H "X-API-Key: $CORDUM_API_KEY" \
  -H "X-Tenant-ID: default" \
  -d '{"jsonrpc":"2.0","id":1,"method":"ping"}'

Source of truth: docs/mcp-server.md and API reference.