Skip to main content
SS

STP SPEI

@codespar/mcp-stp-spei · v0.2.0-alpha.3

🇲🇽 MexicoBankingAuth · API Keybeta18 tools2 env varsprerelease

Mexican instant bank transfers via SPEI. Your agent sends and receives MXN in real time through the national payment system.

Get started · freeView docs

MIT · runs locally or through the CodeSpar runtime

Limitations

  • v0.2.0-alpha.3 is a prerelease, with 18 tools, and the command on this page installs it. The latest stable release is 0.1.0, with 8 tools.
  • The npm package ships no server.json manifest.
Package
@codespar/mcp-stp-spei
Version
0.2.0-alpha.3 · prerelease
npm dist-tag
latest
Category
Banking
Auth
API Key
Country
🇲🇽 Mexico
License
MIT
Transport
stdio · streamable-http

Quickstart

Install, set the credentials, make the first call.

Pick your client. The server runs locally over stdio, or through the hosted runtime.

Add the server to your clientOne config entry. No build step, no SDK required.
Set the environment variables2 variables read by this server's code, listed below.
Restart and make the first callThe agent can call any of the 18 tools. Try create_transfer first.
terminal
# Claude Code claude mcp add stp-spei -e STP_API_KEY=… -e STP_COMPANY=… -- npx -y @codespar/mcp-stp-spei@0.2.0-alpha.3 # then: /mcp to confirm the server is connected
Environment variables2 variables
STP_API_KEYAPI key for STPrequiredsecret
STP_COMPANYCompany identifier for STPrequired

Names read from the package code (@codespar/mcp-stp-spei@0.2.0-alpha.3). Descriptions and flags come from its manifest. Self-hosted, you hold the credentials. On the CodeSpar runtime the credential you connect is stored encrypted (AES-256-GCM, key derived per organization), and the runtime adds it to the provider call itself; the agent never receives it.

First call democreate_transfer

"Create a SPEI transfer"

tools/callcreate_transferresult returned

Tools

What your agent can call.

18 tools, as the package's tools/list returns them.

create_transfer

Create a SPEI transfer

get_transfer

Get transfer details by ID

list_transfers

List transfers with filters

cancel_transfer

Cancel a pending SPEI orden by clave_rastreo (only works while orden is pending)

get_balance

Get account balance

list_account_balances

List balances for all company accounts

validate_account

Validate a CLABE account number against the receiving bank (online check)

validate_clabe

Validate CLABE structure and checksum locally (no API call). Returns bank code, plaza, account, and check digit

list_banks

List participating SPEI banks

lookup_bank_by_code

Look up a participating bank by its ABM/SPEI code (first 3 digits of CLABE)

get_cep

Get CEP (Comprobante Electronico de Pago) for transfer validation

register_beneficiary

Register a beneficiary account

Names and descriptions come from the package's tools/list (@codespar/mcp-stp-spei@0.2.0-alpha.3). A kind (read, write, delete) is shown only when the package annotates its tools or each tool was verified one by one; neither exists for this server yet.

Compatibility

MCP is a protocol. Any client that speaks it can mount this server.

Through the CodeSpar runtime, codespar_discover finds this server's tools, and a tools/call runs with the credential connected in your project, a test key included.

hostedhttps://connect.codespar.dev/mcp15 meta-tools

Protocol

Any MCP client

stdio · streamable-http

Questions

Before you install.

How do I install the STP SPEI MCP server?

Run npx -y @codespar/mcp-stp-spei@0.2.0-alpha.3 and add the config block above to your MCP client: Claude Code, Cursor, Claude Desktop, VS Code, or any MCP-compatible client. No build step, no SDK required. Prefer hosted? Add the CodeSpar endpoint with a test key and connect STP SPEI in your project; codespar_discover finds its tools.

What can my agent do with STP SPEI?

STP SPEI exposes 18 tools for banking. Your agent calls them directly; the full list is above.

How does STP SPEI authenticate, and how are credentials stored?

STP SPEI uses API Key. Self-hosted, you hold the credentials: the server reads them from its environment variables. On the CodeSpar runtime the credential you connect is stored encrypted for your organization, and the runtime adds it to each provider call, so the agent never handles it.

How does STP SPEI handle upstream API changes?

Every server is versioned independently on npm. The command on this page pins 0.2.0-alpha.3, the version whose tools are listed here; your agent keeps running it until you change the version.

Is STP SPEI open source? How do I report a bug?

Yes. STP SPEI is MIT-licensed and published on npm as @codespar/mcp-stp-spei, source on GitHub (link in the Details panel). Report issues on the package repository; security issues go to security@codespar.dev, and we respond within 24 hours.

Start in seconds.

On the CodeSpar runtime, the credential you connect stays encrypted for your organization and the runtime adds it to each call. You just call the tool.

Start in seconds demo
Create an account and copy a test key.
Add the hosted endpoint to your client with the config above.
Connect STP SPEI in your project and ask your agent for the first call.
STP SPEI — MCP server · 18 tools | CodeSpar