Mercado Pago MCP

Overview

The node integrates with Mercado Pago's MCP Server to manage orders and their payment processing. Specifically, the Process Order operation triggers the processing of a payment for an existing order by its ID. This is useful in scenarios where an order has been created and authorized but requires explicit processing to complete the payment flow.

Typical use cases include:

• E-commerce platforms that create orders and later process payments once certain conditions are met.
• Systems that separate order creation from payment processing for better control or compliance.
• Automations that handle order lifecycle events, such as capturing or refunding payments after processing.

Example: After creating an order in Mercado Pago, you can use this node operation to process the payment, moving it forward in the payment lifecycle.

Properties

Output

The node outputs a JSON object containing the result of the order processing request. The structure includes:

• type: A string indicating the type of response, here "order_processed".
• order: An object with detailed information about the processed order returned by Mercado Pago's API.
• success: A boolean indicating if the operation was successful (true).
• timestamp: ISO 8601 timestamp of when the operation was executed.

No binary data output is produced by this operation.

Example output snippet:

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

Dependencies

• Requires an API key credential for Mercado Pago MCP API with appropriate permissions.
• Uses Axios HTTP client internally to communicate with Mercado Pago endpoints.
• The node expects the Mercado Pago MCP API endpoint and access token to be configured in the credentials.
• No additional environment variables are required beyond the credential setup.

Troubleshooting

• Common issues:

  • Invalid or missing order ID will cause the API call to fail.
  • Expired or incorrect API authentication token will result in authorization errors.
  • Network connectivity problems may cause request timeouts or failures.

• Error messages:

  • "Card token is required for card payments" (not applicable here but common in payment operations).
  • HTTP 401 Unauthorized: Check API credentials and token validity.
  • HTTP 404 Not Found: Verify the order ID exists in Mercado Pago.
  • HTTP 400 Bad Request: Ensure all required parameters are correctly set.

• Resolution tips:

  • Double-check the order ID input.
  • Confirm the API credentials are valid and have necessary scopes.
  • Review Mercado Pago API documentation for error codes and meanings.
  • Enable "Continue on Fail" in n8n to handle errors gracefully during workflow execution.

Links and References

• Mercado Pago Orders API Documentation
• Mercado Pago MCP Server Integration Guide
• n8n Documentation on Creating Custom Nodes