MCP Hub
Back to servers

Cordum_io

The Control Plane for Autonomous AI Enforce policy before execution, require human approvals where risk demands it, and keep a full audit trail — from first action to final result.

glama
Stars
460
Forks
20
Updated
Mar 23, 2026
Validated
Mar 25, 2026

Cordum

Cordum

Know What Your AI Agents Are Doing. Before They Do It.
The Source-Available Agent Control Plane for Governance, Safety, and Trust.

License Release Discord CAP Protocol


The Problem: The Agent Risk Gap

Enterprises are rushing to deploy Autonomous AI Agents, but they're hitting a wall of risk. According to Gartner, 74% of enterprises see AI agents as a new attack vector, and over 40% of agentic AI projects will be canceled due to inadequate risk controls.

The current landscape leaves teams with a choice:

  1. Restrict agents to simple, low-value read-only tasks.
  2. Accept the risk of autonomous agents taking destructive, unmonitored actions.

Without a dedicated governance layer, you're flying blind:

  • No visibility: You don't know what your agents are doing until after they do it.
  • No safety rails: There's no way to intercept dangerous operations before they execute.
  • No human-in-the-loop: Sensitive actions happen without manual oversight.
  • No audit trail: When things go wrong, you can't reconstruct the chain of thought.

The Solution: Cordum Agent Control Plane

Cordum is an Agent Control Plane that provides a deterministic governance layer for probabilistic AI minds. It allows you to define, enforce, and audit the behavior of your Autonomous AI Agents across any framework or model.

graph TB
    subgraph CP [AGENT CONTROL PLANE]
        direction LR
        G[API Gateway] --- S[Scheduler] --- SK[Safety Kernel]
        S --- WE[Workflow Engine]
    end
    
    subgraph AGENTS [AUTONOMOUS AGENT POOLS]
        direction LR
        A1[Financial Ops]
        A2[Data Science]
        A3[Customer Service]
    end
    
    CP -->|Governed Jobs| AGENTS
    AGENTS -->|Audit Trail| CP

nWwQVRVqwlZKeRbBZvkSof-img-2_1771930624000_na1fn_ZGFzaGJvYXJkLXByZXZpZXctZGFyaw

Governance Across the Lifecycle

Cordum's Before/During/Across framework provides exhaustive control over your agent operations:

graph LR
    subgraph BEFORE [1. BEFORE - Governance]
        P[Policy Evaluation] --> S[Safety Gating]
        S --> H[Human Approval]
    end
    subgraph DURING [2. DURING - Safety]
        M[Real-time Monitoring] --> C[Circuit Breakers]
        C --> A[Live Approvals]
    end
    subgraph ACROSS [3. ACROSS - Observability]
        F[Fleet Health] --> T[Audit Trail]
        T --> O[Optimization]
    end
    BEFORE --> DURING
    DURING --> ACROSS
  • BEFORE (Governance): Define declarative policies that evaluate job requests before an agent executes. Trigger safety kernel checks, throttle risky actions, or flag operations for human approval.
  • DURING (Safety): Real-time visibility into active agent runs. Monitor progress, handle step-level approvals, and enforce timeouts or circuit breakers on the fly.
  • ACROSS (Observability): Manage your entire fleet from a single control plane. Aggregate audit trails, track capability-based routing, and observe agent pool health in real-time.

Quickstart

Prerequisites: Docker (4GB+ RAM), Docker Compose, Go 1.24+

git clone https://github.com/cordum-io/cordum.git
cd cordum
./tools/scripts/quickstart.sh

That's it. The script auto-creates .env, generates API keys and Redis password, builds all services, and runs health checks. No manual configuration needed.

Dashboard: http://localhost:8082 Login: admin / admin123 (change in .envCORDUM_ADMIN_PASSWORD)

Manual setup (without quickstart script)
cp .env.example .env
# Edit .env: set CORDUM_API_KEY (or generate: openssl rand -hex 32)
export CORDUM_API_KEY="your-key-here"
go run ./cmd/cordumctl up
open http://localhost:8082

Ports

PortService
8082Dashboard
8081API Gateway (HTTPS)
9080gRPC Gateway
4222NATS
6379Redis
9092Gateway Metrics
9093Workflow Engine Health
50051Safety Kernel (gRPC)
50400Context Engine (gRPC)

After Setup

# Submit a test job
curl -sS --cacert ./certs/ca/ca.crt \
  -X POST https://localhost:8081/api/v1/jobs \
  -H "X-API-Key: $CORDUM_API_KEY" -H "X-Tenant-ID: default" \
  -H "Content-Type: application/json" \
  -d '{"topic":"job.default","context":{"prompt":"hello"}}'

# Stop the stack
docker compose down

# View logs
docker compose logs -f api-gateway

Troubleshooting

IssueFix
Port already in usedocker compose down then retry, or check lsof -i :8082
Docker out of memoryAllocate at least 4 GB RAM to Docker Desktop
Can't login to dashboardDefault credentials: admin / admin123
TLS/SSL cert errorsRemove ./certs/ and re-run — certs auto-regenerate
openssl not foundNot needed — quickstart.sh auto-generates keys without it
Go build failsRequires Go 1.24+ — check with go version
Stale config after changesredis-cli DEL cfg:system:default then restart

For detailed troubleshooting, see docs/troubleshooting.md.

Key Features

nWwQVRVqwlZKeRbBZvkSof-img-4_1771930611000_na1fn_d29ya2Zsb3ctdmlzdWFsaXphdGlvbg

Governance FeatureWhy It Matters for Enterprise
Safety GatingPrevents agents from executing destructive or unauthorized actions before they occur.
Output QuarantineAutomatically blocks PII leaks, secrets, or hallucinated results from reaching the client.
Human-in-the-LoopMandates human oversight for high-risk operations (e.g., financial transfers, prod access).
Pool SegmentationEnsures sensitive data only reaches agents in trusted environments.
Deterministic AuditProve exactly why a decision was made with a full chain-of-thought audit trail.
Governance PoliciesDeclarative YAML-based rules that map enterprise risk to agent behavior.
Policy SimulatorTest your governance rules against historical data before rolling them out to production.

Architecture

cordum/
├── cmd/                          # Service entrypoints + CLI
│   ├── cordum-api-gateway/       # API gateway (HTTP/WS + gRPC)
│   ├── cordum-scheduler/         # Scheduler + safety gating
│   ├── cordum-safety-kernel/     # Policy evaluation
│   ├── cordum-workflow-engine/   # Workflow orchestration
│   ├── cordum-context-engine/    # Optional context/memory service
│   └── cordumctl/                # CLI
├── core/                         # Core libraries
│   ├── controlplane/             # Gateway, scheduler, safety kernel
│   ├── context/                  # Context engine implementation
│   ├── infra/                    # Config, storage, bus, metrics
│   ├── protocol/                 # API protos + CAP aliases
│   └── workflow/                 # Workflow engine
├── dashboard/                    # React UI
├── sdk/                          # SDK + worker runtime
├── cordum-helm/                  # Helm chart
├── deploy/k8s/                   # Kubernetes manifests
└── docs/                         # Documentation

Documentation

DocDescription
System OverviewArchitecture and data flow
Core ReferenceDeep technical details
Docker GuideRunning with Compose
Agent ProtocolCAP bus + pointer semantics
MCP ServerMCP stdio + HTTP/SSE integration
Pack FormatHow to package agent capabilities
Local E2EFull local walkthrough
Production GuideTLS, HA, backups, incident runbooks

Protocol: CAP — The Open Standard for Agent Governance

Cordum implements CAP (Cordum Agent Protocol), an open protocol specifically designed for distributed AI agent governance. CAP provides a unified interface for defining agent capabilities, submitting jobs, and enforcing safety policies across heterogeneous agent pools.

CAP vs. MCP: Why You Need Both

While both are essential, they solve different parts of the agent stack:

ProtocolFocusLevelResponsibility
MCP (Model Context Protocol)Tool CallingLocalHow a model interacts with a tool.
CAP (Cordum Agent Protocol)GovernanceNetworkHow an agent is governed within an enterprise.
  • MCP is for within the agent — it defines how a model calls local tools.
  • CAP is for above the agent — it defines the governance control plane for the entire agent fleet.

Use CAP for high-level orchestration and safety gating, and MCP inside your agents for fine-grained tool integration.

Read the full deep dive: MCP vs CAP: Why Your AI Agents Need Both Protocols

MCP Server

Cordum includes an MCP server framework with:

  • Standalone stdio mode via cmd/cordum-mcp (for Claude Desktop/Code local integration)
  • Gateway HTTP/SSE mode via /mcp/message and /mcp/sse (when mcp.enabled=true)

See docs/mcp-server.md for setup, auth headers, and client configuration examples.

SDK

The Go SDK makes it easy to build CAP-compatible workers:

import (
    "log"

    "github.com/cordum/cordum/sdk/runtime"
)

type Input struct {
    Prompt string `json:"prompt"`
}

type Output struct {
    Summary string `json:"summary"`
}

func main() {
    agent := &runtime.Agent{Retries: 2}

    runtime.Register(agent, "job.summarize", func(ctx runtime.Context, input Input) (Output, error) {
        // Your agent logic here
        return Output{Summary: input.Prompt}, nil
    })

    if err := agent.Start(); err != nil {
        log.Fatal(err)
    }
    select {}
}

SDKs: Go (stable) | Python | Node

Integration Packs

Extend Cordum with 26+ integration packs for Slack, GitHub, AWS, Jira, and more. Each pack is a CAP-native worker with policy-gated workflows. Browse the catalog at packs.cordum.io.

Community

Enterprise

Cordum Enterprise adds:

  • SSO/SAML integration
  • Advanced RBAC
  • SIEM export
  • Priority support

Contact us for pricing.

Governance

Cordum follows a transparent governance model with a protocol stability pledge, maintainer structure, and clear decision-making process. See GOVERNANCE.md for details including:

  • Protocol Stability: CAP v2 wire format frozen until February 2027
  • Security: SECURITY.md for vulnerability reporting
  • Versioning: Semantic versioning with deprecation policy

Roadmap

See ROADMAP.md for the full feature roadmap, completed milestones, and planned work.

Changelog

See CHANGELOG.md for a detailed log of all changes by version.

Contributing

We welcome contributions! See CONTRIBUTING.md for guidelines.

License

Licensed under Business Source License 1.1 (BUSL-1.1).

  • Self-host and use internally: Permitted
  • Modify and contribute back: Permitted
  • Offer as a competing hosted service: Not permitted
  • Change Date: January 1, 2029 — automatically converts to Apache License 2.0

See LICENSE for full terms.


Ready to govern your AI agents?
cordum.io · CAP Protocol · Packs · Discord

⭐ Star this repo if Cordum helps you deploy agents safely

Reviews

No reviews yet

Sign in to write a review