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 platform) to manage webhooks among other resources. Specifically, for the Webhook - Get operation, it retrieves detailed information about a specific webhook by its ID.

Common scenarios where this node is beneficial include:

  • Verifying the configuration and status of an existing webhook.
  • Debugging webhook issues by fetching current webhook details.
  • Automating management of webhook endpoints in your payment or notification workflows.

Practical example:

  • You have set up multiple webhooks to listen for payment events. Using this node, you can programmatically fetch the details of a particular webhook to confirm its URL, subscribed events, and status without manually checking the Mercado Pago dashboard.

Properties

Name Meaning
Webhook ID The unique identifier of the webhook to retrieve. This is required to specify which webhook's details to fetch.

Output

The node outputs a JSON object containing the webhook details under the webhook property. The output structure includes all data returned by the Mercado Pago API for the specified webhook, such as:

  • Webhook ID
  • URL endpoint configured
  • List of subscribed event topics (e.g., payment, plan, subscription, invoice)
  • Status and metadata related to the webhook

Additionally, the output includes:

  • type: A string indicating the type of response, here "webhook_retrieved".
  • success: Boolean flag indicating if the operation was successful.
  • timestamp: ISO timestamp of when the response was generated.

Example output snippet:

{
  "type": "webhook_retrieved",
  "webhook": {
    "id": "123456",
    "url": "https://example.com/webhook",
    "events": [
      { "topic": "payment" },
      { "topic": "plan" }
    ],
    ...
  },
  "success": true,
  "timestamp": "2024-06-01T12:00:00.000Z"
}

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for Mercado Pago MCP with appropriate permissions.
  • Uses the Mercado Pago REST API endpoint (https://api.mercadopago.com/v1/webhooks/{webhookId}).
  • Requires network access to Mercado Pago's API servers.
  • The node expects the credential to provide an access token used in the Authorization header.

Troubleshooting

  • Common issues:

    • Invalid or missing Webhook ID: The node requires a valid webhook ID; otherwise, the API will return an error.
    • Authentication errors: If the API key or access token is invalid or expired, the request will fail.
    • Network connectivity problems may cause timeouts or unreachable errors.

  • Error messages and resolutions:

    • "401 Unauthorized": Check that the API credentials are correctly configured and have not expired.
    • "404 Not Found": Verify that the provided Webhook ID exists and is correct.
    • "400 Bad Request": Ensure the Webhook ID parameter is properly formatted and not empty.
    • "500 Internal Server Error" or other server errors: Retry after some time or check Mercado Pago service status.

  • To handle errors gracefully, enable the node’s "Continue On Fail" option to allow workflow continuation despite failures.

Links and References

This summary focuses exclusively on the Webhook - Get operation as requested, based on static analysis of the provided source code and input properties.

Discussion