helcim-mcp
Read-only MCP server for the Helcim payment API, letting AI agents safely query customers, invoices, card transactions, subscriptions, and more without risking financial mutations.
README
helcim-mcp
Unofficial community MCP server and developer toolkit for the Helcim API. Secure, typed, agent-friendly, and read-only by default. Not affiliated with, sponsored by, maintained by, or endorsed by Helcim Inc.
helcim-mcp is a production-quality, TypeScript monorepo that makes it safe
and easy for AI agents (and humans) to work with the Helcim payment platform.
It ships three things:
@helcim-mcp/server- an MCP server exposing read-only Helcim tools (customers, invoices, card transactions, card batches, recurring payment plans, subscriptions, connection test).@helcim-mcp/core- a typed, idempotency-aware Helcim API client with normalized errors, rate-limit handling, and secret redaction.@helcim-mcp/webhooks- a standalone Helcim webhook verifier (HMAC-SHA256 signature verification, timestamp validation, replay protection, typed events).
Why would you use this?
- You want an AI agent to answer questions about your Helcim data - "what invoices are outstanding?", "show recent card transactions", "find the customer for this invoice", "which subscriptions need attention?" - without ever risking a financial mutation.
- You want a clean, typed Helcim client that handles the API's quirks
(HTTP 200 ≠ success,
errorsobject shapes, idempotency, rate limits, pagination) so you don't have to. - You want to verify Helcim webhooks securely with constant-time signature comparison and replay protection, without re-inventing the HMAC scheme.
The MCP server is read-only by default. It physically cannot create, update, delete, or move money - there are no such tools. Even a token with full processing privileges cannot trigger a financial mutation through this server.
Quick start
1. Get a Helcim API token
Log in to your Helcim account (or a developer test account), go to All Tools → Integrations → API Access Configurations, and create a configuration. For read-only use, set General: Read, Settings: Read, and Transaction Processing: None.
2. Run the MCP server
# From source
git clone https://github.com/tejasghalsasi/helcim-mcp.git
cd helcim-mcp
pnpm install
pnpm rebuild esbuild # required: pnpm 11 blocks esbuild's postinstall by default
pnpm build
# Set your token (never commit it)
export HELCIM_API_TOKEN="your_token_here"
# Run over stdio
node packages/mcp/dist/index.js
2b. Run with Docker (optional)
docker build -t helcim-mcp .
docker run --rm -e HELCIM_API_TOKEN=your_token_here helcim-mcp
2c. Run via npx (once published)
npx @helcim-mcp/server
3. Connect it to an MCP client
Add this to your MCP client config (e.g. Claude Desktop, Cursor, or any MCP client):
{
"mcpServers": {
"helcim": {
"command": "node",
"args": ["/absolute/path/to/helcim-mcp/packages/mcp/dist/index.js"],
"env": {
"HELCIM_API_TOKEN": "your_token_here"
}
}
}
}
4. Ask your agent
Once connected, your agent can call tools like:
connection_test- confirm the token works.list_invoiceswithstatus: "DUE"- "what invoices are outstanding?"list_card_transactions- "show recent card transactions."get_customer- "find the customer for this invoice."list_subscriptionswithhasFailedPayments: true- "which subscriptions need attention?"
How read-only mode works
- The MCP server exposes only read tools. There are no payment, refund, capture, reversal, withdraw, settle, or delete tools.
- The core client exposes no write methods in v1.
- If a future version adds writes, it will require an explicit
HELCIM_ENABLE_WRITES=trueenvironment variable and a separate high-risk feature flag for financial mutations, with strong documentation and tests. - HTTP 200 is not treated as success. Helcim explicitly warns that a 200
response does not mean the requested action succeeded; the client surfaces
errorsin the body as typed errors.
How credentials are protected
- The API token is read only from the
HELCIM_API_TOKENenvironment variable. Never hardcoded, never committed, never logged. - All log lines and error messages pass through
redact(). Token-like strings, card numbers, and F6L4 values are replaced with<redacted-...>. - The token is never exposed to the model. The MCP server returns only redacted data and typed error codes.
- See SECURITY.md for the full security model.
Architecture
flowchart LR
subgraph Client["MCP Client (LLM)"]
A[Agent]
end
subgraph Server["@helcim-mcp/server"]
M[MCP Server<br/>stdio transport]
T[Read-only tools<br/>13 tools]
end
subgraph Core["@helcim-mcp/core"]
C[HelcimClient]
H[HelcimHttpClient<br/>auth, idempotency,<br/>rate-limit, redaction]
E[Normalized errors]
end
subgraph Webhooks["@helcim-mcp/webhooks"]
W[HelcimWebhookVerifier<br/>HMAC-SHA256, replay protection]
end
subgraph Helcim["Helcim API"]
API[api.helcim.com/v2]
end
A -->|JSON-RPC over stdio| M
M --> T
T --> C
C --> H
H -->|HTTPS + api-token| API
W -.->|verifies signed events| API
The monorepo layout:
helcim-mcp/
├── packages/
│ ├── core/ # Typed Helcim API client (read-safe)
│ ├── mcp/ # MCP server (read-only tools)
│ ├── webhooks/ # Webhook verifier
│ └── fixtures/ # Deterministic mock responses + test vectors
├── examples/ # Copy-paste usage examples
├── docs/ # Architecture, env reference, troubleshooting
└── scripts/ # Smoke test, CI helpers
Example interaction
Agent: "What invoices are currently outstanding?"
list_invoices(status: "DUE")
→ { count: 2, invoices: [
{ invoiceId: 28658838, invoiceNumber: "INV1000", status: "DUE", currency: "CAD", customerId: 2488717 },
{ invoiceId: 28658839, invoiceNumber: "INV1001", status: "DUE", currency: "USD", customerId: 2488718 }
] }
Agent: "Show recent card transactions."
list_card_transactions(limit: 5)
→ { count: 2, transactions: [
{ transactionId: 25557533, status: "APPROVED", type: "purchase", amount: 100.99, currency: "CAD", cardType: "MC", customerCode: "CST1000" },
{ transactionId: 25557534, status: "DECLINED", type: "purchase", amount: 250.00, currency: "CAD", cardType: "VI", customerCode: "CST1001" }
] }
Agent: "Find the customer associated with this invoice."
get_invoice(invoiceId: 28658838) → { customerId: 2488717, ... }
get_customer(customerId: 2488717) → { customerCode: "CST1000", businessName: "Acme Widgets Ltd", ... }
Agent: "Show subscriptions requiring attention."
list_subscriptions(hasFailedPayments: true)
→ { count: 1, subscriptions: [ { id: 42, status: "ACTIVE", hasFailedPayments: true, customerCode: "CST1000", ... } ] }
Agent: "Process a refund for transaction 25557533."
→ Error: Unknown tool: process_refund
The agent cannot move money. There is no such tool.
Webhook verification
import { HelcimWebhookVerifier } from '@helcim-mcp/webhooks';
const verifier = new HelcimWebhookVerifier(process.env.HELCIM_VERIFIER_TOKEN!);
// In your webhook handler (e.g. Next.js route handler):
export async function POST(req: Request) {
const body = await req.text();
const headers = Object.fromEntries(req.headers.entries());
try {
const verified = verifier.verify(headers, body);
// verified.event.type === 'cardTransaction' | 'terminalCancel'
return new Response('ok', { status: 200 });
} catch (err) {
return new Response('invalid signature', { status: 401 });
}
}
See examples/webhook-nextjs.md for a full Next.js example.
Environment variables
| Variable | Required | Description |
|---|---|---|
HELCIM_API_TOKEN |
Yes (for server) | Your Helcim API token. |
HELCIM_BASE_URL |
No | Override base URL (default https://api.helcim.com/v2). |
HELCIM_DEBUG |
No | true to enable redacted request logging. |
HELCIM_TIMEOUT_MS |
No | Request timeout in ms (default 15000). |
HELCIM_VERIFIER_TOKEN |
For webhooks | Your Helcim webhook verifier token. |
See docs/environment.md for the full reference.
Reference
- Supported tools & API matrix - every MCP tool and core client method mapped to its Helcim endpoint.
- Architecture - design decisions and data flow.
- Troubleshooting - common issues and fixes.
- Environment reference - all env vars.
- Release process - how to cut a release.
Development
pnpm install
pnpm rebuild esbuild # pnpm 11 blocks esbuild's postinstall by default
pnpm build # build all packages
pnpm test # run all tests
pnpm typecheck # type-check all packages
pnpm lint # prettier check
pnpm smoke # verify the built server exposes only read-only tools
License
MIT. See LICENSE.
Disclaimer
This is an independent community project. It is not affiliated with, sponsored by, maintained by, or endorsed by Helcim Inc. "Helcim" is a trademark of Helcim Inc. and is used here only to describe API compatibility. This project does not use Helcim logos or branding.
推荐服务器
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 模型以安全和受控的方式获取实时的网络信息。