Spreedly MCP connector
The Spreedly connector lets Claude, ChatGPT, Cursor and other AI clients look up transactions, gateways, environments and card refresher inquiries in Spreedly and act on them through one governed endpoint, with every request logged.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Spreedly to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Spreedly once
-
Open Connections, choose Add connection, and pick Spreedly.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Spreedly API key. One person generates a token in Spreedly and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Spreedly MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Spreedly MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Spreedly MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Spreedly to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Spreedly through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Payments
Find out why a transaction failed
Ask for a transaction by its Spreedly ID or pull up the most recent ones for a gateway, then read the response message and state without opening the dashboard.
-
Finance
Pull a transaction export for month end
Create a Spreedly export of the period you need and get the file ready for reconciliation, then update a transaction's description or reference when the books need a correction.
-
Engineering
Add a new gateway without a ticket
Create a Spreedly gateway for a new acquirer, check its settings alongside the gateways already in place, and update credentials when the processor rotates them.
-
Support
Check a customer's payment before replying
Look up the transaction a customer is asking about, confirm whether it succeeded, was declined or was refunded, and answer in one message with the facts in front of you.
-
Revenue operations
Refresh expired cards before renewals run
Create a Spreedly card refresher inquiry for stored payment methods that are about to expire and review the inquiries that have come back, so subscription charges stop failing on stale card numbers.
-
Security
Keep certificates and access secrets in order
List the certificates and access secrets in each Spreedly environment, create replacements ahead of expiry and delete secrets that are no longer in use.
Try asking
- “Show all failed Spreedly transactions from yesterday”
- “Which Spreedly gateways handled the most transactions this week”
- “Open a card refresher inquiry for expiring cards”
Compare
Elaichi vs Zapier MCP vs Composio for Spreedly
All three can connect Spreedly to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Spreedly tools | Allow or restrict single Spreedly tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Spreedly call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
Spreedly tools for your AI agents
78 tools are ready to call through Elaichi's MCP endpoint the moment you connect Spreedly, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Spreedly gets you
6 screens from the product, each doing one job for your Spreedly account.
The agent
Ask in plain language, read live Spreedly records.
Type a question and the agent answers from current Spreedly transactions and gateways.
- transactions
- gateways
- inquiries
- certificates
Ask Elaichi to work across your apps.
Show all failed Spreedly transactions from yesterday
Which Spreedly gateways handled the most transactions this week
Open a card refresher inquiry for expiring cards
Also runs in Claude, ChatGPT or Cursor
MCP clients
One Spreedly endpoint for every MCP client.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK or shared key.
Copy the endpoint
Tool catalog
All 78 Spreedly tools arrive ready to call.
Transactions, gateways, inquiries, certificates and exports, listed with methods and no custom code.
- Create a Spreedly export
- Update a Spreedly transaction by ID
- Create a Spreedly transaction
- List all Spreedly transactions
Toolboxes
Every team gets its own Spreedly toolbox.
Curate one toolbox per team so payments work stays scoped to that team.
- Payments
- Finance
- Support
- Risk
Shared connections
Teammates use Spreedly without seeing a credential.
The connections table shows who connected each Spreedly account and how widely it is shared.
- Payments EMEA
- Payments US
- Finance
- Support
Audit log
Every Spreedly call is on the record.
When, who, what happened, type and resource, appended for each Spreedly transaction and gateway call.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires and Spreedly work finishes.
Six steps fetch transactions, group them, draft a digest, take approval, then post back.
Spreedly digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch transactions
Spreedly
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Spreedly
Queued
Collections and dashboards
Spreedly gateway health, counted on a schedule.
Four metrics, fourteen days of transactions created and a team breakdown, computed without a model.
Spreedly health
Refreshed 4 minutes ago · every 15 minutes · from the transactions collection
Transactions
1,284 ↓ 12%
Gateways
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Transactions created
Last 14 days
By team
Share of activity
Payments EMEA 34%
Payments US 27%
Finance 21%
Support 18%
FAQ
Frequently asked questions
How do I connect Spreedly to Claude?
Two steps. In Elaichi, choose Spreedly and paste in the API key from your Spreedly account, then paste the Elaichi endpoint, https://api.elaichi.ai/mcp, into Claude under Customize, then Connectors, then Add. Spreedly connects with an API key, so there is no OAuth application to register and no client ID or secret to generate.
Does Spreedly work with ChatGPT and Cursor as well as Claude?
Yes. Once Spreedly is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, the Elaichi Agent and any other MCP client. You connect Spreedly once and every client you use picks it up.
What can an AI agent actually do with my Spreedly account?
It can look up a Spreedly transaction by ID, list recent transactions, create a new one or update its details, and create an export for reconciliation. It can also list, create and update gateways, environments and certificates, manage access secrets, and start card refresher inquiries for stored payment methods. Because Spreedly has many actions, short concrete asks such as "show me yesterday's failed transactions on the Stripe gateway" work better than long paragraphs.
Does connecting Spreedly give the AI every environment and gateway?
No. The connection carries only the access of the Spreedly API key that was used to connect, and each person signs in to Elaichi as themselves, so requests run inside that person's own permissions. Elaichi can narrow what the AI is allowed to do in Spreedly, and it can never widen it beyond what the key already allows.
Can I stop an agent from deleting or changing things in Spreedly?
Yes. Restrictions in Elaichi work per action, so you can allow reading Spreedly transactions and gateways while blocking the ability to create transactions, update gateways or delete access secrets. A blocked action is never shown to Claude, ChatGPT or any other client, so no prompt can reach it.
What happens to a Spreedly connection when someone leaves?
Offboarding that person in Elaichi ends their access to Spreedly through every AI client at once. A Spreedly connection they shared keeps working for everyone else on the team. If you want to remove Spreedly entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.
Does the Spreedly MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Spreedly is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Spreedly?
Yes. Both let Claude, ChatGPT or Cursor use Spreedly. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Spreedly call.
How is Elaichi different from Composio for Spreedly?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Spreedly: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Spreedly in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.