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 API) to manage various resources such as payments, orders, customers, preferences, webhooks, and notifications. Specifically, for the Notification - Get operation, it retrieves detailed information about a notification using its ID, which is typically received from a webhook event.

Use cases include:

  • Fetching detailed merchant order information related to a notification triggered by Mercado Pago.
  • Automating workflows that respond to payment or order notifications by retrieving full details for further processing.
  • Integrating Mercado Pago notifications into broader business processes like order fulfillment or customer communication.

Example: After receiving a notification ID from a webhook, this node can fetch the corresponding merchant order details to update your internal system or trigger additional actions.

Properties

Name Meaning
Notification ID The unique identifier of the notification received from the webhook. This is required to retrieve the specific notification details.

Output

The node outputs a JSON object containing:

  • type: A string indicating the type of response, here "notification_retrieved".
  • notification: An object with the detailed data of the merchant order associated with the notification ID.
  • success: Boolean indicating if the operation was successful (true).
  • timestamp: ISO 8601 timestamp of when the operation was performed.

The output structure corresponds to the full merchant order details fetched from Mercado Pago’s API for the given notification ID.

No binary data output is involved in this operation.

Example output snippet:

{
  "type": "notification_retrieved",
  "notification": {
    /* merchant order details object */
  },
  "success": true,
  "timestamp": "2024-06-01T12:00:00.000Z"
}

Dependencies

  • Requires an API key credential for Mercado Pago MCP with appropriate permissions.
  • The node makes HTTP requests to Mercado Pago’s API endpoints, specifically to:
    https://api.mercadopago.com/v1/merchant_orders/{notificationId}
  • Proper configuration of the credential with a valid access token is necessary.
  • Network connectivity to Mercado Pago’s API endpoints is required.

Troubleshooting

  • Common issues:

    • Invalid or missing Notification ID: The node requires a valid notification ID; ensure it is correctly provided.
    • Authentication errors: If the API key or access token is invalid or expired, the request will fail.
    • Network or API downtime: Temporary issues connecting to Mercado Pago’s API may cause failures.

  • Error messages:

    • Errors thrown by the node will include the error message from the HTTP request or credential validation.
    • If the notification ID does not exist or is incorrect, the API may return a 404 or similar error.

  • Resolutions:

    • Verify the notification ID is correct and corresponds to an existing notification.
    • Check and refresh the API credentials if authentication fails.
    • Ensure the node has internet access and Mercado Pago’s API is operational.

Links and References

Discussion