Mercado Pago MCP icon

Mercado Pago MCP

Integração com MCP Server do Mercado Pago

Actions26

Overview

This node integrates with the Mercado Pago MCP (Mercado Pago's server) to handle various payment-related operations, including processing notifications received from webhooks. Specifically, for the Notification - Process operation, it processes raw notification data sent by Mercado Pago via webhook and retrieves detailed information about the event.

Typical use cases include:

  • Automatically handling payment or order status updates triggered by Mercado Pago webhook notifications.
  • Enriching incoming notification data with full payment or order details by fetching them from Mercado Pago API.
  • Integrating real-time payment/order event processing into workflows without manual intervention.

For example, when a payment notification is received, this node can process the raw notification JSON, fetch the full payment details from Mercado Pago, and output structured data for further workflow steps such as updating databases or triggering emails.

Properties

Name Meaning
Notification Data The raw notification data received from the Mercado Pago webhook in JSON format. Required.

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 raw notification JSON parsed from input.
  • Depending on the notification type:
    • For "payment" notifications:
      • payment_details: Full payment information fetched from Mercado Pago API.
      • event_type: Set to "payment_notification".
    • For "merchant_order" notifications:
      • order_details: Full merchant order information fetched from Mercado Pago API.
      • event_type: Set to "order_notification".
  • success: Boolean flag indicating successful processing (true).
  • timestamp: ISO timestamp of when the processing occurred.

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

The node does not output binary data.

Dependencies

  • Requires an API key credential for Mercado Pago MCP with access token and endpoint URL.
  • Uses the Mercado Pago REST API endpoints to fetch payment or order details.
  • Requires network connectivity to Mercado Pago API.
  • 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 representing the webhook payload.
  • API authentication errors: Verify that the Mercado Pago API credentials are correctly configured and have necessary permissions.
  • Network issues: Confirm that the node can reach Mercado Pago API endpoints.
  • Unsupported notification types: The node currently supports "payment" and "merchant_order" notification types; other types may not be processed.
  • Error messages:
    • If card token or issuer ID is missing for card payments (not relevant here but common in payment operations), the node throws an error.
    • General HTTP errors from Mercado Pago API calls will be surfaced; check API keys and request parameters.
  • To continue processing despite errors, enable the node's "Continue On Fail" option.

Links and References


This summary focuses exclusively on the Notification - Process operation of the Mercado Pago MCP node based on static code analysis and provided property definitions.

Discussion