Skip to main content
Glama
cledara-mcp

cledara-mcp

by ilyesBen

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CLEDARA_API_KEYYesRequired. Your Cledara API key.
CLEDARA_ENV_FILENoPath to an env file to read the key from.
CLEDARA_API_BASE_URLNoOverride the API host, e.g. for a mock server.https://api.cledara.com

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_applicationsA

List SaaS applications in the Cledara workspace with status, owner, teams, budget, balance, next renewal date and expected next payment. Filters are optional.

list_transactionsA

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.

get_invoice_urlA

Get a download URL for the invoice attached to a transaction (only when hasInvoice is true). The URL expires after 5 minutes.

spend_summaryA

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.

upcoming_renewalsA

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.

missing_invoicesA

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.

list_peopleA

People and teams in the workspace, inferred from application owners, application teams and cardholders seen in recent transactions (Cledara has no users endpoint).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 7 tools

Disambiguation5/5

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.

Naming Consistency3/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues