Skip to content

MCP server

Stripe MCP (agenticledger)

MCP server exposing Stripe API calls over Streamable HTTP with bearer token passthrough authentication.

  • Community
  • Token

Repository and documentation last checked Built from public product pages and documentation. SourcesClaim this listing

ecommerceguide summary

Stripe MCP (agenticledger) is a community MCP server that exposes Stripe API calls to AI agents for payments work. It runs over Streamable HTTP transport and authenticates with bearer token passthrough, so credentials are not stored by the server. The code is TypeScript, built on Express with the Model Context Protocol SDK, published as the stripe-mcp-http repository with no licence file and no packaged install, so you build and run it from source.

Why it stands out

Community server exposing Stripe over Streamable HTTP with bearer token passthrough instead of credentials stored by the server.

What Stripe MCP (agenticledger) does

ecommerceguide editorial
  • Exposes Stripe API calls to MCP clients over Streamable HTTP
  • Bearer token passthrough authentication, no server-side credential storage
  • Maintained by agenticledger as a community project, not by Stripe
  • TypeScript on Express, using the Model Context Protocol SDK
  • Run from source: no npm package, Docker image or hosted endpoint
  • Repository lists no licence; last pushed July 2026

How ecommerce teams could use it

ecommerceguide editorial

Illustrative scenarios written by ecommerceguide from the product's documented capabilities. They are not customer case studies.

  1. Ecommerce team taking payments through Stripe

    Connecting an MCP client to Stripe so an agent can call the payments API

    Intended outcomeThe server proxies the calls over Streamable HTTP, forwarding the caller's bearer token to Stripe

  2. Engineering team building agent tooling around an existing Stripe account

    Adding a Stripe tool server alongside other MCP servers in an agent stack

    Intended outcomeThe TypeScript Express service is built and run from the repository source, with no stored keys on the server

Who it suits

ecommerceguide editorial

Best for

You run MCP clients that support Streamable HTTP and want a Stripe connector you build and host from source with bearer token passthrough.

Probably not for

You need stdio transport, an npm or Docker install, documented client setup steps, or a licensed project maintained by Stripe itself.

Business size
Any stageNo pricing or stated audience is published; the server is self-run source code usable by any team with a Stripe account.
Verticals
B2B commerce, Digital products and memberships

Technical details

From the vendor's own pages

From the server's repository, documentation and MCP directory listings.

What an agent can do
Payments
Transport
HTTP (remote)
Authentication
TokenRepo description states bearer passthrough auth
Package
stripe-mcp-http
Language
TypeScript
Repository last updated
7 Jul 2026

Connect Stripe MCP (agenticledger)

Third-party data

Setup steps are in the repository README (opens in a new tab). We only show an install command when a source lists one.

Works with

Ecommerce platforms and services

  • Stripe logoStripe

Systems this server reads from or writes to.

Often used alongside

ecommerceguide editorial

Categories and use cases

Sources

ecommerceguide profiles are built from public product information and written for ecommerce teams. We do not test products, and paying never changes where a listing ranks.

Also listed on PulseMCP.

See something incorrect? Report an update