How do I install Dev Latam?

Dev Latam is a local plugin. Install it using npm package: @codespar/mcp-openpay and add the generated configuration snippet to your AI app's MCP config file. Then restart your AI app.

What credentials does Dev Latam need?

Dev Latam requires the following credentials or environment variables: OPENPAY_MERCHANT_ID, OPENPAY_PRIVATE_KEY, OPENPAY_ENV. You can find setup instructions on the server detail page.

What AI apps work with Dev Latam?

Dev Latam uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Dev Latam MCP Server

by User

Developer ToolsUse Caution4.2LocalNew

Free

MCP server for Openpay — BBVA-owned Mexican gateway (cards, SPEI, OXXO, subscriptions, payouts)

About

MCP server for Openpay — BBVA-owned Mexican gateway (cards, SPEI, OXXO, subscriptions, payouts)

Security Report

4.2

Use Caution4.2High Risk

MCP Dev LATAM is a large monorepo catalog of 109 MCP servers for Latin American commerce APIs and agentic payment protocols. The codebase shown (README, package.json, and one server implementation) demonstrates sound architecture with appropriate permission scoping, proper authentication patterns, and no malicious code. Minor code quality observations (broad exception handling, lack of input validation in some paths, basic error handling) are consistent with alpha-stage software and do not constitute security vulnerabilities. The project's distributed architecture, reliance on environment variables for secrets, and category-appropriate permissions align with security best practices for MCP servers. Supply chain analysis found 2 known vulnerabilities in dependencies (1 critical, 0 high severity). Package verification found 1 issue (1 critical, 0 high severity).

4 files analyzed · 7 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

Unverified package source

We couldn't verify that the installable package matches the reviewed source code. Proceed with caution.

What You'll Need

Set these up before or after installing:

Openpay merchant id (forms part of the API URL path)Optional

Environment variable: OPENPAY_MERCHANT_ID

Openpay private API key (used as HTTP Basic auth username with empty password)Required

Environment variable: OPENPAY_PRIVATE_KEY

Environment: 'sandbox' (default) or 'production'. Selects between https://sandbox-api.openpay.mx and https://api.openpay.mx.Optional

Environment variable: OPENPAY_ENV

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-codespar-mcp-openpay": {
      "env": {
        "OPENPAY_ENV": "your-openpay-env-here",
        "OPENPAY_MERCHANT_ID": "your-openpay-merchant-id-here",
        "OPENPAY_PRIVATE_KEY": "your-openpay-private-key-here"
      },
      "args": [
        "-y",
        "mcp-dev-latam"
      ],
      "command": "npx"
    }
  }
}