Cledara MCP by usefulapi

List applications, transactions and invoice download links in Cledara.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
73%
Naming quality
73%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Findings (1)

  • LOWTool 'cledara_get_transaction_invoice_url' name length outside 3-30 rangein cledara_get_transaction_invoice_url

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~746Tokens (tool definitions)
~1.2 KBTypical response size
Moderate attention impact (0.58% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "cledara": {
      "url": "https://cledara.usefulapi.io/mcp"
    }
  }
}

Remote endpoints

https://cledara.usefulapi.io/mcpstreamable-http

What it can do

Tool inventory

Tools (3)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢cledara_list_applications

List the applications in the Cledara workspace of this API key, with status, budget, owner, teams, balance and the next renewal or payment date. Good first call to see which SaaS applications are tracked. Cledara API: GET /v0/applications.

Input Schema

{
  "type": "object",
  "properties": {},
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢cledara_list_transactions(from, to, applicationIds, offset)

List transactions in the Cledara workspace: amount (negative for debits), currency, account type, application, invoice flag and accounting fields. Filter by time window (`from` is after, `to` is before, RFC 3339), by application ids, and page with `offset`. The result has `hasMore`, `nextOffset` and `totalCount`; pass `nextOffset` as `offset` for the next page. Cledara API: GET /v0/transactions.

Input Schema

{
  "type": "object",
  "properties": {
    "from": {
      "description": "Only transactions after this RFC 3339 date-time, for example 2026-01-01T00:00:00Z.",
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}(\\.\\d+)?(Z|[+-]\\d{2}:\\d{2})$"
    },
    "to": {
      "description": "Only transactions before this RFC 3339 date-time, for example 2026-01-31T23:59:59Z.",
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}(\\.\\d+)?(Z|[+-]\\d{2}:\\d{2})$"
    },
    "applicationIds": {
      "description": "Only transactions of these application ids.",
      "type": "array",
      "items": {
        "type": "string",
        "pattern": "^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$"
      }
    },
    "offset": {
      "description": "Offset for pagination (default 0).",
      "type": "integer",
      "minimum": 0,
      "maximum": 9007199254740991
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢cledara_get_transaction_invoice_url(transactionId)

Get a download URL for a transaction's invoice. The URL is valid for 5 minutes. Check `hasInvoice` in cledara_list_transactions first; a transaction without an invoice or an unknown id returns an error. Cledara API: GET /v0/transactions/{transactionId}/invoice-url.

Input Schema

{
  "type": "object",
  "properties": {
    "transactionId": {
      "type": "string",
      "pattern": "^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$",
      "description": "Transaction unique identifier (UUID)."
    }
  },
  "required": [
    "transactionId"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded3 tools