@klappay/mcp
OfficialClick 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., "@@klappay/mcplook up charge ch_9f2a and show its timeline"
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.
@klappay/mcp
A local Model Context Protocol server for
the Klap Core API. Your AI assistant (Claude Code, Claude Desktop, Cursor,
or any MCP client) runs it on your own machine over stdio with npx.
Nothing is hosted by Klappay: the server talks straight to the Klap API with
the key klap login already stored in
~/.klap/config.json.
What the assistant can do with it:
Read: look up a charge and its timeline, list webhooks and their deliveries, list accepted
(token, network)pairs, run metrics queries.Test mode: create charges, re-check them on-chain, retry webhook deliveries and push a sandbox charge through its payment states.
Live mode: read-only by default. Writes are only registered when you opt in explicitly.
Moving money (escrow release/refund) and managing webhook endpoints or payout recipients are never exposed. See Security.
Install
Requires Node.js 24+. Log in once with the CLI so the key lives in
~/.klap/config.json instead of your MCP client's config file:
npx @klappay/cli login --api-key - --base-url https://api.klap.examplePaste the key on stdin and press Ctrl-D. --api-key - keeps the key out of
your shell history; KLAP_API_KEY=... npx @klappay/cli login --base-url ...
works too.
Then add one server per environment. Keeping test and live as separate servers means the assistant always knows which one it is talking to, and you can turn live off without touching test.
Claude Code
claude mcp add klap-test -- npx -y @klappay/mcp@1.0.0
claude mcp add klap-live -e KLAP_ENV=live -- npx -y @klappay/mcp@1.0.0Claude Desktop (claude_desktop_config.json) and Cursor (~/.cursor/mcp.json)
Both use the same shape:
{
"mcpServers": {
"klap-test": {
"command": "npx",
"args": ["-y", "@klappay/mcp@1.0.0"]
},
"klap-live": {
"command": "npx",
"args": ["-y", "@klappay/mcp@1.0.0"],
"env": { "KLAP_ENV": "live" }
}
}
}Pin the exact version as above rather than @latest: an MCP server runs
with your API key, so upgrade it on purpose. On startup it prints one line
to stderr, e.g. klap-mcp: test → api.example.com, and never the key.
Related MCP server: cryptbrew-mcp
Environment variables
Variable | Default | Meaning |
|
|
|
| unset | Use this key instead of |
| stored | Required with |
| unset | Set to exactly |
An empty value counts as unset. Full rules: Configuration.
Tools
Tool | Test | Live | Live + writes |
| yes | yes | yes |
| yes | yes | yes |
| yes | yes | yes |
| yes | yes | yes |
| yes | yes | yes |
| yes | yes | yes |
| yes | yes | yes |
| yes | no | yes |
| yes | no | yes |
| yes | no | yes |
| yes | no | no |
Every result is JSON and carries environment. Inputs and outputs are
described in Tools.
Security notes
Live is read-only unless
KLAP_MCP_ALLOW_LIVE_WRITES=1.A key stored by
klap loginis only ever sent to the base URL it was stored with. PointingKLAP_BASE_URLsomewhere else refuses to start.Plain
http://is only accepted forlocalhost,127.0.0.1and[::1].API responses are filtered through the published
@klappay/typesschemas before the assistant sees them; unknown fields are dropped and a charge'smetadatais left out unless asked for.Not available at all: escrow
release/refund, webhook create/delete/rotate-secret, recipient changes, live event streams, QR codes and swap quotes.
More in Security.
Documentation
Full docs live in docs/ and as a browsable site at
mcp.klappay.com, which also publishes
llms.txt and
llms-full.txt.
Topic | |
Log in, add the server, first prompts | |
How the environment and key are chosen, every refusal | |
Every tool's input, output and availability | |
Threat model, what's excluded and why |
License
This server cannot be deployed
Related MCP Connectors
Run AI customer support from your terminal: conversations, knowledge base, and chat widget.
Deploy, monitor, and manage your OpenClaw AI assistants via natural language.
- QuallaaOAuthcom.quallaa
Talk to your public-facing AI from any MCP client — Claude, ChatGPT, Cursor, Cline, Windsurf.
Real-time chat hub for AI agents — Claude Code, Cursor, Cline, Codex over MCP or REST.
Related MCP Servers
- FlicenseBqualityBmaintenanceEnables an AI assistant to read and manage a local project-management database over stdio: listing and creating projects, tasks, expenses, chats and people, and pulling money, margin, deadline and overdue summaries. It runs on the same service layer and SQLite file as the bundled web UI, so figures shown to the assistant and to the human always agree.14-

cryptbrew-mcpofficial
AlicenseAqualityBmaintenanceEnables AI agents to answer Cryptbrew product questions and check live API health without merchant authentication. Exposes tools for pricing, FAQs, invoice flow, and health probes over stdio or streamable HTTP.8MIT- FlicenseNot gradedqualityBmaintenanceEnables MCP clients such as Claude Desktop or Claude Code to drive the local daemon through stdio, listing agents and sessions, running agents, and reporting costs.-

@shieldlabs-ai/mcpofficial
AlicenseAqualityBmaintenanceEnables AI assistants to read identification verdicts, search history, summarize entities, explain risk scores, and verify webhook signatures through read-only tools over stdio or streamable HTTP.6216 npmMIT