Yugo MCP Server
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., "@Yugo MCP Server Create a payout of 100 USD to Jane"
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.
Yugo MCP Server
An MCP (Model Context Protocol) server for the Yugo Payments API. Auto-generates tools from the OpenAPI spec — new API endpoints are supported with zero code changes.
Features
OpenAPI-driven — Tools are auto-generated from the Yugo OpenAPI spec
Future-proof — New endpoints auto-register when the spec is updated
Dual transport — stdio (local) and SSE (remote) support
MCP Resources — Exposes the OpenAPI spec and payment rails reference data
Idempotency — Auto-generates idempotency keys for POST requests
Error handling — Parses RFC 9457 problem details into readable messages
Related MCP server: Payments MCP
Quick Start
1. Install dependencies
npm install2. Configure environment
cp .env.example .env
# Edit .env and set your YUGO_API_KEY3. Build & run
npm run build
npm startOr for development:
npm run devEnvironment Variables
Variable | Required | Default | Description |
| Yes | — | Your Yugo API key (contact support@yugo.finance) |
| No |
| API base URL. Set to |
| No |
| Transport type: |
| No |
| HTTP port (only used with SSE transport) |
Available Tools
Auto-generated from the OpenAPI spec. Currently includes:
Tool | Description |
| Create a new payin — accept funds from a payer |
| Get payin details by ID |
| List payins (paginated, filterable by reference) |
| Create a new payout — send funds to a recipient |
| Get payout details by ID |
| List payouts (paginated, filterable by reference) |
| List available banks for open banking |
| List merchant accounts and balances |
MCP Resources
URI | Description |
| Full OpenAPI 3.1 specification |
| Supported payment methods, settlement methods, and currencies |
Usage with Claude Desktop
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"yugo": {
"command": "node",
"args": ["/path/to/yugo-mcp-server/dist/index.js"],
"env": {
"YUGO_API_KEY": "your_api_key_here"
}
}
}
}Usage with Cursor
Add to your Cursor MCP settings:
{
"mcpServers": {
"yugo": {
"command": "node",
"args": ["/path/to/yugo-mcp-server/dist/index.js"],
"env": {
"YUGO_API_KEY": "your_api_key_here"
}
}
}
}Usage with SSE (Remote)
TRANSPORT=sse PORT=3000 YUGO_API_KEY=your_key node dist/index.jsConnect your MCP client to http://localhost:3000/sse.
Updating the OpenAPI Spec
To pick up new API endpoints:
curl -sL https://docs.yugo.finance/openapi/payments.yaml -o openapi/payments.yaml
npm run buildRestart the server and new tools will be available automatically.
Architecture
This server is the MCP Server interface layer in the Yugo System Architecture. It runs as a separate process that calls the Yugo REST API.
AI Agent → MCP Server → Yugo REST API → Payment Core → Settlement RailsLicense
MIT
Available Tools
8 toolscreate_payinA
Create Payin — Create a new Payin resource - accepting funds from a Payer — [POST /payins]
Inputs: payer (required), amount (required), return_url (required), payment, +4 more.
create_payoutA
Create Payout — Create a new Payout resource - sending funds to a Recipient — [POST /payouts]
Inputs: amount (required), return_url (required), payment, recipient, +3 more.
get_accountsA
List Accounts — Retrieve a paginated list of accounts with their balances — [GET /accounts]
Inputs: page, currency, page_size.
get_banksA
List Banks — Retrieve a paginated list of banks available for open banking payments — [GET /banks]
Inputs: page, page_size.
get_payin_by_idA
Get Payin — Retrieve details of a specific Payin by its unique identifier — [GET /payins/{id}]
Inputs: id (required).
get_payinsA
List Payins — Retrieve a paginated list of all Payins for the merchant — [GET /payins]
Inputs: page, page_size, reference.
get_payout_by_idA
Get Payout — Retrieve details of a specific Payout by its unique identifier — [GET /payouts/{id}]
Inputs: id (required).
get_payoutsA
List Payouts — Retrieve a paginated list of all Payouts for the merchant — [GET /payouts]
Inputs: page, page_size, reference.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Each tool targets a distinct resource (payin, payout, bank, account) and action (create, list, get). The only potential confusion between create_payin and create_payout is resolved by the resource name in each.
All tools follow a consistent verb_noun pattern, using 'create_' for creation, 'get_' for retrieval, plural nouns for list operations, and '_by_id' for single item details. This makes the naming predictable and unambiguous.
Eight tools adequately cover the core payment operations (create and query payins/payouts) along with supporting resources (banks, accounts). This is well-scoped for a payments server without unnecessary bloat.
The tool surface covers creation and retrieval for payins and payouts, plus listing banks and accounts. While there is no cancel or update operation, these are not essential for a payment flow; a cancel for payouts could be a minor addition but the current set is functionally sufficient.
Related MCP Connectors
MCP server for Modern Treasury — payment orders, transactions, counterparties and ledgers.
Query and manage Mercoa AP/AR bill-pay: entities, invoices, transactions and payment methods.
Tools to explore SumUp accounts, payments, customers, and payouts.
Official BlindPay MCP server: stablecoin payouts, payins, quotes and customers for global payments.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables interaction with Velo Payments APIs for global payment operations, automatically generated using AG2's MCP builder from the Velo Payments OpenAPI specification.-
- AlicenseNot gradedqualityDmaintenanceCentralizes payment gateway integrations for Pagar.me (customers, recipients, Pix, credit card, splits, charges) and Woovi/OpenPix (Pix charges, refunds, webhook verification) through MCP tools.MIT

Conekta MCP Serverofficial
FlicenseAqualityDmaintenanceEnables interaction with the Conekta payment API to manage orders, customers, subscriptions, and financial transactions. It provides a comprehensive suite of tools for core payment operations like processing refunds, creating checkouts, and monitoring account balances.322-- AlicenseNot gradedqualityDmaintenanceEnables interaction with Paystack via MCP tools to get total transactions, create checkout links, and verify transactions.4MIT