@paychainly/mcp
v1.0.3
Published
MCP server for the Paychainly payment platform — control payments, customers, invoices and withdrawals from Claude Desktop or any AI agent
Maintainers
Readme
Paychainly MCP Server
MCP server for the Paychainly payment platform. Exposes 38 tools, 10 documentation resources, and 9 workflow prompts.
| Category | Count |
|----------|-------|
| Tools | 38 (customers, addresses, payment links, transactions, invoices, webhooks, withdrawals, sandbox, system) |
| Resources | 10 (paychainly://docs/* — readable by Claude before acting) |
| Prompts | 9 (4 integration pattern guides + 5 utility workflows) |
stdio (Claude Desktop) — via npm
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"paychainly": {
"command": "npx",
"args": ["-y", "@paychainly/mcp"],
"env": {
"PAYCHAINLY_API_KEY": "your_api_key_here"
}
}
}
}Restart Claude Desktop after saving. npx downloads and caches the package automatically — no global install needed.
Local development (stdio)
{
"mcpServers": {
"paychainly": {
"command": "node",
"args": ["/absolute/path/to/mcp.paychainly.com/dist/index.js"],
"env": {
"PAYCHAINLY_API_KEY": "your_api_key_here",
"PAYCHAINLY_BASE_URL": "https://api.paychainly.com"
}
}
}
}HTTP/SSE (remote)
PORT=3003 PAYCHAINLY_BASE_URL=https://api.paychainly.com node dist/http.jsConnect Claude to: http://your-server:3003/sse
Header: Authorization: Bearer your_api_key
Deploy with Docker
chmod +x docker-run.sh
PAYCHAINLY_BASE_URL=https://api.paychainly.com PORT=3003 ./docker-run.shIntegration patterns
Not sure which workflow prompt to use? Pick based on your use case:
| # | Prompt | Use case |
|---|--------|----------|
| 1 | setup_wallet | User wallet / permanent deposit address / balance top-up |
| 2 | wallet_topup_with_link | Fixed-amount top-up with hosted checkout page |
| 3 | order_checkout | E-commerce order / invoice / subscription (logged-in user) |
| 4 | guest_checkout | One-off payment, no account needed, fully anonymous |
For patterns 2, 3, and 4 — the response always includes all three payment options from the same single call:
payUrl→ redirect user to hosted checkout (QR, countdown, MetaMask connect)address→ show in your own custom UIaddress→ QR-encode it yourself
Workflow prompts
| Prompt | Description |
|--------|-------------|
| setup_wallet | Pattern 1 — permanent deposit wallet for a customer (mode: reuse) |
| wallet_topup_with_link | Pattern 2 — fixed-amount payment link on an existing wallet |
| order_checkout | Pattern 3 — per-order checkout for a logged-in user |
| guest_checkout | Pattern 4 — per-order checkout with no customer required |
| lookup_customer_history | Look up a customer and show all their transactions |
| verify_webhook_signature | Code examples for verifying webhook HMAC signatures |
| sandbox_test_payment | End-to-end test flow using sandbox mode (no real funds) |
| initiate_withdrawal | Safely withdraw USDT to an external wallet |
| check_account_status | Full account health overview |
