Server data from the Official MCP Registry
Circulara Observe MCP plugin - meters your AI agents' token spend and carbon, free tier.
Circulara Observe MCP plugin - meters your AI agents' token spend and carbon, free tier.
Valid MCP server (1 strong, 0 medium validity signals). No known CVEs in dependencies. ⚠️ Package registry links to a different repository than scanned source. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.
7 files analyzed · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: CIRCULARA_BACKEND_URL
Environment variable: CIRCULARA_TENANT_ID
Environment variable: CIRCULARA_TOKEN
Environment variable: CIRCULARA_SEAT_ID
Environment variable: CIRCULARA_USER_ID
Add this to your MCP configuration file:
{
"mcpServers": {
"ai-circulara-plugin": {
"env": {
"CIRCULARA_TOKEN": "your-circulara-token-here",
"CIRCULARA_SEAT_ID": "your-circulara-seat-id-here",
"CIRCULARA_USER_ID": "your-circulara-user-id-here",
"CIRCULARA_TENANT_ID": "your-circulara-tenant-id-here",
"CIRCULARA_BACKEND_URL": "your-circulara-backend-url-here"
},
"args": [
"-y",
"@circulara/plugin",
"-y",
"-p",
"@circulara/plugin",
"circulara-mcp"
],
"command": "npx"
}
}
}From the project's GitHub README.
Circulara Observe tier: per-tenant backend + MCP plugin. Sprints 1-4: WS0 (scaffold), WS6 (pricing registry), WS1 (MCP plugin), WS2 (auth + BYO keys + gateway), WS3 (telemetry pipeline: normalize -> re-price -> append; free-tier cap; OpenAI-format gateway for Cursor-class hosts), WS4 (meter compute: registry pricing, energy/CO2e ranges with confidence labels, per user/team/module/month report), WS5 (Observe dashboard + savings-potential report + monthly statement, server-rendered, Ledger Light brand tokens; seed a demo tenant with packages/backend/scripts/seed-demo.ts and open the printed /dashboard URL). Architecture: /outputs/reports/architecture_v1.md (AD1-AD6, rev 2026-07-07) + the sourcing addendum (AD7-AD12).
Pricing placement: the meter owns money. All three capture paths (hook, tool, gateway) deliver tokens + model; pricing happens ONCE in the WS3/WS4 pipeline from the approved registry snapshot. Client-submitted observe events are re-priced server-side; client cost is a hint, never the booked number. Engine-computed events (reuse/sourcing, waves 3+) carry their own math and are born meter-priced in-process.
| Package | What |
|---|---|
| packages/schema | THE event schema (zod, v1.0+v1.1, AD4/AD12 incl. call_id + M1 stacking rule). Single source of truth for backend intake AND plugin emission |
| packages/backend | Per-tenant backend: tenancy/isolation (PGlite+pgvector dev, per-tenant Postgres prod), append-only meter, seats (AD6), WS2 auth (OIDC + short-lived agent tokens + dev mode), BYO provider keys envelope-encrypted at rest, gateway metering mode (AD3-B, M2 per-seat credentials), object store, WS6 pricing registry + carbon coefficients |
| packages/plugin | MCP plugin (AD3 path C tools: circulara_report, circulara_status) + Claude Code PostToolUse hook (path A observe capture). Validates events against the shared schema BEFORE sending |
npm install
npm test # all workspaces: backend 11 + plugin 4 (in-memory, no keys)
npm run typecheck
npm run dev # backend on 127.0.0.1:8787 (CIRCULARA_AUTH_MODE=dev|oidc)
# WS6 registry flow (human approves diffs, D12):
npm run registry -- update|approve|show
# WS2 LIVE smoke (deliberate; ~cents on the configured Anthropic key):
cd packages/backend && npx tsx scripts/live-smoke.ts
circulara_role=admin claim).Bearer dev-admin-token / dev-seat-token.claude mcp add circulara \
-e CIRCULARA_BACKEND_URL=http://127.0.0.1:8787 \
-e CIRCULARA_TENANT_ID=<uuid> -e CIRCULARA_TOKEN=<bearer> \
-e CIRCULARA_SEAT_ID=<uuid> -e CIRCULARA_USER_ID=<sso-subject> \
-- npx tsx <repo>/packages/plugin/src/server.ts
Hook capture (path A): wire packages/plugin/src/hook.ts as a PostToolUse hook (see file
header). The hook never fails the host tool call.
Runtime keys come ONLY from the external env file via loadSecret() (path in src/config.ts, names in /context/api.md): CIRCULARA_MASTER_KEY (envelope KEK), CIRCULARA_AGENT_TOKEN_SECRET (agent JWTs), tenant provider keys via the API. Never hardcoded, never logged, never committed.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.