Provides tools for reading Stripe data including customers, charges, subscriptions, balance, and invoices.
Click on "Deploy 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., "@Stripe Connect MCP Server show me my latest 5 charges"
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.
Stripe MCP Pack — read-only access to Stripe data via API key.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
Tool | Description |
| List Stripe customers. Supports pagination. |
| Get a Stripe customer by ID. |
| List Stripe payment charges for your account, optionally filtered by customer ID. Returns charge ID, amount, currency, status, and timestamp. Supports limit (1-100) pagination. |
| List subscriptions on a Stripe account via the Stripe API (api.stripe.com/v1/subscriptions), authenticated with a Stripe secret or restricted key passed as _apiKey, with optional customer id and status filters (active, canceled, past_due, trialing, unpaid) and a limit of 1-100. Returns each subscription id, customer, price and plan items, status, and current period start and end. Answers who is subscribed to a Stripe billing plan and on what terms. |
| Get the current Stripe account balance. |
| List Stripe invoices, optionally filtered by customer ID and/or status (draft, open, paid, void, uncollectible). Returns invoice ID, amount due, due date, and payment status. |
Related MCP server: mcp-paypal
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"stripe_connect": {
"url": "https://gateway.pipeworx.io/stripe_connect/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/stripe_connect/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Stripe_connect data" })The gateway picks the right tool and fills the arguments automatically.
MIT
This server cannot be deployed
Read-only SaaS business intelligence from GA4, Stripe, and Google Search Console.
Read-only access to your Reporting Ninja marketing and analytics data across 20+ ad platforms.
Read-only Search Console analytics, URL inspection, indexing diagnostics, and sitemaps.
Read-only revenue, subscriptions, customers, and experiments tools for ZeroSettle accounts.
