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 (Mercado Pago's API platform) to process various operations related to payments, orders, customers, preferences, webhooks, documentation search, and notifications. Specifically for the Notification - Process operation, it processes raw notification data received from a webhook, interprets the notification type, and fetches detailed information about the payment or merchant order referenced in the notification.

Typical use cases include:

Automatically handling incoming webhook notifications from Mercado Pago.
Fetching detailed payment or order information based on notification events.
Integrating real-time payment/order updates into workflows for further processing, such as updating databases, triggering alerts, or managing order fulfillment.

Example: When a payment notification is received via webhook, this node can process the notification payload, retrieve full payment details from Mercado Pago, and output them for downstream workflow steps.

Properties

Name	Meaning
Notification Data	The raw JSON notification data received from the webhook. This should be the exact payload sent by Mercado Pago's webhook system.

Output

The node outputs a JSON object containing:

type: A string indicating the type of processed notification, e.g., "notification_processed".
original_data: The original parsed notification JSON object received.
Depending on the notification type:
- For "payment" notifications:
  - payment_details: Detailed payment information fetched from Mercado Pago API.
  - event_type: Set to "payment_notification".
- For "merchant_order" notifications:
  - order_details: Detailed merchant order information fetched from Mercado Pago API.
  - event_type: Set to "order_notification".
success: Boolean flag indicating if the operation was successful (true).
timestamp: ISO timestamp of when the node executed.

If an error occurs and "Continue On Fail" is enabled, the output will contain an error message and success set to false.

The node does not output binary data.

Dependencies

Requires an API key credential for Mercado Pago MCP with appropriate permissions.
Uses the Mercado Pago REST API endpoints to fetch payment and order details.
Requires network access to Mercado Pago API endpoints.
No additional environment variables are needed beyond the configured credentials.

Troubleshooting

Missing or invalid notification data: Ensure that the "Notification Data" property contains valid JSON exactly as received from the webhook. Malformed JSON will cause parsing errors.
API authentication errors: Verify that the provided API key credential is valid and has necessary permissions.
Unsupported notification types: Currently supports "payment" and "merchant_order" notification types. Other types will result in output containing only the original data without additional details.
Network issues: Connectivity problems to Mercado Pago API endpoints will cause request failures.
Common error messages:
- "Card token is required for card payments" or "Issuer ID is required for card payments" appear in other operations but not relevant here.
- Errors from the Mercado Pago API will be propagated; check the error message for details like invalid IDs or permission issues.

To resolve errors:

Validate input JSON.
Check API credentials.
Confirm the notification type is supported.
Review Mercado Pago API status and connectivity.