Cosmos Pay MCP Server
OfficialCosmos Pay MCP server exposes Cosmos Pay Payments API tools so an AI agent can create non-custodial stablecoin payment links and inspect/manage payments on Stellar, Solana, and Monad using an API key.
Create payment links, QR codes, and hosted checkout pages with destination, chain, amount, asset, memo/message, and checkout theme.
Read one payment by id, get its status history, and list/filter payments by status, chain, or creation date.
Validate a transaction hash or Solana signature against a payment and settle it if it matches; this is idempotent.
Delete an unpaid payment so its link can no longer be paid; paid payments cannot be deleted.
Get organization summary metrics, settled/pending balances per asset, and the Stellar asset catalog.
Supports read-only mode and API-key scopes; the API key determines testnet vs. public network. The server does not sign or move funds.
Enables creating and managing Cosmos Pay stablecoin payment requests on Solana, including Solana Pay links, QR codes, hosted checkout, payment status/history, balances, and validating transaction hashes.
Enables creating and managing Cosmos Pay stablecoin payment requests on Stellar, including SEP-7 payment links, QR codes, hosted checkout, payment status/history, balances, Stellar asset listing, and validating transaction hashes.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Cosmos Pay MCP Server Create a payment link for 25 USDC on Stellar to my store's address"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Cosmos Pay MCP server
An MCP server for the Cosmos Pay Payments API. It lets an AI agent (Claude Code, Claude Desktop, Cursor, VS Code, Windsurf and any other MCP client) create stablecoin payment links and check payments on Stellar, Solana and Monad with your API key.
Cosmos Pay is non-custodial: a payment link is a request the customer pays from their own wallet, and the money settles on-chain straight to your address. Nothing in this server signs or moves funds.
Cosmos Pay (cosmospay.lat) is a different project from the Cosmos Network (ATOM).
Tools
Tool | What it does | Kind |
| Create a payment request: a link (SEP-7 on Stellar, Solana Pay on Solana, EIP-681 on Monad), its QR code and a hosted checkout page | creates, moves no money |
| One payment: status, amount, asset, chain, link, checkout URL and, once paid, the transaction hash | read |
| A payment's status changes | read |
| Payments, newest first, filtered by status, chain or date, paged | read |
| Check a transaction hash against a payment and settle it if it pays it | idempotent |
| Delete an unpaid payment so its link can no longer be paid | destructive |
| Totals, settled volume, webhook health and a 30-day series | read |
| Settled and pending amounts per asset | read |
| Stellar asset codes and issuers to charge in (USDC, EURC...) | read |
Each tool carries MCP annotations (readOnlyHint, destructiveHint), so your client can ask before anything that writes.
Related MCP server: Yolfi MCP Server
Setup
Create a secret API key in the Cosmos Pay dashboard (API keys). Start with a
dv_key: it works on test networks with no real money. Aprod_key works on mainnet.Add the server to your MCP client with the key in its environment.
Claude Code
claude mcp add cosmos-pay --env COSMOS_PAY_API_KEY=dv_your_key -- npx -y @cosmosapp/pay_mcpClaude Desktop, Cursor, Windsurf (claude_desktop_config.json, .cursor/mcp.json, ~/.codeium/windsurf/mcp_config.json)
{
"mcpServers": {
"cosmos-pay": {
"command": "npx",
"args": ["-y", "@cosmosapp/pay_mcp"],
"env": { "COSMOS_PAY_API_KEY": "dv_your_key" }
}
}
}VS Code (.vscode/mcp.json)
{
"inputs": [{ "type": "promptString", "id": "cosmos-pay-key", "description": "Cosmos Pay API key", "password": true }],
"servers": {
"cosmos-pay": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@cosmosapp/pay_mcp"],
"env": { "COSMOS_PAY_API_KEY": "${input:cosmos-pay-key}" }
}
}
}Then ask your agent things like "Create a payment link for 25 USDC on Stellar to my store's address" or "Which payments from this week are still pending?"
Configuration
Variable | |
| Required. A secret key from the dashboard: |
|
|
| Another Payments API root (default |
| Another hosted checkout origin (default |
Security
The API key is read from the environment only. It is never a tool argument, never logged and never part of a result.
The key decides the network: every payment the tools return names it (
testnetorpublic), and the server tells the agent which one it is on.A key's scopes limit what the server can do: create a key with only the permissions you want the agent to have, or run it read-only.
Payments settle to the address in the request. Check the
destinationan agent proposes before you share a link.
Links
Docs: https://dev.cosmospay.lat/docs/ (index for LLMs: https://dev.cosmospay.lat/docs/llms.txt)
Payments API reference: https://dev.cosmospay.lat/docs/api/
JavaScript/TypeScript SDK:
@cosmosapp/pay_sdkAgent skill for coding agents: CosmosPay-Skill
Development
npm ci
npm run typecheck && npm test && npm run build
COSMOS_PAY_API_KEY=dv_your_key npm run inspect # MCP Inspector against the built serverApache-2.0.
Available Tools
9 toolscreate_payment_linkCreate a payment linkA
Create a payment request that a customer pays from their own wallet: a payment link (SEP-7 on Stellar, Solana Pay on Solana, EIP-681 on Monad), its QR code and a hosted checkout page. It moves no money: the payment settles on-chain straight to destination once the customer pays. The network is the API key’s: this server is on test networks (dv_ key: no real funds). Omit amount to let the payer choose it (not on Monad, which needs one). Omit asset_code to charge in the chain’s coin (XLM, SOL, MON). Send the customer checkoutUrl (or paymentUri for a wallet), then use get_payment to see when it is paid.
Inputs: destination (required), memo, chain, amount, +5 more.
delete_paymentDelete a paymentADestructive
Delete a payment that is not paid, so its link can no longer be paid. A paid (SUCCEEDED) payment cannot be deleted. This cannot be undone: confirm with the user first.
Inputs: id (required).
get_balancesGet settled balancesARead-only
Settled and pending amounts per asset for the API key’s organization (what its payments brought in, not a wallet balance).
Inputs: no named parameters.
get_paymentGet a paymentARead-only
Read one payment: its status (PENDING, SUBMITTED, SUCCEEDED, FAILED, CANCELLED, EXPIRED), amount, asset, chain, destination, payment link, hosted checkout URL and, once paid, the transaction hash.
Inputs: id (required).
get_payment_historyGet a payment historyARead-only
The status changes of one payment, oldest first, with when each happened.
Inputs: id (required).
get_summaryGet the account summaryBRead-only
Overview of the API key’s organization: payment totals, settled volume, webhook health and a 30-day series.
Inputs: no named parameters.
list_paymentsList paymentsARead-only
List the payments of the API key’s organization, newest first, optionally filtered by status, chain or creation date. Paged: total says how many match.
Inputs: skip, take, chain, status, +1 more.
list_stellar_assetsList Stellar assetsARead-only
The Stellar asset catalog: codes and issuers to charge in (for example USDC and EURC by Circle). Use an entry’s code and issuer as create_payment_link’s asset_code and asset_issuer.
Inputs: network, verified_only.
validate_paymentValidate a paymentAIdempotent
Check a transaction against a payment and settle it if it pays it. Use it when the payer sent the payment but its status has not changed: pass the transaction hash (or Solana signature) the payer has.
Inputs: id (required), tx_hash (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
Each tool targets a distinct action (retrieve, list, create, validate, delete) on payments or org data. Minor overlap between get_summary and get_balances (both org-level overviews), and get_payment vs get_payment_history could occasionally be confused, but descriptions clarify the boundary.
All tools follow a consistent snake_case verb_noun pattern: get_payment, list_payments, create_payment_link, validate_payment, delete_payment, get_summary, etc. No mixed conventions or vague verbs.
Nine tools is well-scoped for a payments API, covering the full lifecycle without redundancy. Each tool earns its place with a clear, non-trivial function.
Create/read/list/validate/delete coverage is solid, plus summary, balances, and asset catalog. However, webhook management (referenced in get_summary's webhook health) and refunds lack dedicated tools, leaving minor gaps.
Maintenance
Related MCP Connectors
Crypto pay links and API for people and AI agents. BTC, Lightning, USDC, USDT, EURC, SOL, ETH.
Stripe payments for AI agents. Create links, verify, manage customers.
USDC wallets, payment links and x402 payments on Solana for AI agents.
Keyless non-custodial crypto payments for AI agents: payment links and tip jars, no API key.
Related MCP Servers
- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents to add stablecoin crypto checkout, payment links, payment status checks, webhook verification, and webhook-based access logic to applications through hosted payment APIs.-
- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents to add stablecoin checkout, payment links, payment status checks, webhook verification, and webhook-based entitlement logic to applications. It also provides tools for workspace registration, settlement and webhook configuration, paylink creation, and crypto payment status checks.-
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to add stablecoin checkout, payment links, payment status checks, webhook verification, and webhook-based access logic to applications. It provides tools for registering workspaces, configuring settlement wallets and webhooks, creating paylinks, and verifying crypto payment status.MIT

Yolfi MCP Serverofficial
AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to add stablecoin checkout, payment links, payment status checks, webhook verification, and webhook-based access logic to applications through an API-first payment workflow.MIT