Cresium MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CRESIUM_SECRET | Yes | Partner secret for HMAC signing | |
| CRESIUM_API_KEY | Yes | Partner API key | |
| CRESIUM_COMPANY_ID | Yes | Company ID to operate on |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkB | Check if the Cresium API is available and responding |
| get_balanceB | Get wallet balances for the company. Returns balance, lockedBalance, investedBalance, availableBalance, and currency for each wallet. |
| search_transactionsB | Search and filter company transactions with pagination. Supports filtering by date range, type, tag, status, external ID, and more. |
| get_transactionA | Get a single transaction by ID. Returns the full transaction object including from/to addresses, amounts, fees, status, and related entities. |
| lookup_bank_addressA | Look up a bank address by CBU, CVU, or alias. Returns the address ID (needed as toId for creating transfers), bank name, owner name, and account type. |
| create_transfer_previewA | Create a transfer preview (does not execute the transfer yet). Use lookup_bank_address first to get the toId. Returns the preview transaction and whether 2FA is required. |
| confirm_transactionA | Confirm a previewed transaction, moving it from PREVIEW to PENDING status for processing. Only works on transactions in PREVIEW status. |
| create_signature_requestB | Create a signature request for a transaction, bulk, or payroll. Signers will be notified and can approve from the Dashboard. The transaction auto-confirms on approval. |
| create_paymentsB | Create one or more payments (accounts payable). Each payment represents an amount the company owes to a supplier/creditor. |
| create_invoicesC | Create one or more invoices (accounts receivable). Each invoice represents an amount the company expects to receive from a customer. |
| list_paymentsB | List all company payments. Returns the full list of payments with their status, amounts, and related data. |
| list_invoicesB | List all company invoices. Returns the full list of invoices with their status, amounts, payer information, and related data. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool has a clearly distinct purpose with no overlap: confirm_transaction, create_invoices, create_payments, create_signature_request, create_transfer_preview, get_balance, get_transaction, health_check, list_invoices, list_payments, lookup_bank_address, and search_transactions all target specific financial operations. The descriptions reinforce unique functions, such as create_transfer_preview for previewing transfers versus confirm_transaction for finalizing them, ensuring agents can easily differentiate.
Tool names follow a consistent verb_noun pattern throughout, with clear and predictable conventions: create_invoices, list_payments, get_balance, search_transactions, etc. All tools use snake_case and descriptive verbs (create, get, list, search, confirm, lookup), making the set highly readable and uniform without any deviations or mixed styles.
With 12 tools, the count is well-scoped for a financial operations server, covering core workflows like transfers, invoices, payments, and transactions. Each tool earns its place by addressing specific needs (e.g., previewing vs. confirming transactions, listing vs. creating entities), avoiding bloat while providing comprehensive functionality for the domain.
The tool set offers complete CRUD/lifecycle coverage for financial transactions and related entities: create, list, and get operations for invoices, payments, and transactions, plus preview/confirm workflows for transfers, balance checks, and bank lookups. No obvious gaps exist; agents can handle end-to-end processes from lookup_bank_address to confirm_transaction without dead ends.