Skip to main content
Glama
Yugo MCP Server

Yugo MCP Server

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 install

2. Configure environment

cp .env.example .env
# Edit .env and set your YUGO_API_KEY

3. Build & run

npm run build
npm start

Or for development:

npm run dev

Environment Variables

Variable

Required

Default

Description

YUGO_API_KEY

Yes

—

Your Yugo API key (contact support@yugo.finance)

YUGO_BASE_URL

No

https://sandbox-api.yugo.finance/api/v2

API base URL. Set to https://api.yugo.finance/api/v2 for production

TRANSPORT

No

stdio

Transport type: stdio or sse

PORT

No

3000

HTTP port (only used with SSE transport)

Available Tools

Auto-generated from the OpenAPI spec. Currently includes:

Tool

Description

create_payin

Create a new payin — accept funds from a payer

get_payin_by_id

Get payin details by ID

get_payins

List payins (paginated, filterable by reference)

create_payout

Create a new payout — send funds to a recipient

get_payout_by_id

Get payout details by ID

get_payouts

List payouts (paginated, filterable by reference)

get_banks

List available banks for open banking

get_accounts

List merchant accounts and balances

MCP Resources

URI

Description

yugo://spec

Full OpenAPI 3.1 specification

yugo://rails

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.js

Connect 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 build

Restart 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 Rails

License

MIT

Available Tools

8 tools
create_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

    A4/5.0

    Scored across 8 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      An 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.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Centralizes 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
    • F
      license
      A
      quality
      D
      maintenance
      Enables 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.
      32
      2
      -