Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MP_ACCESS_TOKENYesMercado Pago access token. Required by every tool except `verify_webhook_signature`.
MP_ALLOW_WRITESNoSet to `true` to register the write tools. Same as `--allow-writes`. Defaults to false.
MP_WEBHOOK_SECRETNoDefault secret used by `verify_webhook_signature`.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_paymentA

Fetch one Mercado Pago payment by ID, including status, status_detail, amounts, payer, fees, and refunds.

search_paymentsB

Search payments on the account by status, external_reference, payer email, and date range. Returns paging info and compact summaries unless compact=false.

get_merchant_orderA

Fetch a merchant order by ID: order_status, total vs paid amount, items, and every payment attached to it. Useful when a webhook arrives with topic=merchant_order.

get_preferenceB

Fetch a Checkout Pro preference by ID: items, back_urls, notification_url, external_reference, expiration, and init_point.

list_payment_methodsB

List payment methods available to the account or to a country site, optionally filtered by payment type.

verify_webhook_signatureA

Verify a Mercado Pago webhook x-signature locally with HMAC-SHA256. Runs offline and needs no access token. Returns whether it is valid and the signed manifest for debugging.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 6 tools

Disambiguation5/5

Each tool targets a distinct resource or action: single payment, merchant order, payment search, Checkout Pro preference, payment method catalog, and offline webhook signature verification. The two 'get_*' tools differ clearly by resource (payment vs merchant_order vs preference), and verify_webhook_signature is unmistakable. No two tools compete for the same request.

Naming Consistency5/5

All names follow a clean snake_case verb_noun pattern: get_payment, get_merchant_order, search_payments, get_preference, list_payment_methods, verify_webhook_signature. Plural/singular usage matches whether the operation is a list/search versus a single fetch.

Tool Count4/5

Six tools is a tight, well-scoped surface for a payments/checkout integration, with each tool earning its place. It leans slightly thin given the breadth of the Mercado Pago domain, but nothing is redundant.

Completeness3/5

The surface is read-only: it can fetch and search payments and orders and verify webhooks, but there is no create_payment, create_preference, refund_payment, or cancel operation, so agents cannot complete write-side workflows. Refund data is only visible indirectly through get_payment. These are notable gaps for a payment integration rather than minor ones.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues