Stripe MCP

Coming soon

OAUTH 2.1

PAYMENTS

Accounting & Finance

Every customer, subscription, dispute, and Stripe API operation your agent needs to run lives in Stripe. Stripe MCP gives your agent per-user OAuth access scoped to the authorizing Stripe account.

  • Acts as the user: Subscription updates and API calls stay tied to the Stripe account that authorized the agent.
  • Credentials stay vaulted: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: User permissions enforced. 90-day audit trail.
Stripe MCP
agent · Acme Q3
Run
Pause the subscription for customer cus_Q9 until next billing cycle.
S
stripemcp_update_subscription
118ms
Billing agent
Subscription sub_8K2 paused. pause_collection set to keep_as_draft. Resumes on the next billing date (Dec 14). No invoices will be sent in the interim.
Sources: Stripe Billing, cus_Q9
stripemcp
1
18:29
Message Claude...

Tools your agent reaches for on Stripe MCP, scoped per user.

CALL ANY TOOL
Manage subscriptions, search and execute any Stripe API operation, recommend integration patterns. Same toolkit, every framework, no auth plumbing.
stripemcp_get_stripe_account_info
Get account info
Retrieve account information for the authorized Stripe account including capabilities and settings.
Parameters
Name
Type
Required
Description
No parameters required
stripemcp_update_subscription
Update subscription
stripemcp_search_stripe_api
Search Stripe API
stripemcp_stripe_api_details
Get API operation details
stripemcp_execute_stripe_api
Execute Stripe API operation
stripemcp_stripe_integration_recommender
Integration recommender
Build your Agent
Drop the toolkit in, point it at the user, and your agent can manage Stripe subscriptions and call any Stripe API from the first run.
Python · LlamaIndex
import { ScalekitClient } from "@scalekit-sdk/node";
import { DynamicStructuredTool } from "@langchain/core/tools";
import { createReactAgent } from "@langchain/langgraph/prebuilt";
import { z } from "zod";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["stripemcp"], toolNames: ["stripemcp_get_stripe_account_info", "stripemcp_update_subscription", "stripemcp_search_stripe_api"] },
pageSize: 100,
});

const lcTools = tools.map((t) => new DynamicStructuredTool({
name: t.tool.definition.name,
description: t.tool.definition.description,
schema: z.object({}).passthrough(),
func: async (args) => {
const { data } = await sk.tools.executeTool({
toolName: t.tool.definition.name,
identifier: "user_123",
params: args,
});
return JSON.stringify(data);
},
}));

const agent = createReactAgent({ llm, tools: lcTools });
import { ScalekitClient } from "@scalekit-sdk/node";
import OpenAI from "openai";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["stripemcp"], toolNames: ["stripemcp_get_stripe_account_info", "stripemcp_update_subscription", "stripemcp_search_stripe_api"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
type: "function",
function: {
name: t.tool.definition.name,
description: t.tool.definition.description,
parameters: t.tool.definition.input_schema,
},
}));

const resp = await openai.responses.create({
model: "gpt-4o", input: prompt, tools: llmTools,
});
import { ScalekitClient } from "@scalekit-sdk/node";
import Anthropic from "@anthropic-ai/sdk";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["stripemcp"], toolNames: ["stripemcp_get_stripe_account_info", "stripemcp_update_subscription", "stripemcp_search_stripe_api"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
name: t.tool.definition.name,
description: t.tool.definition.description,
input_schema: t.tool.definition.input_schema,
}));

const msg = await anthropic.messages.create({
model: "claude-sonnet-4-6", max_tokens: 1024,
tools: llmTools,
messages: [{ role: "user", content: prompt }],
});
import { Agent } from "@google/adk/agents";
import {
MCPToolset, StreamableHTTPConnectionParams,
} from "@google/adk/tools/mcp";

const toolset = new MCPToolset({
connectionParams: new StreamableHTTPConnectionParams({
url: "https://mcp.scalekit.com/stripemcp",
headers: { Authorization: `Bearer ${userScopedToken}` },
}),
});

const agent = new Agent({
name: "agent", model: "gemini-2.0-flash",
tools: await toolset.getTools(),
});
Try these prompts
Paste any prompt into your agent to start managing Stripe from your workflows.
Billing actions
Copy the prompt
Copied
Pause subscription [sub_id] until [date].
Copy the prompt
Copied
Refund the last charge for customer [cus_id].
Copy the prompt
Copied
Upgrade [cus_id] from monthly to annual plan with prorated credit.
Reporting & search
Copy the prompt
Copied
Find all disputes opened in the last 7 days.
Copy the prompt
Copied
Show MRR by plan for active subscriptions.
Copy the prompt
Copied
List customers with failed payments this month.
SEE HOW AUTH WORKS
Users authorize Stripe once. Their credentials stay vaulted, every call is checked, and every action is logged.
1
Authorize
Your user connects
Stripe MCP
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Stripe MCP
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Stripe MCP
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Stripe MCP
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
Same per-user auth pattern across other finance and payments connectors.
No items found.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Other connector libraries treat auth as a demo afterthought. Scalekit starts with user identity, scope enforcement, and audit.
01.
Shared tokens break per-user analytics
A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential so attribution, audit, and scope stay accurate.
// shared token
 audit → bot_service_account
 user_filter → broken

 // scalekit
 audit → user_abc
 scope → enforced ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
Stripe MCP today. Others tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions
Does the agent access Stripe as the user or a shared service account?
As the user. Each Stripe account authorizes once and Scalekit resolves their credential at request time. All API calls are attributed to that user.
Where is the Stripe OAuth token stored?
In Scalekit's AES-256 vault, namespaced per tenant. Refresh is automatic. Tokens never appear in prompts or LLM context.
Can I prevent the agent from executing destructive API calls?
Yes. Use listScopedTools to restrict the agent to read-only operations (account info, search, details) without granting execute_stripe_api.
What happens when a user revokes Stripe access?
The connection is invalidated on the next tool call. Subsequent requests fail closed with a clear error.
Is this safe to use for production billing workflows?
Yes. Per-user credential isolation, scope enforcement before every call, and a 90-day audit trail are built in. Every Stripe operation executes as the authorizing user with their Stripe permissions.
Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""stripemcp"": {
""url"": ""https://mcp.scalekit.com/stripemcp"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.stripemcp]
url = ""https://mcp.scalekit.com/stripemcp""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""stripemcp"": {
""url"": ""https://mcp.scalekit.com/stripemcp"",
""type"": ""http""
}
}
}