Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@cledara-mcp show me our SaaS spend by app for the last 30 days"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A read-only MCP server for Cledara, the SaaS and spend management platform. It lets Claude (or any MCP client) look up your applications, transactions, invoices, spend, renewals and people.
It wraps the Cledara public API (v0). That API is read-only, and so is this server: no tool can change anything in Cledara.
This server cannot change anything in Cledara:
Requests: it only ever makes HTTP GET requests, and only to /v0/applications, /v0/transactions and /v0/transactions/{id}/invoice-url. A test fails the build if any tool sends another kind of request or calls another path.
Tools: every tool is marked readOnlyHint: true and destructiveHint: false, so MCP clients know none of them have side effects.
Local files: it writes nothing to disk. The only cache is an in-memory copy of the application list.
The Cledara API (v0): it has no write endpoints at all.
A Cledara API key carries all the permissions of the user who created it, and Cledara has no read-only key type. If Cledara adds write endpoints later, this server still won't call them, but the key itself could. Treat the key like a password.
Related MCP server: wiseMcp
Tool | What it does |
| Apps with status, owner, teams, budget, balance, next renewal and next payment. Filter by status, name, owner or team. |
| Raw transactions for a date range (default: last 30 days), optionally for specific apps or transaction types. Paginated. |
| Download link for a transaction's invoice (valid for 5 minutes). |
| Spend over a date range grouped by application, team, owner, card, month or account type, totalled per currency. |
| Apps renewing or due a payment in the next N days (default 30) with the expected amount. Cledara often leaves the renewal date empty, so the expected next payment date is used instead ( |
| Card payments with no invoice uploaded, for month-end close. |
| People and teams, inferred from app owners and cardholders (Cledara has no users endpoint). |
How the computed tools work:
Spend counts card payments (cardSend) net of refunds (cardReceive), plus reimbursement. Debits are shown as positive numbers. Top-ups, flushes and transfers are left out because they only move money between Cledara accounts. You can override this with transactionTypes.
Currencies are never converted. Every total is per currency.
Team totals: an app assigned to several teams counts in full under each team.
Owner: the application owner when the payment is for an app, otherwise the cardholder.
Large ranges: aggregate tools fetch up to 50 API pages. If a range has more, the result includes a warning.
Node.js 20.12 or later. Running the tests or npm run dev needs Node 23.6 or later.
A Cledara API key. Only users with the SaaS Admin/Finance or Spend Admin/Accountant role can create one: in Cledara, go to Profile → API Keys → Create API key.
The key can see everything the user who created it can see. Create it from the least-privileged eligible user and give it an expiry.
Each key works for one Cledara account only.
git clone https://github.com/ilyesBen/cledara-mcp.git
cd cledara-mcp
npm install # also builds dist/
cp .env.example .env # then paste your key after CLEDARA_API_KEY=
chmod 600 .env
claude mcp add --scope user cledara -- node "$PWD/dist/index.js"mkdir -p ~/.config/cledara-mcp
printf 'CLEDARA_API_KEY=\n' > ~/.config/cledara-mcp/.env # then paste your key
chmod 600 ~/.config/cledara-mcp/.env
claude mcp add --scope user cledara -- npx -y github:ilyesBen/cledara-mcpDownload cledara.mcpb and double-click it. Claude Desktop asks for your API key and stores it in the system keychain. Node.js isn't needed.
There's a step-by-step guide for non-technical users in docs/claude-desktop.md.
To build the extension yourself, run npm run mcpb. It writes build/cledara.mcpb. To publish a release, bump version in package.json, then push a matching vX.Y.Z tag; the Release workflow builds the extension and attaches it.
For Claude Desktop, Cursor and similar clients, add this to the client's MCP config:
{
"mcpServers": {
"cledara": { "command": "npx", "args": ["-y", "github:ilyesBen/cledara-mcp"] }
}
}--scope user makes the server available in every Claude Code project. Use --scope project to write it to a shared .mcp.json instead.
Variable | Default | Purpose |
| — | Required. Your Cledara API key. |
| — | Path to an env file to read the key from. |
|
| Override the API host, e.g. for a mock server. |
The server takes the first non-empty key it finds, in this order:
The process environment
$CLEDARA_ENV_FILE
.env in the package root (a git clone)
~/.config/cledara-mcp/.env
Prefer an env file over claude mcp add -e CLEDARA_API_KEY=..., which stores the key in plain text in ~/.claude.json.
The key is only ever sent to the Cledara API in the Authorization header. It is never logged or included in error messages.
Cledara allows 120 requests per minute per key. The server:
Limits itself to 100 requests per minute, so other users of the key keep some headroom.
When it gets a 429, waits for the time in Retry-After and retries, up to 3 times.
Caches the application list for 5 minutes.
npm test # unit, server and stdio end-to-end tests against mocks (no API key needed)
npm run typecheck
npm run build # compiles src/ to dist/
npm run dev # runs src/index.ts directlyThe tests use synthetic fixtures based on Cledara's published OpenAPI spec and never call the real API.
You can try the server interactively with the MCP Inspector: npx @modelcontextprotocol/inspector node dist/index.js.
Get a download URL for the invoice attached to a transaction (only when hasInvoice is true). The URL expires after 5 minutes.
Inputs: transactionId (required).
List SaaS applications in the Cledara workspace with status, owner, teams, budget, balance, next renewal date and expected next payment. Filters are optional.
Inputs: team, owner, search, status.
People and teams in the workspace, inferred from application owners, application teams and cardholders seen in recent transactions (Cledara has no users endpoint).
Inputs: cardholderLookbackDays.
List raw Cledara transactions (SaaS and Spend cards, transfers, top-ups) in a date range. Amounts are negative for debits. Defaults to the last 30 days. If nextOffset is returned, call again with that offset for more.
Inputs: to, from, types, offset, +2 more.
Card payments (cardSend) in a date range that have no invoice uploaded, newest first, with totals per currency. Useful for month-end close. Defaults to the last 30 days.
Inputs: to, from, applicationIds.
Total spend over a date range grouped by application, team, owner, card, month or account type, with separate totals per currency (no FX conversion). Spend counts card payments net of refunds plus reimbursements by default, reported as positive numbers. Defaults to the last 30 days.
Inputs: to, from, groupBy, applicationIds, +1 more.
Applications renewing or due a payment within the next N days, soonest first, with the expected payment amount and budget. Uses nextRenewalDate when Cledara sets it, otherwise the expected next payment date (see dateSource). Inactive and disabled apps are excluded unless includeInactive is true.
Inputs: withinDays, includeInactive.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 7 tools
Each tool targets a clearly distinct resource or analytical view: applications, people, raw transactions, invoice URLs, spend summaries, renewals, and missing invoices. The boundaries between raw transactions, spend summaries, overdue invoices, and renewals are well described, so an agent can select the right tool without confusion.
All names use snake_case, but the naming conventions are mixed: list_* and get_* verb-noun tools coexist with noun-phrase tools like spend_summary, upcoming_renewals, and missing_invoices. The names remain readable and understandable, but the pattern is not fully predictable.
Seven tools is a well-scoped size for a read-only SaaS spend reporting integration. Each tool fills a specific reporting or lookup need without redundant or filler operations.
The surface covers the core Cledara reporting workflows: applications, people, transactions, invoices, spend summaries, renewals, and missing invoices. Minor gaps exist, such as no dedicated application-detail or card-listing endpoint, but most needs can be worked around using filters and summaries.
Read-only MCP access to a documented IT fleet: state, changes, posture. 15 tools.
Read-only MCP access to sessions, funnels, campaigns, errors, live visitors, and anomalies.
Read-only access to InfluSense influencer discovery, ratings, watchlists, and reports via MCP.
Read-only MCP over your own revenue and net margin across 14 billing rails
