Mercado Pago MCP

Integração com MCP Server do Mercado Pago

Actions26

Documentation Actions
- Search
Payment Actions
Order Actions
Customer Actions
Preference Actions
Webhook Actions
Notification Actions
- Get
- Process

Overview

This node integrates with the Mercado Pago MCP Server to manage orders and their payment transactions. Specifically, for the Order - Create operation, it allows users to create a new order with detailed payment information such as transaction amount, description, payment method, and payer email. It also supports an option to either immediately capture the payment or just authorize it.

Typical use cases include:

E-commerce platforms creating orders and processing payments through Mercado Pago.
Automating order creation workflows where payment details are collected and sent to Mercado Pago.
Scenarios requiring control over payment capture timing (immediate capture vs. authorization only).

Example: Creating an order for a customer who wants to pay R$100.50 using a Visa card, with immediate capture enabled.

Properties

Name	Meaning
Valor da Transação	Transaction amount in Brazilian reais (R$).
Descrição	Description of the order (e.g., "Pagamento do pedido").
ID do Método de Pagamento	Payment method identifier (e.g., "visa", "pix", "master").
Email do Pagador	Email address of the payer.
Capturar	Boolean flag indicating whether to capture the payment immediately (`true`) or only authorize (`false`).

Output

The node outputs a JSON object containing the response from Mercado Pago's API after creating the order. The output includes:

type: A string indicating the type of response, here "order_created".
order: The full order data returned by Mercado Pago, including order ID, status, transaction details, and other metadata.
success: Always true if the operation succeeded.
timestamp: ISO timestamp of when the operation was performed.

If the operation fails and "Continue On Fail" is enabled, the output will contain an error message with success: false.

No binary data is output by this operation.

Dependencies

Requires an API key credential for Mercado Pago MCP API with appropriate permissions.
Uses Axios HTTP client internally to communicate with Mercado Pago endpoints.
The node expects the Mercado Pago API endpoint and access token to be configured via credentials.
No additional environment variables are required beyond the API authentication setup.

Troubleshooting

Missing or invalid API credentials: The node requires a valid access token to authenticate requests. Ensure the API key credential is correctly configured.
Invalid payment method ID: Using an unsupported or incorrect payment method ID will cause the API call to fail. Verify the payment method ID matches Mercado Pago's accepted values.
Incorrect email format: The payer email must be a valid email address; otherwise, the API may reject the request.
Capture flag misuse: If you want to only authorize without capturing, set Capturar to false. Setting it incorrectly might lead to unexpected payment states.
Network or API errors: Standard HTTP errors from Mercado Pago will be surfaced. Check network connectivity and API status.
Error messages: Errors thrown by the node include descriptive messages from the Mercado Pago API or internal validation errors like missing required parameters.

To resolve errors, verify all required properties are provided and valid, check API credentials, and consult Mercado Pago API documentation for specific error codes.