LabscoMCP early access ↗
cordum-ioMCP SERVER · OFFICIAL PROJECT

Cordum.io

Ask what your agents did, what is waiting for approval, and whether the audit trail is intact — in plain language.

by cordum-io ↗Agent Guardrails, Content Safety & Audit✓ Official

LABSCO SUMMARY

Fourteen tools only look; the seven that change things wait, by default, for a human to approve each call.

The discovery tools tell you what happened and what is pending. The mutating ones, such as cordum_create_workflow, cordum_install_pack and cordum_update_policy_bundle, return an approval id first and run only after someone approves in the dashboard or with cordumctl mcp approve. Every call lands in the per-tenant audit chain as an event, and cordum_audit_verify will tell you whether that chain has gaps — which is the point of pointing an assistant at it in the first place.

What it is

The MCP surface of Cordum, an agent control plane: read-only discovery tools over jobs, workflow runs, packs, topics, workers, agent identities, approvals and the audit chain, plus seven approval-gated tools that create workflows, install or remove packs, register agents and change policy.

What you get

  • cordum_list_jobs and cordum_get_job — what ran, filtered by state or topic, and the full record for one job including its policy decision and retry history
  • cordum_list_runs, cordum_get_run and cordum_run_timeline — workflow runs with graph state, and an ordered event timeline for tracing where one got stuck
  • cordum_list_workflows, cordum_list_packs and cordum_list_topics — the definitions, installed integration packs, and registered job topics
  • cordum_list_workers and cordum_list_agents — registered workers with capabilities and last-seen, plus configured agent identities with their allowed tools and risk tier
  • cordum_list_pending_approvals — what is waiting on a human, defaulting to pending
  • cordum_audit_query and cordum_audit_verify — search the audit chain, and walk the Merkle chain to report ok, compromised or partial
  • cordum_status — one health snapshot of the platform components, queue depth and active workers
  • List tools page at 50 by default and up to 500, returning an opaque cursor to resume

Requirements

A running Cordum stack — the quickstart script or docker compose brings up the gateway, scheduler, safety kernel and the rest — and a CORDUM_API_KEY. The MCP server runs standalone over stdio from cmd/cordum-mcp, or through the gateway at /mcp/message and /mcp/sse when mcp.enabled is true. Calls are tenant-scoped; cross-tenant queries on the audit tools are admin-only.

Setup effort

Build from source — git clone https://github.com/cordum-io/cordum.git

See installation options