Cresium MCP Server
OfficialThe Cresium MCP server enables AI assistants to interact with the Cresium API to manage financial operations for a partner company. Key capabilities include:
Health Check: Verify API connectivity.
Wallet Balances: Retrieve available, locked, invested, and total balances per currency.
Transactions: Search and filter transactions by type, status, date, tags, etc.; get full details; create transfer previews using resolved bank addresses; confirm previews to execute transfers; reverse deposited transactions; and download transaction receipts as PDF.
Payment Orders: Create one-off payment orders that generate a dedicated CVU; search, view, and delete unpaid orders.
Deposit Addresses (CVUs): List, create, update aliases, and delete CVUs for collections.
Signature Requests: Create approval requests for transactions, bulk operations, or payroll; reject pending requests.
Accounts Payable: Create and list payments; extract payment data from files via OCR.
Accounts Receivable: Create and list invoices; extract invoice data from files via OCR.
Investments: View investment fund positions.
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., "@Cresium MCP ServerCheck my current wallet balances and list my most recent transactions"
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.
Cresium MCP Server
MCP (Model Context Protocol) server the Cresium API. Enables AI tools like Claude Code and Claude Desktop to manage transactions, payments, invoices, and balances through the Cresium Partner API (V3).
Prerequisites
You need a Cresium partner account with:
API Key (
apiKey)Secret (
secret)Company ID (
companyId)
These are available from the Cresium Dashboard under your partner settings.
Related MCP server: CurrencyTransfer MCP Server
Installation
Claude Code
claude mcp add cresium-server \
-e CRESIUM_API_KEY=your_api_key \
-e CRESIUM_SECRET=your_secret \
-e CRESIUM_COMPANY_ID=your_company_id \
-- node /absolute/path/to/cresium-mcp-server/build/index.jsClaude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"cresium": {
"command": "node",
"args": ["/absolute/path/to/cresium-mcp-server/build/index.js"],
"env": {
"CRESIUM_API_KEY": "your_api_key",
"CRESIUM_SECRET": "your_secret",
"CRESIUM_COMPANY_ID": "your_company_id"
}
}
}
}Build from source
git clone <repo-url>
cd cresium-mcp-server
npm install
npm run buildEnvironment Variables
Variable | Required | Description |
| Yes | Partner API key |
| Yes | Partner secret for HMAC signing |
| Yes | Company ID to operate on |
| No | API URL. Defaults to |
Available Tools
Balances and investments
Tool | Description |
| Wallet balances (balance, locked, invested, available) per currency |
| Investment fund positions with units held, current value and fund details |
Transactions
Tool | Description |
| Search with filters (date, type, operation type, direction, tag, status) |
| Get a single transaction by ID |
| Download the transaction receipt as a PDF |
| Look up a CBU/CVU/alias to get the address ID used as |
| Create a transfer in PREVIEW status (does not move money) |
| Confirm a previewed transaction |
| Refund a received deposit back to its sender |
Collections — one-off payment orders (V2)
Tool | Description |
| Create a one-off collection and get a dedicated CVU to receive it |
| List payment orders with their status and amount collected |
| Get one payment order by your own |
| Delete an unpaid order and take down its CVU |
Collections — CVU management (V1, deprecated)
Tool | Description |
| List all active CVUs and aliases |
| Get one CVU with its alias |
| Issue a new CVU |
| Rename the alias of an active CVU |
| Take down a CVU (irreversible) |
Signature requests
Tool | Description |
| List signature requests and their status |
| Request signer approval for a transaction, bulk or payroll |
| Reject a pending request (approval is Dashboard-only) |
Accounts payable and receivable
Tool | Description |
| Create payments (accounts payable) |
| List all company payments |
| Extract payment data from PDFs/images via OCR |
| Create invoices (accounts receivable) |
| List all company invoices |
| Extract invoice data from PDFs/images via OCR |
Other
Tool | Description |
| Check API availability |
Typical Workflow
Send a transfer
Look up the destination:
lookup_bank_addresswith the CBU/CVU/aliasCreate a preview:
create_transfer_previewwith the address ID, amount, and currencyRequest approval:
create_signature_requestwith the transaction ID (signers approve from Dashboard)
Check balances and transactions
Get balances:
get_balanceto see available funds per currencySearch transactions:
search_transactionswith date or status filtersGet details:
get_transactionwith a specific transaction ID
Collect a one-off payment
Create the order:
create_payment_orderwith the expected amount and your own reference — returns a dedicated CVUShare the CVU with the payer, and persist it to match incoming
DEPOSITwebhooksTrack it:
get_payment_orderwith your reference to seestatusandamountPaid
The CVU is taken down automatically once the order is paid or expires.
Load invoices from files
Extract:
read_invoices_from_fileswith local PDF/image paths — OCR only, nothing is savedReview the extracted data
Create:
create_invoiceswith the reviewed values
Permissions
Some tools require a partner permission to be enabled on your account, otherwise the API
returns 403 FORBIDDEN:
Permission | Tools |
|
|
|
|
|
|
Contact the Cresium team to enable them.
Authentication
All requests are signed using HMAC-SHA256. The server handles this transparently:
signature = HMAC-SHA256("{timestamp}|{METHOD}|{path+query}|{body}", secret) → base64The signed path includes the query string exactly as sent. Headers sent on every request:
x-api-key, x-company-id, x-timestamp, x-signature. Requests are rejected if the
timestamp is more than 60 seconds old, so keep the host clock NTP-synced.
License
MIT
Available Tools
12 toolsconfirm_transactionA
Confirm a previewed transaction, moving it from PREVIEW to PENDING status for processing. Only works on transactions in PREVIEW status.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Transaction ID to confirm |
create_invoicesC
Create one or more invoices (accounts receivable). Each invoice represents an amount the company expects to receive from a customer.
| Name | Required | Description | Default |
|---|---|---|---|
| invoices | Yes | Array of invoice objects to create |
create_paymentsB
Create one or more payments (accounts payable). Each payment represents an amount the company owes to a supplier/creditor.
| Name | Required | Description | Default |
|---|---|---|---|
| payments | Yes | Array of payment objects to create |
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.
| Name | Required | Description | Default |
|---|---|---|---|
| type | Yes | Type of signature request | |
| id | Yes | ID of the entity to sign (transaction, bulk, or payroll) |
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.
| Name | Required | Description | Default |
|---|---|---|---|
| toId | Yes | Destination address ID (from lookup_bank_address response) | |
| amount | Yes | Transfer amount as string for decimal precision | |
| currencyCode | Yes | Currency code | |
| tag | No | Optional transaction tag | |
| sendingDate | No | Optional scheduled date (ISO 8601) | |
| description | No | Optional transfer description/concept |
get_balanceB
Get wallet balances for the company. Returns balance, lockedBalance, investedBalance, availableBalance, and currency for each wallet.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_transactionA
Get a single transaction by ID. Returns the full transaction object including from/to addresses, amounts, fees, status, and related entities.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Transaction ID |
health_checkB
Check if the Cresium API is available and responding
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
list_invoicesB
List all company invoices. Returns the full list of invoices with their status, amounts, payer information, and related data.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
list_paymentsB
List all company payments. Returns the full list of payments with their status, amounts, and related data.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
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.
| Name | Required | Description | Default |
|---|---|---|---|
| value | Yes | CBU, CVU, or alias to look up |
search_transactionsB
Search and filter company transactions with pagination. Supports filtering by date range, type, tag, status, external ID, and more.
| Name | Required | Description | Default |
|---|---|---|---|
| fromDate | No | Start date filter (ISO 8601) | |
| toDate | No | End date filter (ISO 8601) | |
| types | No | Transaction types to filter (DEPOSIT, WITHDRAWAL, YIELD, etc.) | |
| tags | No | Transaction tags to filter (SALARY, SUPPLIER, SERVICE, RENTAL) | |
| states | No | Transaction statuses to filter (SUCCESS, PENDING, PROCESSING, FAILED, PREVIEW) | |
| externalId | No | Filter by external ID | |
| nameAmountFilter | No | Filter by name or amount | |
| cursor | No | Pagination cursor from previous response | |
| pageSize | No | Number of results per page (default: 10) | |
| field | No | Sort field | |
| order | No | Sort order | |
| depositAddressIds | No | Filter by deposit address IDs | |
| sendingFromDate | No | Filter scheduled transactions from date (ISO 8601) | |
| sendingToDate | No | Filter scheduled transactions to date (ISO 8601) | |
| scheduledTransactions | No | Include only scheduled transactions |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
12 tool updates
v1.0.0- First observed
confirm_transaction - First observed
create_invoices - First observed
create_payments - First observed
create_signature_request - First observed
create_transfer_preview - First observed
get_balance - First observed
get_transaction - First observed
health_check - First observed
list_invoices - First observed
list_payments - First observed
lookup_bank_address - First observed
search_transactions
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.
Related MCP Connectors
Financial intelligence for AI: manage balances, transactions, payments, and more
Connect AI agents to bank accounts, transactions, balances, and investments.
Complete financial infrastructure for AI agents — payments, lending, escrow & more.
Connect AI agents to financial institution origination, analytics, and compliance workflows.
Related MCP Servers
- AlicenseNot gradedqualityFmaintenanceEnables AI agents to perform financial transactions such as direct payments, escrows, and bounty management using natural language with zero code integration. It provides a comprehensive suite of tools for fund streaming, subscriptions, and reputation tracking to facilitate secure agent-to-agent commerce.29 npmMIT
- FlicenseBqualityCmaintenanceEnables AI assistants to trade FX, manage beneficiaries, check balances, request quotes, and configure rate alerts and market orders via the CurrencyTransfer API.51-

Wallbit MCPofficial
FlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with Wallbit's API for financial operations like checking balances, trading stocks, and managing accounts.-- AlicenseAqualityDmaintenanceEnables AI agents to manage financial operations including balance checks, money transfers, invoicing, spending policies, and audit logs through the PayGent API.13MIT