Stripe

Overview

A payments MCP listed through mcpmeter exposes the publisher's API as a set of tools an agent can reason about: customers, payment intents, subscriptions, refunds, invoices, and a handful of read-only inspections. There is no SDK to import, no ngrok tunnel, no webhook endpoint to stand up. The agent calls a tool, money moves, the publisher sends an event back, the agent reads it.

mcpmeter sits between agent and publisher: authenticate the bearer key, forward the JSON-RPC body unchanged, count tool-call envelopes in the response, write a ledger row, return the response unchanged. The publisher never sees the consumer's API key. The consumer never sees the publisher's secret. The proxy is open source so the meter can be inspected.

Tools

Twenty-one tools, grouped where Stripe groups them. Read tools are read-only against the live API; Write tools mutate state and respect idempotency keys.

Integration

Drop the proxy URL and your bearer key into any MCP-compatible agent's config. Below: the configuration block for Claude Desktop. The same shape works in Cursor, Cody, the OpenAI Apps SDK, and OpenRouter with a one-line difference.

{
  "mcpServers": {
    "stripe": {
      "url":     "https://proxy.mcpmeter.com/stripe",
      "headers": {
        "Authorization": "Bearer mcpm_live_…"
      }
    }
  }
}

The proxy authenticates the bearer token, looks up the price, forwards the call to the upstream MCP, returns the response unchanged, and writes a usage record. The publisher never sees the consumer's API key. The consumer never sees the publisher's secret.

Pricing

The publisher sets the per-call price. Below: a representative tier ladder for layout reference. mcpmeter takes a fixed percentage; the publisher receives the rest.

Publisher's own card-processing fees pass through unchanged. mcpmeter's per-call price covers the proxy and the meter; it does not duplicate what the publisher already charges.

Trust & Compliance