{
  "markdown": "# mcp-stripe_connect\n\nStripe MCP Pack — read-only access to Stripe data via API key.\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Tools\n\n| Tool | Description |\n|------|-------------|\n| `stripe_list_customers` | List Stripe customers. Supports pagination. |\n| `stripe_get_customer` | Get a Stripe customer by ID. |\n| `stripe_list_charges` | 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. |\n| `stripe_list_subscriptions` | 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. |\n| `stripe_get_balance` | Get the current Stripe account balance. |\n| `stripe_list_invoices` | 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. |\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"stripe_connect\": {\n      \"url\": \"https://gateway.pipeworx.io/stripe_connect/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/stripe_connect/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1476+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Stripe_connect data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 3400,
  "sha": "b3d4fb19c93e8755c7588bff62a14b077ea1fb5cb0f721cbbbb6e77f47e6c54c",
  "repo_slug": "pipeworx-io/mcp-stripe_connect",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_stripe_connect_15e29dba/readme"
}