Ordo

Developers

Live

MCP server: agents that keep promises.

Ordo runs a Model Context Protocol server so agents can ask what is owed and propose commitments they notice. The tools sit on the same rules as the API: an agent proposes, and a person confirms in Ordo unless an admin allowed its key to confirm.

Endpoint

POST https://api.ordo.app/mcp, Streamable HTTP transport, stateless (no sessions, no server-initiated stream). Authenticate with an Ordo API key as a Bearer token; create one in Settings → Developers with the scopes the agent needs. MCP calls count toward the same rate limits and monthly allowance as the API.

Give the key an agent name (for example claude-desktop) so the audit log shows which agent did what.

Claude Code

Terminal
claude mcp add --transport http ordo https://api.ordo.app/mcp --header "Authorization: Bearer $ORDO_API_KEY"

Claude Desktop

Add this to claude_desktop_config.json, put your key in ORDO_API_KEY, and restart Claude Desktop. It uses mcp-remote to bridge to the HTTP server, so Node.js needs to be installed.

claude_desktop_config.json
{
  "mcpServers": {
    "ordo": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.ordo.app/mcp",
        "--header",
        "Authorization:Bearer ${ORDO_API_KEY}"
      ],
      "env": {
        "ORDO_API_KEY": "ordo_sk_…"
      }
    }
  }
}

Tools

ToolScopeWhat it does
list_commitmentsreadList commitments, newest first. Filter by state, owner (a user id or `me`) or requester.
what_do_i_owereadOpen commitments owned by the key's person: overdue, due in the next 48 hours, then the rest.
get_commitmentreadOne commitment by its id or the proposal id it came from.
propose_commitmentproposePropose a commitment someone made. It waits in the review queue for a person.
capture_conversationproposeSend an email thread, chat or meeting notes. Ordo proposes the commitments in it.
confirm_commitmentconfirmApprove a proposal. Works only if an admin allowed this key to confirm.
mark_fulfilledproposeSay a commitment was kept. Applied with confirm rights; otherwise proposed for approval.

Read tools are marked read-only. When a tool is refused (a missing scope, or a change that needs a person) it returns a tool error in plain words, so the agent can tell its user what to do next, such as approving the proposal in Ordo.

Other clients

Any MCP client that speaks Streamable HTTP and can send a header works. To check the key and connection by hand, send an initialize request; a JSON reply naming the ordo server means you are connected.

Initialize
curl https://api.ordo.app/mcp \
  -H "Authorization: Bearer $ORDO_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{ "jsonrpc": "2.0", "id": 1, "method": "initialize", "params": { "protocolVersion": "2025-06-18", "capabilities": {}, "clientInfo": { "name": "curl", "version": "1" } } }'

API version 2026-11-17. Breaking changes are versioned; we email key holders before they ship. Request access.

Start free

Try commitment infrastructure on one conversation.

Paste one email thread. Ordo proposes the next steps, and nothing happens until you confirm.