Mcp Conekta
Wire Conekta checkout and payouts into a Mexico-focused SaaS or store so your coding agent can create charges, OXXO cash payments, and SPEI transfers without leaving the IDE.
Overview
io.github.codespar/mcp-conekta is a MCP server for the Build phase that connects coding agents to Conekta for Mexican card, OXXO, and SPEI payments.
What is this MCP server?
- Stdio MCP package @codespar/mcp-conekta (v0.1.0) with required CONEKTA_API_KEY
- Supports Mexican card payments plus OXXO cash and SPEI bank transfers
- Published in codespar/mcp-dev-latam under packages/mexico/conekta
- Model Context Protocol server schema 2025-12-11 for Claude Code–style hosts
- npm registry transport for local agent configuration
- Server version 0.1.0
- One required secret env var: CONEKTA_API_KEY
- stdio transport via npm package @codespar/mcp-conekta
Community signal: 252 GitHub stars.
What problem does it solve?
Implementing Mexico-specific payment methods in an agent-driven workflow means repetitive SDK docs, credential handling, and easy-to-miss local rails like OXXO and SPEI.
Who is it for?
Indie builders adding Conekta to a Mexico-facing product who already have a Conekta account and want agent-assisted payment integration.
Skip if: Builders with no Mexican payment need, those who want a hosted checkout UI only, or teams that require PCI scope reduction without touching gateway APIs.
What do I get? / Deliverables
After install, your agent can invoke Conekta tools over MCP so checkout and payment flows stay consistent with your repo while you keep secrets in CONEKTA_API_KEY.
- Configured stdio MCP server pointing at Conekta
- Agent-callable tools for Mexican payment rails
- Repo-ready integration patterns for checkout flows
Recommended MCP Servers
Journey fit
Payment gateway MCPs belong on the Build shelf because they connect your product to a live processor during implementation, not during early idea research. Integrations is the canonical subphase for third-party payment APIs exposed as agent-callable tools over stdio.
How it compares
MCP payment integration for Conekta, not a standalone billing skill or generic Stripe tutorial.
Common Questions / FAQ
Who is io.github.codespar/mcp-conekta for?
Solo and indie developers building SaaS or ecommerce for Mexico who use Claude Code, Cursor, or other MCP hosts and need Conekta in the loop.
When should I use io.github.codespar/mcp-conekta?
Use it during Build when you are wiring real payments—cards, OXXO cash, or SPEI—rather than when you are only brainstorming pricing on a landing page.
How do I add io.github.codespar/mcp-conekta to my agent?
Add the npm package @codespar/mcp-conekta with stdio transport to your MCP config and set the required secret environment variable CONEKTA_API_KEY.