Coupa MCP connector
Connecting Coupa to Elaichi lets Claude, ChatGPT, Cursor and any MCP client look up requisitions, purchase orders, suppliers and invoices, and raise new requisitions, inside each person's own access and fully logged.
-
How it connects. App credentials. 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 Coupa to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Coupa once
-
Open Connections, choose Add connection, and pick Coupa.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste your Coupa app credentials. Coupa authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.
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.
Coupa 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.
Coupa MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Coupa 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.
Coupa 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 Coupa 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 Coupa through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Procurement
Raise a requisition from a team's request
Turn a request for new laptops into a Coupa requisition with the right items and supplier, without opening the form yourself.
-
Accounts payable
Match an invoice to its purchase order
Pull up a supplier's invoice and the purchase order behind it side by side to check quantities and amounts before it is paid.
-
Finance
See what is committed with each supplier
List open purchase orders by supplier and currency to understand spend commitments before month end close.
-
Supplier management
Onboard a supplier and keep details current
Add a new supplier to Coupa and update contact or payment details when they change, straight from the chat.
-
Operations
Find the right catalog item before ordering
Search Coupa items and supplier items to check what is already on contract and at what price.
-
Office management
Check where a requisition is stuck
Ask which requisitions are still waiting and who raised them, then chase the right person.
Try asking
- “Show me open requisitions waiting for a purchase order”
- “Which suppliers invoiced us this month and for how much?”
- “Create a requisition for 20 standing desks from Steelcase”
Compare
Elaichi vs Zapier MCP vs Composio for Coupa
All three can connect Coupa 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 Coupa tools | Allow or restrict single Coupa 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 Coupa 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
Coupa tools for your AI agents
62 tools are ready to call through Elaichi's MCP endpoint the moment you connect Coupa, 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 Coupa gets you
6 screens from the product, each doing one job for your Coupa account.
The agent
Ask about purchase orders in plain language.
Elaichi's agent answers from live Coupa requisitions, suppliers and invoices, not a stale export.
- purchase orders
- requisitions
- suppliers
- invoices
Ask Elaichi to work across your apps.
Show me open requisitions waiting for a purchase order
Which suppliers invoiced us this month and for how much?
Create a requisition for 20 standing desks from Steelcase
Also runs in Claude, ChatGPT or Cursor
MCP clients
One Coupa endpoint for Claude, ChatGPT and Cursor.
Every MCP client reaches Coupa through one endpoint, no SDK and no shared API key.
Copy the endpoint
Tool catalog
62 Coupa tools, ready without writing code.
Purchase orders, requisitions, suppliers, invoices, items and accounts, cataloged with every method.
- List all Coupa accounts
- Get single Coupa account by ID
- Create a Coupa purchase order
- List all Coupa purchase orders
Toolboxes
Every team gets its own Coupa toolbox.
Procurement raises requisitions, accounts payable reads invoices, each team scoped to its own toolbox.
- Procurement
- Accounts payable
- Finance
- Operations
Shared connections
Share a Coupa connection, never a credential.
One person connects Coupa, teammates work through it, and nobody else sees the app credentials.
- Procurement
- Accounts payable
- Finance
- Operations
Audit log
Every Coupa call is logged with a name.
When, who, what happened and which supplier or requisition, in an append-only log.
- 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 drafts the invoice digest, you approve.
Invoices are fetched, grouped by supplier, summarized, approved by a person, then posted to Coupa.
Coupa digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch purchase orders
Coupa
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
Coupa
Queued
Collections and dashboards
Coupa spend health, computed without a model.
Four metrics, 14 days of purchase orders created, a breakdown by team, refreshed on schedule.
Coupa health
Refreshed 4 minutes ago · every 15 minutes · from the purchase orders collection
Purchase orders
1,284 ↓ 12%
Requisitions
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Purchase orders created
Last 14 days
By team
Share of activity
Procurement 34%
Accounts payable 27%
Finance 21%
Operations 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Coupa to Claude?
Connect Coupa in Elaichi first: Coupa uses app credentials, so you paste the credentials your Coupa administrator issues, with no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi, and from then on it can work with your Coupa requisitions, purchase orders, suppliers and invoices.
Does Coupa work with ChatGPT and Cursor as well as Claude?
Yes. Once Coupa is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Coupa once and every client you use picks it up.
What can an AI agent actually do with my Coupa data?
It can look up Coupa requisitions, purchase orders, invoices, suppliers, catalog items and accounts, and answer questions like which invoices arrived from a supplier this month or which requisitions are still open. It can also raise a new requisition or purchase order, add a supplier, and update a supplier's details or an open requisition. Short, concrete asks work best, such as 'list open requisitions over 5,000' rather than a long paragraph.
Does connecting Coupa give the AI every purchase order and invoice in the company?
No. The connection carries the access of the Coupa app credentials it was set up with, and each person signs in to Elaichi as themselves, so an agent sees only the Coupa requisitions, orders, suppliers and invoices that access allows. Elaichi can narrow that further by team or by action, and it can never widen it beyond what Coupa itself permits.
Can I stop an agent from deleting or changing things in Coupa?
Yes. Restrictions in Elaichi work per action, so you can allow reading Coupa invoices and purchase orders while blocking the ability to delete a requisition or change a supplier. A restricted action is left out of the AI client's tool list entirely, so it cannot be called no matter how the prompt is phrased.
What happens to a Coupa connection when someone leaves?
Offboarding a person in Elaichi ends their access to Coupa through every AI client at once. If they had shared a Coupa connection with a team, it keeps working for everyone else. If you want it gone entirely, disconnecting Coupa once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.
Does the Coupa MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Coupa 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 Coupa?
Yes. Both let Claude, ChatGPT or Cursor use Coupa. 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 Coupa call.
How is Elaichi different from Composio for Coupa?
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 Coupa: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Coupa 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.