An installable MCP server for the Assurance API

pip install -e '.[assurance-mcp]'

export ASSURANCE_API_URL=http://127.0.0.1:8000   # or a real deployment
export ASSURANCE_API_KEY=...                      # optional — paid tools only

assurance-mcp

Transport is stdio by default, which is what most MCP clients expect — including Cursor's mcp.json, shown on the Cursor connector page. For a generic MCP client, point it at the assurance-mcp command directly:

{
  "mcpServers": {
    "assurance": {
      "command": "assurance-mcp",
      "env": {
        "ASSURANCE_API_URL": "http://127.0.0.1:8000",
        "ASSURANCE_API_KEY": ""
      }
    }
  }
}

pip install -e '.[neuralbridge-ai-mcp]'

export NEURALBRIDGE_API_URL=http://127.0.0.1:8000/api/v1   # or a real deployment
export NEURALBRIDGE_AI_API_KEY=...                           # optional — write tools only
export NEURALBRIDGE_AI_ACTOR=your-agent-name                 # real identity for the audit trail

neuralbridge-ai-mcp

{
  "mcpServers": {
    "neuralbridge-ai": {
      "command": "neuralbridge-ai-mcp",
      "env": {
        "NEURALBRIDGE_API_URL": "http://127.0.0.1:8000/api/v1",
        "NEURALBRIDGE_AI_API_KEY": "",
        "NEURALBRIDGE_AI_ACTOR": "your-agent-name"
      }
    }
  }
}

See docs/ai-local-setup.md for standing up a local Postgres to point this at.

Adding a route as a tool is mechanical — src/assurance/mcp/server.py is under 150 lines, one @mcp.tool() function per route calling the same _call() helper. The remaining free-tier routes (separation, bundle/manifest/declaration checks, attestation key/verify) are the natural next additions, since they need no key either. Read the source or open a PR.

Prefer plain HTTP for now? Read /developers or fetch /openapi.json directly — exactly what /llms.txt points agents at.