MCP server
Stripe MCP server: let your AI see payments next to the rest of the business
Stripe hosts its own MCP server at mcp.stripe.com: with OAuth or an agent API key, an agent can read and write through much of the Stripe API, and refunds need human confirmation. Mojobase's MCP server shows an agent your Stripe payments, plans and unpaid invoices read-only, on each customer's page and in Numbers, beside the emails that explain them.
Updated . Stripe facts link to Stripe's own documentation
How does Stripe's own MCP server compare with Mojobase's?
| What matters | Mojobase MCP | Stripe's own |
|---|---|---|
| What an agent can do | Read payments, plans and unpaid invoices beside each customer's emails, meetings and tasks | stripe_api_read reads with any GET method in the Stripe API; stripe_api_write writes with any POST, PATCH, PUT and DELETE method1 |
| Moving money | Nothing: the Stripe connection only reads, so refunds and payouts stay in Stripe | Creating a refund needs human confirmation, as do the Treasury tools that send, transfer or convert money2 |
| Sign-in | Your Mojobase sign-in or agent key; an owner connects Stripe separately with a restricted read-only Stripe key | OAuth for interactive clients, granted per account or sandbox; agent API keys for autonomous ones3 |
| Keys | Mojobase's own agent keys, shown once and switched off at once | From December 2026 it stops accepting full-access secret keys and restricted keys without the Agent tag; Stripe asks users to migrate by 30 November 20264 |
| Context for a chase | Email, meeting notes, team chat and tasks checked for agreements before reminder drafts with the existing Stripe payment link | Turn on your client's tool-approval setting, and take care using Stripe's server beside other servers, to avoid prompt injection5 |
Which tools does your agent get for Stripe through Mojobase?
| Tool | What it does |
|---|---|
customers_person | One customer: their details, company and history, with their Stripe plan, payments and unpaid invoices |
customers_find_companies | Companies by name or web domain, to find who an invoice belongs to |
numbers_summary | The business's numbers for a period against the one before |
numbers_invoices | List and filter the company's Stripe invoices, including open and overdue amounts by customer, read-only |
numbers_invoice | One Stripe invoice with its history, status and existing Stripe invoice payment-page link, read-only |
mail_search | Every email with a customer, to find what was agreed about paying |
calendar_notes | Notes from recent meetings, where payment terms are often agreed |
draft_reply | A reminder in the customer's thread with the existing Stripe invoice payment link, left as a draft for a person to send |
mojobase_search | One search across mail, events, files, tasks and Handbook pages |
What can you ask your agent once it's connected?
- “Who owes us money, and what did we agree with each of them?”
- “Draft reminders for invoices over 30 days late, skipping anyone we gave more time.”
- “Before my call with Dana, show her plan, what she's paid and her last emails.”
- “Which customers on a monthly plan haven't emailed us in three months?”
Which should you use: Stripe's MCP server or Mojobase's?
Use Stripe's when an agent has to work in Stripe itself: create a payment link, look up a dispute, update a price, or prepare a refund for you to confirm. Use Mojobase's when the agent needs payments in context: which customers owe money, what you agreed with each of them, and a reminder drafted in your tone. Mojobase's connection can't move money, which makes it the safer one to leave connected all day.
Why should an agent check what was agreed before chasing an invoice?
Because the invoice isn't the whole story. Stripe knows invoice 1042 is unpaid; it doesn't know you told Dana on a call to hold it until the second delivery. An agent chasing from Stripe alone can miss that agreement. Through Mojobase it checks email, meeting notes, team chat and tasks, skips agreed delays with a source-linked reason, and drafts the remaining reminders with each existing Stripe invoice payment link. A person sends each draft from Email. Mojobase reads invoices in US dollars; it does not create, prepare or send invoices or create payment pages.
An owner connects the company's Stripe account in Settings → Connections → Connect a source: find Stripe, choose Connect, paste the restricted read-only Stripe key into Restricted key and choose Connect Stripe. That source key is separate from the Mojobase agent sign-in or key. Your agent reads the invoices through numbers_invoices and numbers_invoice with your Numbers permissions; it does not need its own Stripe key.
How do you keep an agent with payment access safe?
Separate reading from acting. Give everyday agents Mojobase's read-only view, where the worst a confused agent can do is write a draft. When an agent must act in Stripe, use OAuth or an agent-tagged key, so Stripe's approval rules apply to payouts and refunds, and keep your client's tool approval on. Check Mojobase's Activity for what the agent read and drafted.
Questions people ask
Is there an official Stripe MCP server?
Yes. Stripe hosts one at mcp.stripe.com. Clients sign in with OAuth, or use an agent API key, and Stripe's own plugin setup (stripe agent setup) configures it for the agents it finds on your computer.
Can an AI agent refund a payment over MCP?
Through Stripe's server, an agent can create a refund once a person confirms it, and agent keys add Stripe's approval rules. Through Mojobase, no: its Stripe connection only reads, so refunds stay in Stripe.
What changes for Stripe MCP keys in December 2026?
Stripe's MCP server stops accepting full-access secret keys and restricted keys without the Agent tag. Stripe asks users to switch to agent API keys or reconnect with OAuth by 30 November 2026.
Can I connect Stripe's server and Mojobase's to the same agent?
Yes. Use Mojobase's to see who owes what and what was agreed, and Stripe's when someone needs to act in Stripe, with tool approval on. Stripe advises care when its server runs beside others, because of prompt injection.
Sources
- Stripe: What an agent can do. docs.stripe.com/mcp, checked 7 Nov 2026.
- Stripe: Moving money. docs.stripe.com/mcp, checked 7 Nov 2026.
- Stripe: Sign-in. docs.stripe.com/mcp, checked 7 Nov 2026.
- Stripe: Key change. docs.stripe.com/mcp, checked 7 Nov 2026.
- Stripe: Stripe's advice. docs.stripe.com/mcp, checked 7 Nov 2026.
- Stripe: Agent keys. docs.stripe.com/keys, checked 7 Nov 2026.