Circulara Observe MCP Plugin
OfficialProvides an OpenAI-format gateway for compatible hosts, enabling metered and re-priced usage through the tenant's provider keys.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Circulara Observe MCP Pluginshow me my LLM usage and cost report"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
circulara-core
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.
Workspace layout
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 |
Related MCP server: Ultimate-MCP-Server
Run
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.tsAuth (WS2)
Humans: OIDC/SSO (RS256 vs org issuer JWKS; admin via
circulara_role=adminclaim).Named agents: short-lived HS256 seat tokens minted at POST /v1/seats/:id/token (admin).
Dev mode ONLY with CIRCULARA_AUTH_MODE=dev:
Bearer dev-admin-token/dev-seat-token.Gateway (M2): per-seat credentials from POST /v1/seats/:id/gateway-credential; the host sends the credential as x-api-key to POST /gateway/anthropic/v1/messages; backend maps credential -> seat, forwards on the tenant's real key, meters per seat.
MCP plugin install (Claude Code)
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.tsHook capture (path A): wire packages/plugin/src/hook.ts as a PostToolUse hook (see file
header). The hook never fails the host tool call.
Invariants the tests enforce
Tenant isolation; append-only meter_events; admin-only agent seats (AD6).
avoided_usd == counterfactual - actual; sourcing types require the v1.1 block; M1 call_id chaining telescopes per-call savings.
Provider keys never at rest in plaintext (envelope AES-256-GCM, wrong-KEK/tamper throw); write-only API (names listed, values never returned).
Gateway: unknown credential 401; missing tenant key 503; per-seat attribution exact; registry-priced usage.
OIDC: wrong issuer rejected; dev tokens rejected outside dev mode; agent tokens expire.
Keys
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.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- FlicenseBquality-maintenanceProvides comprehensive telemetry and usage analytics for Claude Code sessions, including token usage tracking, cost monitoring, and tool usage patterns. Enables users to monitor their Claude usage with detailed metrics, warnings, and trend analysis.Last updated12
- Alicense-qualityCmaintenanceProvides a suite of tools like agent orchestration and token optimization for ClaudeLast updatedMIT
- AlicenseAqualityAmaintenanceZero-config session continuity for Claude Code. Automatically captures and restores project context across sessions using Claude Hooks.Last updated253834MIT
- Alicense-qualityAmaintenanceZero-tool-call codebase intelligence for Claude Code and MCP clients. Automatically injects the right code context, functions, callers, and call chains, before the LLM starts thinking. Replaces 4-6 grep/read round-trips with a single 5ms hook injection, cutting token usage by 3-8x.Last updated67036MIT
Related MCP Connectors
WHOOP recovery, strain, sleep and workouts in Claude via official WHOOP OAuth. Free, open source.
Cross-agent artifact workspace with provenance across Claude Code, Codex, Cursor, LangGraph.
Live SEO workflow tools for Claude Code, Codex, and AI agents.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/CircularRoute/circulara-core'
If you have feedback or need assistance with the MCP directory API, please join our Discord server