The Orders API for Checkout API now returns the 429 Too Many Requests error ("usage_quota_exceeded") to indicate that the per-client request limit has been reached. For more information about the error and how to resolve it, see the Possible errors documentation for Checkout API integration.

Added

• Offline mode: generate complete integration code without authentication, using bundled plugin files with official Mercado Pago documentation.
• Automatic product and country detection: identifies product and country from natural language input (e.g., "integrate Checkout Pro for Brazil").
• "/mp-test-cards [country]" command: retrieve test cards by country without login (BR, AR, MX, etc.).
• "create_application" tool: create new applications from the plugin wizard (requires login).
• Windows support: compatibility with Windows environments.
• Multilingual responses: responds in Spanish, Portuguese, or English based on the language of the query.

Changed

• Authentication requirement: login (OAuth) is now required only for account-specific actions: "application_list", "get_credentials", "create_test_user", "add_money_test_user", "search_documentation", "save_webhook", "notifications_history", "quality_checklist", "form_homologation", "create_application".

Fixed

• Bug fixes and security improvements.

Fixed

• "capture" parameter: now sent only when the "--capture" flag is passed. It was previously included in all "mpcli payments create" requests, affecting methods that don't support it and overriding "--data" values. Review your calls if you relied on it being sent automatically.
• Financial reports: fixed the endpoints for "mpcli reports releases list" and "settlements list", which returned errors on accounts with existing reports.

Removed

• "listen", "trigger", "events", and "logs" commands: removed as they are not available for general use.

We corrected the documentation for the Update card endpoint in the Saved Cards API to reflect the fields the request body actually accepts when updating a customer's card. The token field was removed, as the API does not accept it on this endpoint. The valid fields for the update are expiration_month, expiration_year, and cardholder (which includes name and identification).