AI integrations

MCP server

Connect an AI client to a Core instance through the Blnk MCP server.

POST/mcp/{instance_id}

The Blnk MCP server exposes a Core instance through the Model Context Protocol. Cursor, Claude Desktop, and ChatGPT connect to Cloud, and Cloud forwards authorized tool calls to that instance.

Clients do not open a connection to Core. Cloud checks the credential, enforces mcp:read and mcp:write, and sends the operation to the instance in the URL.

{
  "mcpServers": {
    "blnk": {
      "url": "https://api.cloud.blnkfinance.com/mcp/YOUR_INSTANCE_ID",
      "headers": {
        "X-blnk-key": "CLOUD_API_KEY"
      }
    }
  }
}

Set up your client

Create credentials

Create an API key or an OAuth client. Both need mcp:read and mcp:write.

Copy the MCP endpoint

Open Settings > MCP and copy the configuration for the instance.

{
  "mcpServers": {
    "blnk": {
      "url": "https://api.cloud.blnkfinance.com/mcp/YOUR_INSTANCE_ID",
      "headers": {
        "X-blnk-key": "CLOUD_API_KEY"
      }
    }
  }
}

Use the endpoint URL with your OAuth client id and client secret. The client signs in. You do not put a Cloud API key in the config.

https://api.cloud.blnkfinance.com/mcp/YOUR_INSTANCE_ID

Add the server to the client

Open Cursor settings, go to MCP, and add the server. Paste the JSON for an API key, or the endpoint URL for OAuth.

Add the configuration to claude_desktop_config.json.

~/Library/Application Support/Claude/claude_desktop_config.json

%APPDATA%\Claude\claude_desktop_config.json

Go to Settings > Apps. Open Advanced settings, enable Developer mode, and click Create app.

ChatGPT MCP app form with name, server URL, and OAuth fields

Name: A name such as Blnk MCP.
MCP Server URL: The endpoint from the previous step.
Authentication: OAuth, then the client id and client secret.

Click Create and sign in to Blnk Cloud when asked.

Ask about the ledger

The client can read and update ledger data through the tools below.

What you can ask

Activity: Transactions from the last 24 hours, or what changed since yesterday.
Balances: The balance for a wallet, or balances that are negative or low.
Failures: Failed or voided transactions, or a transaction by reference.
Large movements: USD transactions over $5,000, or unusually large transactions today.
Totals: How much moved today, or the total across customer wallets.
Lake: The lake schema, a count of APPLIED transactions last month, or a saved query on a daily schedule.
Workflows: A balance monitor, a bulk inflight commit, or a reconciliation run.

Supported tools

Blnk MCP registers 74 tools: 4 ledgers, 14 balances, 13 transactions, 10 identities, 3 search, 4 filters, 7 reconciliation, 5 hooks, 1 metadata, 2 system, and 11 lake.

create_ledger
get_ledger
list_ledgers
update_ledger

create_balance
get_balance
list_balances
get_balance_by_indicator
take_balance_snapshots
get_historical_balance
get_balance_lineage
update_balance_identity
create_balance_monitor
get_balance_monitor
list_balance_monitors
list_balance_monitors_by_balance
update_balance_monitor
delete_balance_monitor

record_transaction
get_transaction
get_transaction_by_reference
list_transactions
commit_inflight
void_inflight
bulk_commit_inflight
bulk_void_inflight
recover_queued_transactions
refund_transaction
schedule_transaction
bulk_transactions
get_transaction_lineage

create_identity
get_identity
list_identities
update_identity
delete_identity
tokenize_field
tokenize_identity
detokenize_field
detokenize_identity
get_tokenized_fields

search
start_reindex
get_reindex

query_transactions
query_balances
query_ledgers
query_identities

upload_reconciliation_data
create_matching_rule
update_matching_rule
delete_matching_rule
start_reconciliation
start_instant_reconciliation
get_reconciliation

create_hook
update_hook
get_hook
list_hooks
delete_hook

update_metadata

get_health
get_metrics

lake_schema
lake_query
list_lake_queries
get_lake_query
create_lake_query
update_lake_query
delete_lake_query
list_lake_query_runs
get_lake_query_run
put_lake_query_schedule
delete_lake_query_schedule

Response

Blnk MCP follows the Model Context Protocol specification. Message shape, session lifecycle, transport, and errors are defined there. Most clients handle that for you.