Mcp Stp Spei
Wire Claude Code or Cursor to Mexico’s STP/SPEI rails so your agent can initiate and reason about instant bank transfers without leaving the chat.
Overview
io.github.codespar/mcp-stp-spei is a Build-phase MCP server that connects coding agents to Mexican STP/SPEI instant bank transfers over stdio.
What is this MCP server?
- stdio MCP server via npm package @codespar/mcp-stp-spei (v0.1.0)
- Connects agents to Mexican STP/SPEI instant transfer infrastructure
- Requires STP_API_KEY and STP_COMPANY company identifier
- Suited for LATAM solo builders shipping payouts, reconciliation, or B2B transfer features
- MCP protocol integration—not a standalone payment UI or compliance playbook
- Server schema version 0.1.0
- npm identifier @codespar/mcp-stp-spei
- stdio transport
Community signal: 252 GitHub stars.
What problem does it solve?
Agents cannot safely exercise Mexico’s SPEI transfer APIs from the IDE without a typed MCP bridge and your STP credentials configured once.
Who is it for?
Solo builders shipping Mexican payout, collections, or treasury features who already have or are obtaining STP access and want agent-driven API exploration in Claude Code or Cursor.
Skip if: Teams without STP onboarding, builders outside Mexico who only need card payments via Stripe, or anyone expecting full compliance, fraud, or accounting automation out of the box.
What do I get? / Deliverables
After registration, your agent can invoke STP/SPEI tools during integration work using your API key and company ID instead of hallucinating transfer payloads.
- Registered stdio MCP server exposing STP/SPEI tools to your agent
- Agent-accessible transfer operations against your STP company context
- Faster integration scaffolding for Mexican instant bank transfer flows
Recommended MCP Servers
Journey fit
Payment-rail wiring happens while you are building backends, checkout flows, and payout automation—not during pure ideation or post-launch SEO. STP/SPEI is an external financial API; the canonical shelf is integrations alongside other payment and banking connectors.
How it compares
Bank-rail MCP integration for STP/SPEI, not a general finance agent skill or card-checkout wrapper.
Common Questions / FAQ
Who is io.github.codespar/mcp-stp-spei for?
Indie developers and small teams building Mexico-facing products that must move money over SPEI and want their AI agent to call STP with real credentials.
When should I use io.github.codespar/mcp-stp-spei?
Use it in the build phase while wiring backend transfers, webhooks, or reconciliation—once you have STP_API_KEY and STP_COMPANY from your STP setup.
How do I add io.github.codespar/mcp-stp-spei to my agent?
Install @codespar/mcp-stp-spei from npm, add an MCP stdio server entry in Claude Code or Cursor, and set STP_API_KEY and STP_COMPANY as required environment variables.