We are evolving our integration process. Discover the new Orders API

Available tools - MCP Server - Mercado Pago Developers
AI resources

Available MCP server tools

Mercado Pago offers the following list of tools.

Depending on the client you are using, some tools may require you to specify the application for which you want to make configurations.
ToolDescriptionParametersSuggested prompt
search-documentationPerforms code or text searches in Mercado Pago Developers documentation.-query (string, required): Term to search.
-language (string, required, enum): Language in which the search is performed. Allowed values are 'es' (español), 'en' (english), 'pt' (português).
Search in Mercado Pago documentation {query}.
quality_checklistProvides a detailed list of fields evaluated by Mercado Pago to optimize your integration quality. Additionally, it provides best practices recommendations to improve your implementation quality during the development stage, ensuring a production release that meets the necessary standards.N/AProvide me with the list of fields that my integration must meet to approve Mercado Pago quality standards. Format the output in two tables, the first with required fields and the second with optional improvements or best practices, if any.
quality_evaluationBased on a productive payment identifier, it measures the quality of your integration, evaluating its correct functioning and compliance with Mercado Pago standards.-payment_id (number, required): Payment identifier that will be used to perform the quality evaluation.Evaluate the quality of my integration using the {payment_id}. If necessary, propose improvements to achieve the best possible score.
save_webhookConfigures or updates Webhook notification settings to receive alerts from Mercado Pago about transactions associated with an application, including notification topics, production and test URLs.-callback (string, optional): Production URL to which Webhook notifications will be sent.
-callback_sandbox (string, optional): Test URL to which Webhook notifications will be sent.
-topics (array, string, optional): List of topics to be configured to receive notifications. If not sent, the payment topic will be considered by default.
Configure Webhook notifications for {topics} for testing URL {callback}.
simulate_webhookSimulates the sending of previously configured Webhook notifications for your integration and tests the functioning of your implementation before receiving real notifications.-topic (string, optional): Topic of Webhook notifications to simulate.
-url_callback (string, optional): URL to which the notification simulation will be sent. If not provided, the simulation is sent to the previously configured URL.
-resource_id (string, required): ID of the resource to be simulated. For example, a payment_id.
-callback_env_production (boolean, optional): allows you to select whether the environment to use for simulation is production (true) or sandbox (false). If not sent, the default environment is sandbox.
Simulate a {topic} notification in {callback_env_production} with ID {resource_id}.
notifications_history_diagnosticsPerforms a diagnosis and obtains reports of events triggered on a specific integration, including delivery metrics and analysis in case it fails, to implement improvements.N/AShow me a summary of my notification history to validate the functioning of my Webhook system.
create_test_userCreates test users with assigned credentials and available money to test payment flows.-site_id (string, required): Site/country ID for which the test account is created. It can be: MLA (Argentina), MLB (Brazil), MLC (Chile), MLM (Mexico), MLU (Uruguay), MPE (Peru), MCO (Colombia)
-description (string, required): Description or name of the test user.
-profile (string, required): Profile type, which can be seller, buyer, or integrator integrator.
-amount (number, optional): Initial amount of money assigned to the user, which must comply with the established limits for the country of operation. If not sent, 1000 will be assigned by default.
Create a Mercado Pago test user for Argentina (MLA) with a seller profile, with the description 'Seller user for checkout testing' and an initial account money of 5000.
add_money_test_userAdds money to a test user account in Mercado Pago to test payment flows. The amount will be validated and adjusted according to the specific limits of each country.-test_user_id (number, required): User ID of the test user that will have the money assigned.
-amount (number, required): Amount of money to add, which must comply with the established limits for the country of operation assigned to the user: for Argentina, Mexico, Chile, Uruguay, Peru and Colombia, it must be between 1000 and 50000; for Brazil, between 100 and 50000 BRL.
Add 10000 balance to the test user account with ID {test_user_id}.
get_applicationGets information about the applications created in a Mercado Pago Developers account. Works as support for tools that require this information to execute correctly.N/AN/A (will only be invoked by other tools if they need to confirm information about applications to execute).