Stripe

This connector bridges Stripe's official remote MCP server (https://mcp.stripe.com). Stripe's own server provides the tools: a generic way to search, inspect, read and write almost any Stripe API method (stripe_api_search, stripe_api_details, stripe_api_read, stripe_api_write), account info, analytics and reports, a balance summary, the Stripe documentation search and an implementation planner. AnythingMCP puts them behind your MCP endpoint with OAuth for Claude and ChatGPT, per-tool roles, the audit log and response mapping, next to your other systems.

The tools come from the server. At install AnythingMCP asks Stripe's server which tools it has, so you get exactly the set Stripe offers today. When Stripe adds tools, open the connector and click Discover tools to pick them up.

Setup (about 5 minutes):

1. Decide on the environment first. A sandbox returns simulated objects and moves no money; live mode works on real customers and payments. Each has its own keys, and objects in one are invisible to the other. Start in a sandbox.
2. In the Stripe Dashboard open Developers > API keys (https://dashboard.stripe.com/apikeys) in that environment and click Create restricted key. When Stripe asks what the key is for, choose Authorizing agent access to your account: this makes it an agent API key (it shows the Agent badge).
3. Give it the least privilege the AI needs: set each resource to None, Read or Write, and leave everything else at None. For reporting only, Read on the resources you want to analyse is enough (analytics need Data > Metrics: Read and Reporting: Read). Complete the two-factor check and copy the key; Stripe shows it once.
4. Paste it into STRIPE_AGENT_KEY and install. The key is sent as a Bearer token and stored encrypted.
5. Check Settings > MCP and CLI access (https://dashboard.stripe.com/settings/mcp-and-cli-access): an administrator can switch MCP access off for the whole team, separately for live mode and sandboxes. It must be on for the environment of your key.

Keys Stripe accepts: from 31 October 2026 Stripe's MCP server refuses full secret keys (sk_live_, sk_test_) and restricted keys without the Agent tag, answering 401. Use an agent key (rk_live_... or rk_test_...) created as above.

Safety:

• stripe_api_write installs switched off: it can call any write method the key permits, including refunds, subscription cancellations, invoice voids and deletions. Turn it on per workspace when the AI should change data, and keep the key's permissions narrow so that the key, not the prompt, is the real boundary.
• Approval rules: agent keys are subject to Stripe's approval rules (Settings > Approvals). For sensitive actions such as refunds, payouts and account changes Stripe does not execute the call; it returns an approval URL. AnythingMCP passes that URL through untouched. A person opens it, reviews the request and clicks Approve in the Dashboard within 24 hours, then tells the agent to retry; the retry goes through without another confirmation.
• send_stripe_feedback installs switched off, because its text goes to Stripe.
• Outputs contain customer personal data (names, emails, addresses). Card numbers never pass through: Stripe returns at most the brand and last four digits. Limit who can use this connector with roles.

Connect platforms: to act on a connected account instead of your platform account, open the connector editor and add the header Stripe-Account: acct_... with the connected account ID, and give the agent key only the connected-account permissions it needs. Analytics and reports read your own account only.

Working with it: start with get_stripe_account_info to confirm the account and mode, then stripe_api_search to find a method, stripe_api_details for its parameters and stripe_api_read to run it. Ask stripe_analytics for MRR, churn or subscriber counts rather than letting the AI compute them from raw objects. A 401 means a missing, expired or non-agent key; a 403 or permission error means the key lacks a permission for that resource (edit the key in the Dashboard); if nothing connects at all, check that MCP access is on for that environment and that your network allows mcp.stripe.com.

Account info: stripe_get_stripe_account_info needs the key to read Accounts (Connect group, Read). Without it Stripe answers 'Permission denied' and every other read still works.