CardOS MCP Server
Enables AI assistants to issue and manage virtual cards, check balances, pull transactions, file disputes, and start KYC via the CardOS API.
README
<div align="center">
CardOS MCP Server
Issue and manage virtual cards from any AI assistant — over the Model Context Protocol.
</div>
cardos-mcp connects CardOS to Claude, Cursor, Windsurf, VS Code and any MCP client. Point your assistant at it and ask, in plain language, to check a balance, issue a card, pull transactions, file a dispute, or start KYC.
It's a thin, safe client over the public CardOS REST API: no provider internals, no secrets in the repo, money operations are idempotent, card details stay masked, and a cms_sk_test_… key runs in sandbox (no real money).
Quick start
- Get an API key → cardos.dev/partner/developers (a
cms_sk_test_…key = sandbox). - Run it — published to npm:
CARDOS_API_KEY=cms_sk_test_xxx npx -y cardos-mcp
…or straight from source:
git clone https://github.com/CMSCardOS/cardos-mcp && cd cardos-mcp
npm install && npm run build
CARDOS_API_KEY=cms_sk_test_xxx node dist/index.js
Add to your client
Drop this into your client config (env holds your key — see examples/ for Claude Desktop, Cursor, Windsurf and VS Code):
{
"mcpServers": {
"cardos": {
"command": "npx",
"args": ["-y", "cardos-mcp"],
"env": { "CARDOS_API_KEY": "cms_sk_test_xxx" }
}
}
}
| Client | Config file |
|---|---|
| Claude Desktop | claude_desktop_config.json (Settings → Developer → Edit Config) |
| Cursor | ~/.cursor/mcp.json |
| Windsurf | ~/.codeium/windsurf/mcp_config.json |
| VS Code | .vscode/mcp.json (use the examples/vscode.json shape) |
Tools (26)
<details open><summary><b>Catalog & balance</b></summary>
| Tool | Description |
|---|---|
list_products |
Card products: code, currency, limits, KYC requirement |
get_merchant_rates |
Per-merchant pricing |
get_balance |
End-user available balance |
| </details> |
<details open><summary><b>Cards</b></summary>
| Tool | Description |
|---|---|
issue_card 💳 |
Issue a virtual card (idempotent; sandbox with a test key) |
get_card |
Masked details (last4, expiry, status) |
freeze_card / unfreeze_card / close_card |
Lifecycle (idempotent) |
set_card_pin |
Set a 4-digit PIN (not stored by CardOS) |
set_card_controls |
Spend limits + blocked MCC/countries (auto-freeze on breach) |
reveal_card |
One-time hosted PAN/CVV link (PCI on CardOS) |
create_card_session |
Hosted manage + transactions screens for the end user |
list_card_transactions |
Transactions (amount, FX, commission, merchant, MCC, decline) |
| </details> |
<details><summary><b>Deposits</b></summary>
| Tool | Description |
|---|---|
create_deposit 💳 |
Crypto deposit invoice (idempotent) |
confirm_deposit_sandbox |
[sandbox] confirm a pending deposit |
simulate_transaction_sandbox |
[sandbox] inject a test transaction |
| </details> |
<details><summary><b>Statements, analytics, disputes, KYC, webhooks</b></summary>
| Tool | Description |
|---|---|
get_statement |
Statement (spent/received/fees + lines) |
get_spending_analytics |
Spending by category |
file_dispute / list_disputes / get_dispute / update_dispute |
Disputes |
start_kyc / get_kyc_status |
Hosted KYC flow |
register_webhook / list_webhooks |
Signed outbound events |
| </details> |
Resources & prompts
- Resources —
cardos://docs(auth/idempotency/webhooks orientation) andcardos://openapi(the live OpenAPI 3 spec). Clients can read these for context. - Prompts —
issue_card_for_user(guided end-to-end issuance) andintegrate_cardos(integration walkthrough).
Example prompts
- "What card products are available?" →
list_products - "Issue a sandbox card for user 123456, then show its details." →
issue_card→get_card - "Top up user 123456 with $100 and confirm it." →
create_deposit→confirm_deposit_sandbox - "Freeze card
<id>and set a $50 daily limit." →freeze_card→set_card_controls
Safety
- Sandbox-first — a
cms_sk_test_…key never moves real money. - No secrets in the repo — the key lives in your client config / env.
- Idempotent money ops —
issue_card/create_depositwon't double-apply on retry. - Masked card data — full PAN/CVV only via a one-time hosted link, never through this server or the model.
- See SECURITY.md.
Configuration
| Env var | Default | Description |
|---|---|---|
CARDOS_API_KEY |
— | Your CardOS API key (required). |
CARDOS_BASE_URL |
https://cardos.dev/api/v1 |
Override the API base. |
Develop
npm install
npm run build # tsc → dist/
npm test # vitest (network mocked)
npm run typecheck
See CONTRIBUTING.md.
Links
- CardOS — https://cardos.dev
- Docs — https://cardos.dev/docs · Reference — https://cardos.dev/reference · OpenAPI — https://cardos.dev/openapi-v1.yaml
- FAQ — FAQ.md · Changelog — CHANGELOG.md
- Model Context Protocol — https://modelcontextprotocol.io
License
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。