Cledara MCP connector
The Cledara connector brings your software applications, card transactions and invoices to Claude, ChatGPT, Cursor and Microsoft Copilot through one governed endpoint, so anyone on your team can ask about spend and get answers from live Cledara records.
- Connects with an API key
- Free 14-day trial
- No credit card
ChatGPT
Elaichi connected
Which Cledara applications renewed this month and what did each cost?
Working in Cledara with Elaichi
-
List all Cledara transactions
-
-
Governance
/
Audit log
Last 24 hours
ChatGPT · 9:41 AM
Done
ChatGPT · 9:41 AM
Done
ChatGPT · 9:41 AM
Done
Claude · 9:38 AM
Done
Cursor · 9:35 AM
Done
How to connect Cledara to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Cledara 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.
Cledara 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.
Cledara 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. The plugin directory lives at chatgpt.com/plugins.
Cledara 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.
Cledara MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Cledara 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.
What teams do with Cledara through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Cledara is logged.
-
Finance
Explain a charge before month-end close
Ask what a Cledara transaction was for, which application it belongs to and who owns it, then pull the invoice link without opening another tab.
-
Accounting
Fetch the invoice behind any card charge
Give the AI a transaction and get the Cledara invoice link straight back, ready to attach to the ledger entry.
-
IT
See every application the company pays for
List the applications in Cledara, spot the ones nobody on the team recognizes, and start the conversation about switching them off.
-
Procurement
Spot overlapping tools before renewal
Ask which Cledara applications do similar jobs and what each has cost this year, so the renewal decision is made with the numbers in front of you.
-
Operations
Answer what we pay for something
When someone asks how much the company spends on a tool, the answer comes from live Cledara transactions rather than a spreadsheet from last quarter.
-
Leadership
Summarize this quarter's software spend
Ask for a plain-language rundown of Cledara transactions grouped by application, and get a picture of where software money went without waiting on a report.
Try asking
- “Which Cledara applications renewed this month and what did each cost?”
- “List last week's Cledara transactions over 500 dollars.”
- “Pull the invoice for the Notion charge from Tuesday.”
What connecting Cledara gets you
6 screens from Elaichi, each doing one job for your Cledara account.
Ask Elaichi to work across your apps.
Which Cledara applications renewed this month and what did each cost?
List last week's Cledara transactions over 500 dollars.
Pull the invoice for the Notion charge from Tuesday.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Cledara spend in plain language.
Answers come from live Cledara transactions and applications, not from a stale export.
ElaichiAI appsClaude
ChatGPT
Cursor
Microsoft Copilot
Copy the endpoint
AI apps
One endpoint brings Cledara to every client.
Claude, ChatGPT, Cursor and Microsoft Copilot reach Cledara through one governed endpoint, no SDK, no shared key.
ElaichiToolsTool catalog
All 3 Cledara tools ready with no code.
Transactions, invoice links and applications are covered without writing any custom code.
ElaichiToolboxesToolboxes
Every team gets its own Cledara toolbox.
Finance, IT and Procurement each work from a toolbox scoped to their own team.
ElaichiConnectionsShared connections
Teammates use Cledara without seeing the key.
One person connects Cledara, shares it with teams, and nobody else handles the API key.
ElaichiAudit logAudit log
Every Cledara call names who made it.
When, who, what happened and which transaction, in a log nobody can edit.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Cledara digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch transactions
Cledara
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 Jake Morgan
Approve Deny -
Post the digest
Cledara
Queued
Workflows
Cledara spend digests run on a schedule.
Transactions are fetched, grouped and drafted into a digest a person approves before it posts.
Cledara health
Refreshed 4 minutes ago · every 15 minutes · from the transactions collection
Transactions
1,284 ↓ 12%
Invoices
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Transactions created
Last 14 days
By team
Share of activity
Finance 34%
Accounting 27%
IT 21%
Procurement 18%
Collections and dashboards
Cledara spend health, computed without a model.
Four metrics, 14 days of transactions and a team breakdown, refreshed on a schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Cledara
All three can connect Cledara 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 Cledara tools | Allow or restrict single Cledara 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 Cledara 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 | Free for one person; $15 per user per month on Gold. | 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.
Cledara tools for your AI agents
3 tools are ready to call through Elaichi's MCP endpoint the moment you connect Cledara, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Cledara to Claude?
Connecting Cledara takes two steps. In Elaichi, choose Cledara and paste in an API key from your Cledara account, then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. There is no OAuth application to register in Cledara and no client ID or secret to generate.
Does Cledara work with ChatGPT and Cursor as well as Claude?
Yes. Once Cledara is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Cledara once and every client picks it up.
What can an AI agent actually do with my Cledara data?
With Cledara connected, an agent can list your transactions, list the applications your company pays for, and fetch the invoice link for any single transaction. That means you can ask what a charge was for, which tools renewed this month, or for the invoice behind a specific card payment. Short, concrete asks such as "list Cledara transactions from last week" work better than long paragraphs.
Does connecting Cledara give the AI everything in my account?
No. Every request to Cledara runs inside the access of the person who signed in to Elaichi, so the AI sees what they could already see in Cledara and nothing more. Elaichi can narrow that access further with restrictions, and it can never widen it.
Can I stop an agent from deleting or changing things in Cledara?
Restrictions in Elaichi work per action, so you decide exactly which Cledara actions each role can use. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says. This Cledara connector only reads transactions, applications and invoice links, and you can narrow even that further.
What happens to a Cledara connection when someone leaves?
Offboarding a person in Elaichi ends their access to Cledara through every client at once. A shared Cledara connection keeps working for everyone else on the team. If you disconnect Cledara in Elaichi, it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client in one step.
Does the Cledara MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Cledara 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, Microsoft Copilot, 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 Cledara?
Yes. Both let Claude, ChatGPT or Cursor use Cledara. 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 Cledara call.
How is Elaichi different from Composio for Cledara?
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 Cledara: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Cledara in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
- ChatGPT
- Claude
- Cursor
- Microsoft Copilot