Mercado Pago MCP

Integração com MCP Server do Mercado Pago

Actions26

Documentation Actions
- Search
Payment Actions
Order Actions
Customer Actions
Preference Actions
Webhook Actions
Notification Actions
- Get
- Process

Overview

This node integrates with the Mercado Pago MCP (Mercado Pago Cloud Platform) API, providing various operations across multiple resources such as payments, orders, customers, preferences, webhooks, notifications, and documentation. Specifically for the Documentation - Search operation, it allows users to search Mercado Pago's official documentation by submitting a query string and selecting a language.

This is useful when you want to programmatically retrieve relevant documentation content or help articles from Mercado Pago without manually browsing their site. For example, you could automate fetching integration guides or troubleshooting tips related to payment processing or checkout features in different languages.

Properties

Name	Meaning
Query	The search term or phrase to look up in Mercado Pago's documentation.
Language	The language of the documentation to search in. Options: Português (`pt`), English (`en`), Español (`es`).

Output

The output JSON contains the following fields:

query: The original search query string.
language: The language code used for the search.
result: The raw result data returned from the Mercado Pago MCP API containing the search results.
type: A fixed string "documentation_search" indicating this output relates to a documentation search.

Additionally, each output item includes metadata:

success: Boolean indicating if the operation succeeded.
timestamp: ISO timestamp of when the operation was performed.

No binary data is produced by this operation.

Dependencies

Requires an API key credential for Mercado Pago MCP with access token and endpoint URL.
Uses the Axios HTTP client library to make POST requests to the Mercado Pago MCP server.
The node expects proper configuration of the Mercado Pago MCP API credentials within n8n.

Troubleshooting

Common issues:
- Invalid or expired API token will cause authorization errors.
- Network connectivity problems may prevent reaching the MCP endpoint.
- Providing an empty or invalid query string will likely return no results or an error.
- Unsupported language codes may yield empty or irrelevant results.
Error messages:
- Authorization errors typically indicate missing or incorrect API credentials.
- HTTP request failures may show network or endpoint errors.
- Validation errors if required parameters like query are missing.
Resolutions:
- Verify that the Mercado Pago MCP API credentials are correctly set up and valid.
- Ensure the query string is meaningful and not empty.
- Confirm the selected language is one of the supported options.
- Check network connectivity and endpoint accessibility.

Links and References

This summary focuses exclusively on the Documentation - Search operation as requested. Other resources and operations are available but not covered here.