Mcp Cobre

io.github.codesparPublished by GitHub account codesparv0.1.0Updated Oct 24, 2026

MCP server for Cobre — CO/MX B2B treasury: balances, counterparties, money movements

VerifiedSTDIODesktop onlyFinanceBusiness & Commerce

Overview

AI-generated overview

Local MCP server for the Cobre B2B treasury platform, letting an assistant view balances, register payout counterparties and create outbound money movements in

What you can do
List and read account balances across visible accounts, or fetch one balance by id. Register payout beneficiaries (Colombian bank accounts or Mexican CLABE) and list or look up existing counterparties. Create outbound payouts over Colombian instant rails or Mexico's SPEI, and list or check the status of money movements.
When to use it
Useful when an assistant needs to work with Cobre treasury operations for Colombian or Mexican business payments: checking balances, managing beneficiaries, or initiating and tracking payouts without leaving the chat.
Requirements
Runs locally via npx (Node.js). Requires a Cobre API user id in COBRE_USER_ID and a secret in COBRE_SECRET; the server authenticates with OAuth2 client credentials and caches the token. COBRE_BASE_URL optionally overrides the API host. Network access to the Cobre API is needed.
Before you install
The credentials in COBRE_USER_ID and COBRE_SECRET grant access to a live treasury account. The server can register new payout beneficiaries and create outbound money movements, which move real funds; review any payout before approving it. Balance and counterparty data is sent to the Cobre API.

Installation

In SourceWeft

  1. Open Mcp Cobre in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@codespar/mcp-cobre

MCP server for Cobre — Colombian/Mexican B2B treasury and payouts platform: balance visibility, counterparty registration, and outbound money movements over Colombia's instant rails and Mexico's SPEI.

[npm] [License: MIT]

Auth is OAuth2 client credentials (POST /v1/auth); the server caches the access token and refreshes before expiry.

Quick Start

Claude Desktop

Add to ~/.config/claude/claude_desktop_config.json:

json
{  "mcpServers": {    "cobre": {      "command": "npx",      "args": ["-y", "@codespar/mcp-cobre"],      "env": {        "COBRE_USER_ID": "your-user-id",        "COBRE_SECRET": "your-secret"      }    }  }}

Claude Code

bash
claude mcp add cobre --env COBRE_USER_ID=uid --env COBRE_SECRET=sk -- npx -y @codespar/mcp-cobre

Tools (8)

ToolDescription
list_balancesBalances across every visible account
get_balanceOne balance by id
create_counterpartyRegister a payout beneficiary (CO bank account or MX CLABE)
list_counterpartiesList registered counterparties
get_counterpartyOne counterparty by id
create_money_movementCreate an outbound payout (instant rails / SPEI)
get_money_movementMovement status by id
list_money_movementsList movements

Environment

VariableRequiredDescription
COBRE_USER_IDyesAPI credential user id
COBRE_SECRETyesAPI credential secret
COBRE_BASE_URLnoOverride the API host (default https://api.cobre.co)

Docs

Enterprise

Need governance, budget limits, and audit trails for agent-driven payments on Cobre? CodeSpar Enterprise adds a policy engine, payment routing, and compliance templates on top of these MCP servers.

License

MIT

Source: packages/colombia/cobre/README.md at commit d0a519a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts