Stripe Connect

What Stripe_connect does

Stripe_connect gives MCP-compatible agents read-only access to selected Stripe account data. Its tools cover customer records, payment charges, subscriptions, invoices, and the current account balance. The integration is intended for inspection and reporting: it does not expose operations for creating, updating, canceling, or deleting Stripe resources.

Customer lookups support both collection and individual-record access. Charge results can include the charge identifier, amount, currency, status, and timestamp. Subscription results identify the customer, plan or price items, subscription status, and the current billing period. Invoice results include the invoice identifier, amount due, due date, and payment status.

How it works

The hosted MCP endpoint is available at https://gateway.pipeworx.io/stripe_connect/mcp. MCP clients can connect to that URL directly. The endpoint lists the Stripe pack tools along with shared Pipeworx gateway tools, including routing and discovery capabilities. A full Pipeworx gateway endpoint is also available when an agent needs direct access to tools from other packs.

The same service can be run locally through the @pipeworx/mcp-stripe_connect npm package. An MCP client starts the package with npx; the bridge forwards calls to the hosted gateway, so network access is still required. Anonymous use is limited to 50 calls per day, while a free Pipeworx account increases the allowance to 200 calls per day. Authenticated calls use a Pipeworx API key as a Bearer token and are metered through the gateway.

Setup and configuration

For a hosted connection, add the MCP URL to the client configuration:

{
  "mcpServers": {
    "stripe_connect": {
      "url": "https://gateway.pipeworx.io/stripe_connect/mcp"
    }
  }
}

For the local bridge, configure the npm package as a stdio server:

{
  "mcpServers": {
    "stripe_connect": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-stripe_connect"]
    }
  }
}

Add PIPEWORX_API_KEY under the server's env object to authenticate the bridge with Pipeworx. Set PIPEWORX_META_TOOLS=1 if the local bridge should also list the shared gateway tools. Stripe requests use the caller's own Stripe secret or restricted key through the _apiKey argument rather than a key supplied by Pipeworx.

Tools and capabilities

• stripe_list_customers lists Stripe customers with pagination support.
• stripe_get_customer retrieves a customer by ID.
• stripe_list_charges lists payment charges, optionally filtered by customer, with limits from 1 to 100.
• stripe_list_subscriptions filters subscriptions by customer or status, including active, canceled, past due, trialing, and unpaid; limits range from 1 to 100.
• stripe_get_balance returns the current Stripe account balance.
• stripe_list_invoices filters invoices by customer and supported statuses: draft, open, paid, void, or uncollectible.

Limitations and notes

All access is read-only. The local npm bridge has no offline mode and requires network access to the Pipeworx gateway. Pack-specific hosted connections also expose shared Pipeworx meta-tools, so the number of tools reported by tools/list can exceed the six Stripe tools listed here. The connection's initialization response defines the exact scope for that connection.