> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spojit.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Stripe

> Connect to Stripe's hosted MCP server for full Stripe API access: customers, charges, subscriptions, products, and more.

The Stripe connector lets your workflows talk to [Stripe's hosted MCP server](https://mcp.stripe.com), a remote MCP endpoint maintained by Stripe that exposes their full API surface (customers, charges, subscriptions, products, invoices, refunds, and more).

<Note>
  Spojit does not curate the tool list; Stripe does. For the live set of tools and their parameters, see the [Stripe MCP documentation](https://docs.stripe.com/mcp).
</Note>

<Snippet file="connection-note.mdx" />

## Connection setup

<Steps>
  <Step title="Create a restricted API key (recommended)">
    Sign in to the [Stripe Dashboard](https://dashboard.stripe.com/apikeys), open **Developers → API keys**, and click **Create restricted key**.

    Restricted keys let you grant only the permissions your workflows actually need (e.g. **Read** on Customers, **Write** on Refunds). Stripe strongly recommends this over your full secret key, since an agent with a full key can do anything in your account, including issuing refunds and creating charges.

    If you absolutely need full access, you can use a standard secret key (`sk_live_...` or `sk_test_...`), but treat it like a password.
  </Step>

  <Step title="Add the connection in Spojit">
    Go to **Connections** in Spojit, click **Add Connection**, select **Stripe (Official MCP)**, and paste the key into the **Secret Key** field.

    Use a **test-mode key** (`sk_test_...` or `rk_test_...`) while you're building workflows, then swap to a live-mode key when you're ready to go to production.
  </Step>
</Steps>

## Caveats

* **This is the full Stripe API.** Stripe's hosted MCP exposes their entire surface, including destructive operations (refunds, subscription cancellation, customer deletion). Pair it with a restricted key whose scopes match what your workflows actually do, and prefer test-mode keys during development.
* **Test vs live mode is decided by the key.** There is no separate "environment" field in the connection; the prefix on the key (`sk_test_` vs `sk_live_`) is what determines which Stripe environment the calls land in. Use separate Spojit connections for test and live.
* **The key represents your account.** A standard secret key has full Stripe API access; a restricted key has whatever scopes you grant when creating it. Treat both like passwords.
* **MCP endpoint is hosted by Stripe.** Availability, rate limits, and the exact tool surface are determined by Stripe. Outages and breaking changes are upstream.

## When to use this vs the Spojit Stripe connector

Spojit offers a separate, curated Stripe connector with a smaller, opinionated tool set tuned for common workflows. Use this **Stripe (Official MCP)** connector when:

* You need access to a Stripe API the curated connector doesn't expose
* You want the broadest possible surface for an AI agent to work with

Use the **Spojit Stripe** connector when you want a tighter, lower-token, opinionated set of tools.

## Tools

For the current list of tools and their parameters, see [Stripe's MCP documentation](https://docs.stripe.com/mcp).