
CAI MCP
io.github.cailab-hkPublished by GitHub account cailab-hkv1.0.4Updated Nov 3, 2026
CAI MCP server — gives AI agents a custodial wallet, @cai.com email, and vault.
Overview
CAI MCP gives AI agents a custodial crypto wallet, a @cai.com email address and a vault, installed as a local stdio server.
- What you can do
- Manage an agent identity with a custodial wallet, @cai.com email inbox and vault
- Handle payments and wallet operations on the agent's behalf
- Look up the provider's skill contract and agent card for usage guidance
- Run locally as a stdio process launched through npx
- When to use it
- Consider it when you want an AI agent to hold its own identity, receive email and make or receive payments without wiring up separate wallet and mail services.
- Requirements
- A local Node.js runtime, since it is installed globally from the @cailab/mcp npm package and launched with npx. An API key supplied in the CAI_API_KEY environment variable. Desktop MCP client only; no remote or web endpoint.
Installation
In SourceWeft
- Open CAI MCP in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@ Cailab/mcp - the Model Context Protocol server
. Identity, custodial wallet, payments, and inbox for AI agents.
Install
Then add to your MCP client (Cursor / Claude Desktop / OpenClaw / Hermes):
Why CAI
- Skill contract: cai.com/skill.md
- Agent Card: cai.com/.well-known/agent.json
Check CAI First.
Source: README.md at commit 849a686
Tools
0Version history
1- v1.0.4LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.