Can my team share one Cledara connection?

Yes. One person connects Cledara with the API key and shares the connection with a team in Elaichi, and nobody else ever sees or handles that key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every Cledara call.

Spend Management

Cledara MCP connector

The Cledara connector brings your software applications, card transactions and invoices to Claude, ChatGPT and Cursor through one governed endpoint, so anyone on your team can ask about spend and get answers from live Cledara records.

Connect on Elaichi How to connect

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.

3 tools

How to connect

How to connect Cledara to Claude, ChatGPT or Cursor

Two steps, about a minute.

In Elaichi

Connect Cledara once

Open Connections, choose Add connection, and pick Cledara.
Optionally set Share with to give a team access, then press Connect.
Paste a Cledara API key. One person generates a token in Cledara 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.

cledara

All categories

Cledara

1Password

360learning

7shifts

Acquire

Ada

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.

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 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.

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.

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.

Connect Cledara on Elaichi See pricing

Use cases

What teams do with Cledara through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

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.”

See all 3 Cledara tools below

AI tools

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.

See it in Elaichi

What connecting Cledara gets you

6 screens from the product, each doing one job for your Cledara account.

The agent

Ask about Cledara spend in plain language.

Answers come from live Cledara transactions and applications, not from a stale export.

transactions
invoices
applications
subscriptions

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 or Cursor

MCP clients

One endpoint brings Cledara to every client.

Claude, ChatGPT and Cursor reach Cledara through one governed endpoint, no SDK, no shared key.

ElaichiMCP clients

Claude

ChatGPT

Cursor

Copy the endpoint

https://api.elaichi.ai/mcp

Client	Connected by	Status	Last used
Claude	E Emma Laurent	• Connected	4 minutes ago
Cursor	S Sofia Ricci	• Connected	2 hours ago
ChatGPT	C Clara Nowak	• Connected	Yesterday

Tool catalog

All 3 Cledara tools ready with no code.

Transactions, invoice links and applications are covered without writing any custom code.

List all Cledara transactions
Get single Cledara transaction invoice URL by ID
List all Cledara applications

ElaichiTools

Tool	Action	Description
List all Cledara transactions	List	List transactions in a Cledara workspace with optional date-range and application filters. Returns transaction records with id, amount, currency, type, authorizedAt, card, hasInvoice, and accounting field values.
Get single Cledara transaction invoice URL by ID	Get	Get the URL to download a Cledara transaction invoice. Returns: invoiceUrl. Required: id.
List all Cledara applications	List	List applications in the Cledara workspace. Returns the workspace's application records, each identified by its unique id, with the remaining record fields defined by Cledara's Application schema upstream. Takes no parameters.

Toolboxes

Every team gets its own Cledara toolbox.

Finance, IT and Procurement each work from a toolbox scoped to their own team.

Finance
Accounting
IT
Procurement

ElaichiToolboxes

Name	Source template	Tools	Created
Finance toolbox Cledara · transactions and invoices	Cledara starter	18	Mar 4, 2026
Accounting toolbox Cledara · invoice retrieval and close	—	9	Mar 2, 2026
IT toolbox Cledara · applications and licenses	—	24	Feb 27, 2026
Procurement toolbox Cledara · renewals and vendors	Cledara starter	6	Feb 19, 2026
Operations toolbox Cledara · team tooling and spend	—	31	Jan 30, 2026
Leadership toolbox Cledara · spend overview	—	12	Jan 22, 2026

Shared connections

Teammates use Cledara without seeing the key.

One person connects Cledara, shares it with teams, and nobody else handles the API key.

Finance
Accounting
IT
Procurement

ElaichiConnections

Connection	Scope	Status	Access
CL Cledara (Finance) Connected by Emma Laurent	Personal	• Active	1 team · 6 members
CL Cledara (Accounting) Connected by James Whitfield	Organization	• Active	3 teams · 24 members
CL Cledara (IT) Connected by Sofia Ricci	Organization	• Active	2 teams · 11 members
CL Cledara (Procurement) Connected by Daniel Ortega	Personal	• Needs re-auth	1 team · 3 members
CL Cledara (Operations) Connected by Clara Nowak	Personal	• Active	Not shared
CL Cledara (Leadership) Connected by Michael Brennan	Personal	• Active	2 teams · 9 members

Audit log

Every Cledara call names who made it.

When, who, what happened and which transaction, in a log nobody can edit.

When
Who
What happened
Type

ElaichiAudit log

When	Who	What happened	Type
2 minutes ago Mar 6, 2026, 3:10 PM	E Emma Laurent [email protected]	Restriction Created	Access
8 minutes ago Mar 6, 2026, 3:04 PM	J James Whitfield [email protected]	Restriction Updated	Access
14 minutes ago Mar 6, 2026, 2:58 PM	S Sofia Ricci [email protected]	Role Assigned	Access
20 minutes ago Mar 6, 2026, 2:52 PM	D Daniel Ortega [email protected]	Cledara Users Updated	MCP
26 minutes ago Mar 6, 2026, 2:46 PM	C Clara Nowak [email protected]	Cledara Transactions Created	MCP
32 minutes ago Mar 6, 2026, 2:40 PM	M Michael Brennan [email protected]	Cledara Transactions List	Toolbox

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

Cledara spend digests run on a schedule.

Transactions are fetched, grouped and drafted into a digest a person approves before it posts.

Cledara digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

Run now

✓

Schedule

Every weekday at 08:00

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 Michael Brennan

Approve Deny
Post the digest

Cledara

Queued

Collections and dashboards

Cledara spend health, computed without a model.

Four metrics, 14 days of transactions and a team breakdown, refreshed on a schedule.

Cledara health

Refreshed 4 minutes ago · every 15 minutes · from the transactions collection

Live

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%

Related connectors

More from the catalog

Browse all 400+ connectors →

FAQ

Frequently asked questions

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, 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 team can use. A restricted action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt can reach it. 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 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, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Put Cledara in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Connect Cledara Talk to us

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.