How to Connect Stripe to Meta Muse — via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Stripe, paste your credentials, mint an MCP API key — done. No Docker, no git clone, no local server.

Stripe + Meta Muse

Look up customers, payments, invoices and subscriptions, ask for MRR and churn, and (when you allow it) create invoices, payment links or refunds in Stripe from Claude, ChatGPT or Copilot through Stripe's official MCP server.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

STRIPE_AGENT_KEY

Step 1 — Get credentials

AnythingMCP bridges Stripe's official remote MCP server (https://mcp.stripe.com). The tools come from Stripe: at install AnythingMCP asks Stripe's server for its current tool list, so the table below is a snapshot. When Stripe adds tools, open the connector and click Discover tools. Stripe's server accepts an OAuth sign-in or an agent API key; this connector signs in with an agent key, the option Stripe names for applications that need their own, lasting access.

1. Pick 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, in that environment, open Developers > API keys (dashboard.stripe.com/apikeys) and click Create restricted key. When Stripe asks what the key is for, choose Authorizing agent access to your account: the key becomes an agent API key and 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, Read on the resources you want to analyse is enough, which also gives you a read-only connector. stripe_analytics needs Data > Metrics: Read and Reporting: Read; stripe_get_stripe_account_info needs Accounts (Connect group) Read, and without it only that tool answers "Permission denied". Complete the two-factor check and copy the key: Stripe shows it once.
4. Open Settings > MCP and CLI access (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.
5. In AnythingMCP, install Stripe from the catalog and paste the key into STRIPE_AGENT_KEY (rk_test_... or rk_live_...). It is stored encrypted and sent to Stripe as a Bearer token.

Which keys work: 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 created as above.

Writes are off until you switch them on: stripe_api_write installs switched off. It can call any write method the key permits, including refunds, subscription cancellations, invoice voids and deletions. Switch it on in the connector only when the AI should change data, and keep the key's permissions narrow, so that the key, not the prompt, is the real boundary. Stripe's approval rules (Settings > Approvals) apply to agent keys: for sensitive actions such as refunds, payouts and account changes Stripe does not run the call but returns an approval URL. A person opens it, clicks Approve in the Dashboard within 24 hours and asks the AI to retry. stripe_send_stripe_feedback also installs switched off, because its text goes to Stripe; you can switch it on.

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

First calls: start with stripe_get_stripe_account_info to confirm the account and the 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 instead of letting the AI add up raw objects.

If something fails: a 401 means a missing, expired or non-agent key; a 403 or a permission error means the key lacks a permission for that resource (edit the key in the Dashboard); if nothing connects, check that MCP access is on for that environment and that your network allows mcp.stripe.com. Responses contain customer personal data such as names, emails and addresses; card numbers never pass through, Stripe returns at most the brand and the last four digits. Limit who can use this connector with roles.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Muse

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Muse adds remote MCP servers as custom connectors and signs in to them with OAuth.

1. In Muse, open Settings → Connectors and choose Add custom connector.
2. Paste the MCP server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID.
3. Muse opens the AnythingMCP sign-in page: sign in and approve access.
4. In a chat, ask Muse for something that needs the Stripe tools.

You can also set it up from a chat, on the web, in the iOS and Android apps or in WhatsApp. Send Muse this message:

Create a Custom Connector for a new remote MCP server, then connect to it:
Name: AnythingMCP
Transport: remote streamable HTTP
URL: https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID
Auth: OAuth

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Muse connects from Meta's cloud, so localhost does not work.

Available tools

FAQ

Where is Muse available? Meta currently offers Muse in the US and Canada, on the web, in the iOS and Android apps and in WhatsApp.

Does Meta review this connector? No. Meta doesn't review custom connectors. Muse sees only the tools you switched on for this MCP server in AnythingMCP, and you can disconnect it anytime under Settings → Connectors.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT