Mercado Pago MCPInstall

Overview

This node integrates with the Mercado Pago MCP (Mercado Pago Checkout Pro) API to manage various payment-related resources such as payments, orders, customers, preferences, webhooks, notifications, and documentation searches. Specifically for the Preference - Get operation, it retrieves detailed information about a checkout preference by its ID.

Use cases include:

• Fetching checkout preference details to verify or display payment options configured in Mercado Pago.
• Integrating with e-commerce platforms to dynamically retrieve preference data before redirecting users to checkout.
• Auditing or troubleshooting existing preferences by retrieving their current state from Mercado Pago.

Example: Given a preference ID, the node fetches the corresponding checkout preference object, which includes items, payment settings, and URLs needed to complete a purchase.

Properties

Output

The node outputs a JSON object containing:

• type: A string indicating the operation type, here "preference_retrieved".
• preference: An object representing the retrieved checkout preference, including all its details as returned by the Mercado Pago API (such as items, payer info, back URLs, payment methods, etc.).
• success: Boolean true indicating the operation succeeded.
• timestamp: ISO 8601 timestamp of when the response was generated.

If an error occurs, the output JSON will contain:

• error: Error message string.
• success: Boolean false.
• timestamp: Timestamp of the error occurrence.
• resource: The resource name ("preference").
• operation: The operation name ("get").

No binary data is produced by this operation.

Dependencies

• Requires an API key credential for Mercado Pago MCP API authentication.
• Uses Axios HTTP client internally to make REST API calls to Mercado Pago endpoints.
• The node expects the Mercado Pago API endpoint and access token to be provided via credentials.
• No additional environment variables are required beyond the API credentials.

Troubleshooting

• Common issues:

  • Invalid or missing preference ID: The node requires a valid preference ID; otherwise, the API call will fail.
  • Authentication errors: Ensure the API key credential is correctly configured and has permissions to access preferences.
  • Network or connectivity problems may cause request failures.

• Error messages:

  • "Card token is required for card payments" or "Issuer ID is required for card payments" do not apply here but appear in other operations.
  • API errors from Mercado Pago will be passed through in the error message field.

• Resolution tips:

  • Verify the preference ID format and existence in your Mercado Pago account.
  • Check that the API credentials are valid and have not expired.
  • Enable "Continue on Fail" in the node settings if you want the workflow to proceed despite errors.

Links and References

• Mercado Pago Checkout Preferences API Documentation
• Mercado Pago Developer Portal
• Axios HTTP Client

This summary focuses exclusively on the Preference - Get operation as requested.