# 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. Source: https://elaichi.ai/connectors/cledara/ ## Facts | | | | --- | --- | | Application | Cledara | | Category | Spend Management | | AI tools | 3 | | Authentication | Connects with an API key | | Bring your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead | ## What you can ask once Cledara is connected - 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. ## Connect Cledara in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Cledara. 2. Optionally set Share with, then press Connect. 3. 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. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Cledara tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Cledara MCP connector for Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect Cledara to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a Cledara tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Cledara through Elaichi ### Explain a charge before month-end close Finance. 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. ### Fetch the invoice behind any card charge Accounting. Give the AI a transaction and get the Cledara invoice link straight back, ready to attach to the ledger entry. ### See every application the company pays for IT. List the applications in Cledara, spot the ones nobody on the team recognizes, and start the conversation about switching them off. ### Spot overlapping tools before renewal Procurement. 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. ### Answer what we pay for something Operations. 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. ### Summarize this quarter's software spend Leadership. 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. ## 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 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. ### 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. ## All 3 Cledara tools Every tool below is callable through https://api.elaichi.ai/mcp once Cledara is connected, subject to the toolbox it is in and the restrictions on the caller. - **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.