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 orders and related payment operations. Specifically, for the Order - Capture operation, it captures a previously authorized order payment. This is useful in scenarios where an order was authorized but not yet charged, allowing merchants to finalize the payment capture when ready.

Practical examples:

  • After authorizing an order payment during checkout, you can use this node to capture the payment once the product is shipped.
  • Automate capturing payments for orders that have passed fraud checks or manual review.
  • Integrate with your ERP or fulfillment system to trigger payment capture only after inventory confirmation.

Properties

Name Meaning
ID do Pedido The unique identifier of the order to perform operations on, such as capture, get, cancel.

Output

The node outputs a JSON object containing the result of the capture operation. The structure includes:

  • type: A string indicating the type of response, here "order_captured".
  • order: An object with detailed information about the captured order returned by Mercado Pago API.
  • success: Boolean indicating if the operation succeeded (true).
  • timestamp: ISO 8601 timestamp of when the operation was performed.

Example output snippet:

{
  "type": "order_captured",
  "order": {
    /* Mercado Pago order details */
  },
  "success": true,
  "timestamp": "2024-06-01T12:00:00.000Z"
}

No binary data output is produced by 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.
  • Requires network access to Mercado Pago API.
  • The node uses HTTP POST to /v1/orders/{orderId}/capture endpoint to perform the capture.

Troubleshooting

  • Common issues:

    • Invalid or expired API token: Ensure the API key credential is valid and has not expired.
    • Incorrect Order ID: Verify the order ID exists and is authorized for capture.
    • Network connectivity problems: Confirm the server running n8n can reach Mercado Pago API endpoints.
    • Attempting to capture an order that is already captured or canceled will likely return an error from the API.

  • Error messages:

    • Errors thrown by the node include the original API error message.
    • If the card token or issuer ID is missing for card payments (not applicable here but relevant for other operations), the node throws a specific error.
    • For capture operation, errors typically relate to invalid order state or permissions.

  • Resolution tips:

    • Double-check input parameters, especially the order ID.
    • Check Mercado Pago dashboard or logs for more details on order status.
    • Enable "Continue On Fail" in the node settings to handle errors gracefully in workflows.

Links and References

This summary focuses exclusively on the Order - Capture operation as requested.

Discussion