Skip to main content
POST
The Blnk MCP server exposes your Core instance through the Model Context Protocol (MCP). AI tools such as Cursor, Claude Desktop, and ChatGPT connect to this endpoint, authenticate with Blnk Cloud credentials, and call tools to read or write ledger data. All MCP traffic is routed through Blnk Cloud. AI clients never connect directly to your Core instance. Cloud validates credentials, enforces scopes, and forwards authorized operations to the target instance.

Set up your client

1

Create authentication credentials

Choose either an API key or OAuth credentials. Both need mcp:read and mcp:write.
Create an API key with MCP scopes in Settings > API Keys.
2

Get your MCP endpoint

Go to Settings > MCP and copy the configuration for your app.
3

Configure your MCP client

  1. Open Cursor Settings.
  2. Go to Features > MCP Servers.
  3. Click Add Server.
  4. Paste the configuration from the previous step (full JSON for API keys, or the endpoint URL for OAuth).
4

Start chatting with your ledger

You can now query, explore, and update Blnk data from your assistant.

What you can ask

  1. Monitor activity
    • “Show me all transactions from the last 24 hours”
    • “What changed since yesterday?”
  2. Check balances
    • “What is the current balance for wallet bln_wallet_456?”
    • “Show me all negative or low balances”
  3. Investigate issues
    • “Find failed or voided transactions”
    • “Get the transaction with reference order_456”
  4. Review large movements
    • “Show all USD transactions over $5,000”
    • “List unusually large transactions today”
  5. Answer operational questions
    • “How much money moved today?”
    • “What is the total balance across all customer wallets?”

Supported tools

Blnk MCP registers 33 tools.
  • create_ledger - Create a new ledger for organizing balances
  • get_ledger - Retrieve ledger details by ID
  • list_ledgers - List all ledgers

Response

Blnk MCP follows the Model Context Protocol specification. Request and response formats, session lifecycle, transport, and error handling are defined by the MCP standard. Most MCP clients handle the protocol automatically. If you are building a custom client, refer to the MCP specification for message structure, initialization, and tool invocation.

Need help?

We are very happy to help you make the most of Blnk, regardless of whether it is your first time or you are switching from another tool. To ask questions or discuss issues, please contact us or join our Discord community.