Overview
This reference documents every MCP tool exposed by the Yuno MCP server. Each tool maps to a Yuno API endpoint and follows the Model Context Protocol specification.Underlying REST calls use the same authentication as the public API:
public-api-key and private-secret-key headers, plus account_id in the body on endpoints that take it. The MCP server reads sandbox credentials from its own environment variables (see LLM & MCP integration).MCP tools are designed for sandbox use during development and debugging. All tool calls count against your standard API rate limits.
Tool Summary
Tool Dependency Matrix
Some tools require outputs from other tools. This matrix shows prerequisites.Calling Order for Common Flows
Standard payment:create_checkout_session -> create_payment -> get_payment
Auth + capture: create_checkout_session -> create_payment -> capture_payment
Refund: get_payment (verify status) -> create_refund
Payout: create_recipient -> create_payout
Tool Specifications
create_checkout_session
Creates a new checkout session to initialize a payment flow. Input Schema:merchant_order_id values.
Error codes:
create_payment
Creates a payment against an existing checkout session. Input Schema:checkout_sessionmust reference an ACTIVE sessionamountmust match the session amountcountrymust match the session country- PIX payments in BR require
customer.document(CPF or CNPJ) - CARD payments require either
tokenorvaulted_token installmentsonly applies to CARD payments
get_payment
Retrieves payment details by ID. Use for polling payment status. Input Schema:create_payment output.
Rate limit: Standard API limits
Idempotency: Safe to call repeatedly (GET request).
Error codes:
list_payments
Returns a paginated list of payments. Input Schema:capture_payment
Captures a previously authorized payment. Only valid for payments inAUTHORIZED status.
Input Schema:
create_payment output (status changes to SUCCEEDED).
Parameter validation rules:
- Payment must be in
AUTHORIZEDstatus - Capture amount must not exceed authorized amount
- Partial capture is supported (amount < authorized amount)
cancel_payment
Cancels a pending or authorized payment. Input Schema:create_payment output (status changes to CANCELLED).
Error codes:
create_refund
Refunds a completed payment. Supports full and partial refunds. Input Schema:create_payment output (status changes to REFUNDED or PARTIALLY_REFUNDED).
Parameter validation rules:
- Payment must be in
SUCCEEDEDorPARTIALLY_REFUNDEDstatus - Refund amount must not exceed remaining refundable balance
- Omitting
amounttriggers a full refund
validate_payload
Client-side validation tool that checks a payment payload against Yuno’s schema without making an API call. Input Schema:create_customer
Creates a customer record for use in checkout sessions. Input Schema:create_recipient
Creates a payout recipient with bank account details. Input Schema:create_payout
Sends funds to a previously created recipient. Input Schema:Multi-Step Examples
Example: Complete Payment Flow
Example: Validate then Create
Rate Limiting
All MCP tools that make API calls share the same rate limits as direct API access.
When rate limited (HTTP 429), implement exponential backoff: