About stablevoy-mcp
stablevoy-mcp connects AI assistants to Stablevoy, a non-custodial USDT and USDC payment gateway. It supports invoice creation and management across selected stores, while its API keys cannot move funds or change store settings.
Key features
- 01Create and cancel invoices
- 02Check invoice status and payments
- 03List and inspect stores
- 04Filter invoice history
- 05Optional read-only mode
Use cases
- 01Send a payment link to a client
- 02Check whether an invoice was paid
- 03Review recent invoices across stores
MCP support
The MCP server exposes Stablevoy store and invoice tools to MCP clients such as Claude Desktop, Claude Code, and Cursor. Store API keys authorize invoice actions and reads, but cannot move funds or change payout settings.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y stablevoy-mcpSTABLEVOY_API_KEYSecretA store API key (sk_live_...) for one store. Leave unset to use the keys of npx stablevoy-mcp login; with neither, the store tools answer not_signed_in and the documentation works.STABLEVOY_MCP_READ_ONLYtrue leaves create_invoice and cancel_invoice out: read tools only.Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEstablevoy-mcp
An MCP server for Stablevoy, the non-custodial USDT and USDC payment gateway. Ask your AI assistant to bill a client, check whether an invoice is paid or sum up the week, across all your stores:
- "Bill Acme 250 dollars for the October work" gives a payment link.
- "Has Acme paid?" gives the status and the transactions.
- "What came in this week in the Main store?" gives the list.
It works with Claude Desktop, Claude Code, Cursor and any client that speaks the Model Context Protocol. It runs on your computer and talks only to the Stablevoy API.
What it can and cannot do
The server holds store API keys only. With them it can create invoices to receive money, cancel unpaid ones and read your stores and invoices. It cannot move funds, change your payout address, your webhooks, your limits, your keys or your stores: those need your wallet signature in the Stablevoy dashboard. Stablevoy never holds your money, so there is nothing to withdraw.
So even an assistant tricked by a malicious web page or document can only create invoices that pay you, cancel an unpaid one (the buyer is told not to pay it and your shop gets the invoice.cancelled webhook), and read your invoices. Reading is the real exposure: invoice amounts and your references. Keep that in mind before you connect the server to an assistant that also reads untrusted content, or run it read-only (below).
Connect
Requires Node.js 22.12 or later.
npx stablevoy-mcp login
This opens the Stablevoy dashboard in your browser. Sign in with your wallet, tick the stores the assistant may use and approve. The browser hands a one-time code back to the command on this computer, which exchanges it for one API key per store and keeps them in your config folder (~/.config/stablevoy-mcp on Linux, ~/Library/Application Support/stablevoy-mcp on macOS, %APPDATA%\stablevoy-mcp on Windows), readable by you only. The keys are named "MCP (your computer)" on the store pages of the dashboard, where you can revoke any of them.
Then add the server to your client.
Claude Desktop (claude_desktop_config.json), Cursor (.cursor/mcp.json) and most clients:
{
"mcpServers": {
"stablevoy": { "command": "npx", "args": ["-y", "stablevoy-mcp"] }
}
}
Claude Code:
claude mcp add stablevoy -- npx -y stablevoy-mcp
One store without a login
Create a key on the store page of the dashboard and pass it instead:
{
"mcpServers": {
"stablevoy": { "command": "npx", "args": ["-y", "stablevoy-mcp"], "env": { "STABLEVOY_API_KEY": "sk_live_..." } }
}
}
Read-only
Add "STABLEVOY_MCP_READ_ONLY": "true" to env: create_invoice and cancel_invoice are then not offered at all.
Change the stores
npx stablevoy-mcp loginagain: the stores this computer has are ticked; untick the ones to drop. Their keys are revoked, the new selection replaces the old one.npx stablevoy-mcp storeslists the stores of this computer;npx stablevoy-mcp stores remove "Main"drops one and revokes its key.npx stablevoy-mcp logoutrevokes every key of this computer and deletes the file.
Adding a store always goes through the browser, since it needs your wallet. The assistant cannot change the set. Several accounts or sets: --profile work on these commands, and "STABLEVOY_MCP_PROFILE": "work" in the client config.
Tools
| Tool | What it does |
|---|---|
| list_stores | The connected stores, whether each can take payments and its EVM payout status. |
| get_store | A store's settings: networks, payout addresses, the EVM payout status, invoice limits, fee, website, return and webhook URLs. Read only. |
| create_invoice | An invoice for an amount in dollars ("19.99"), with an optional reference, return URL and payment window (expiresInMinutes, 15 to 10080; the store default when left out); returns the payment link, which you send to the buyer yourself. The same amount and reference return the same invoice instead of a second one. |
| cancel_invoice | Cancels an invoice no payment has been seen for, so the buyer is told not to pay it. Money that still arrives later marks it paid_late. |
| get_invoice | An invoice by id, with the payments received. |
| list_invoices | Invoices newest first, filtered by status, source, search and the days they were created. |
With several stores, tools take a store argument (the id or the exact name from list_stores); the server asks for it rather than guessing.
Configuration
| Variable | Meaning |
|---|---|
| STABLEVOY_API_KEY | One store key; when set, the login keys are not used. |
| STABLEVOY_MCP_PROFILE | Which login profile to use, default by default. |
| STABLEVOY_MCP_READ_ONLY | true leaves create_invoice and cancel_invoice out. |
| STABLEVOY_API_URL | The API, https://api.stablevoy.com by default. |
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.