Connections

The metered pipe on wasted, repeated inference — Metrecept is a cog in your workflow machine. Attach once to the tools you already use; every MCP host below gets the same ten tools.

Coding agents

CursorMCP marketplace attach
Integrate Visit site
Opens Cursor and prompts authorization for Metrecept read/write access on that platform where supported.
Claude CodeTerminal MCP authorize
Integrate Visit site
Opens Claude Code and prompts authorization for Metrecept read/write access on that platform where supported.
VS CodeCopilot agent MCP
Integrate Visit site
Opens VS Code and prompts authorization for Metrecept read/write access on that platform where supported.
WindsurfCodeium MCP config
Integrate Visit site
Opens Windsurf and prompts authorization for Metrecept read/write access on that platform where supported.
ZedContext servers
Integrate Visit site
Opens Zed and prompts authorization for Metrecept read/write access on that platform where supported.

On the pipe

OpenAICompatible /v1 + BYOK
Integrate Visit site
Opens OpenAI and prompts authorization for Metrecept read/write access on that platform where supported.
AnthropicBYOK on the pipe
Integrate Visit site
Opens Anthropic and prompts authorization for Metrecept read/write access on that platform where supported.
MCPOpen agent protocol
Integrate Visit site
Opens MCP and prompts authorization for Metrecept read/write access on that platform where supported.
StripeSeats + meters
Integrate Visit site
Opens Stripe and prompts authorization for Metrecept read/write access on that platform where supported.
RedisExact-match replay
Integrate Visit site
Opens Redis and prompts authorization for Metrecept read/write access on that platform where supported.

Metrecept surfaces

Agent ShellMetrecept session demo
Integrate Visit site
Opens Agent Shell and prompts authorization for Metrecept read/write access on that platform where supported.
AnalyticsLedger + policy
Integrate Visit site
Opens Analytics and prompts authorization for Metrecept read/write access on that platform where supported.

Prefer the connections workbench? Open Connections.

1. Install the server:

pip install withohm-mcp

2. Paste your key to personalize the configs below (or grab a $0 Intermediate seat first):

Metrecept API key

Cursor

~/.cursor/mcp.json (global) or .cursor/mcp.json (project)

{
  "mcpServers": {
    "ohm": {
      "command": "ohm-mcp",
      "env": {
        "OHM_API_KEY": "sk-at-YOUR_KEY"
      }
    }
  }
}

Claude Code

One terminal command

claude mcp add ohm --env OHM_API_KEY=sk-at-YOUR_KEY -- ohm-mcp

VS Code (Copilot)

.vscode/mcp.json in your workspace

{
  "servers": {
    "ohm": {
      "type": "stdio",
      "command": "ohm-mcp",
      "env": {
        "OHM_API_KEY": "sk-at-YOUR_KEY"
      }
    }
  }
}

Windsurf

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "ohm": {
      "command": "ohm-mcp",
      "env": {
        "OHM_API_KEY": "sk-at-YOUR_KEY"
      }
    }
  }
}

Zed

settings.json (zed: open settings)

{
  "context_servers": {
    "ohm": {
      "source": "custom",
      "command": "ohm-mcp",
      "args": [],
      "env": {
        "OHM_API_KEY": "sk-at-YOUR_KEY"
      }
    }
  }
}

On the stack — Neon

Neon

Serverless Postgres — branches, previews, scale-to-zero compute for apps and agents.

Neon holds application state (and, in beta, a branch-scoped AI Gateway). Metrecept is middleware governance on mechanical repeats — exact-replay tips on the same PR slug, Promote-on-merge, HIT meters. Complementary, not competing.

Compose with Neon neon.tech

What Metrecept can access

The connection is deliberately narrow. Once attached, Metrecept can reach exactly this — nothing more:

Prompts you route through it. Chat calls you send via ohm_chat pass through the pipe so identical prompts can replay from cache. Nothing else on your machine is read.
Public web pages only. ohm_fetch_web fetches public URLs under the compliance policy — robots-gated, PII-redacted, and limited to declared purposes. Ask ohm_policy for the current list.
Your usage meters. ohm_usage, ohm_savings, ohm_models, and ohm_providers read your own tenant's meters and routing status. Read-only.
Your cache inventory. ohm_cache_trees and ohm_cache_inventory list tips and cached digests (model, TTL, size) — metadata only, never message content.
Keys stay yours. BYOK (bring your own keys): provider keys ride the X-Ohm-Upstream-Key header per request and are not stored.

Full detail in Security and Legal & compliance.

Coming to the grid

Hosted remote MCP. One URL attach (no local install) over streamable HTTP.
Slack app. Usage alerts and fetch summaries where your team talks.
Automation platforms. Zapier / Make connectors for no-code pipelines.

Full integration guide · Command catalog · Optimized usage