Cloaked MCP Server

Trustless spending accounts for AI agents on Solana. The cloaked mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 11 defined tools rather than through you.

What it actually does

AI agents need to spend money autonomously. But giving them wallet access is dangerous:

Its toolset

Everything the assistant can do here goes through one of these:

• Zero — knowledge proofs** hide wallet-agent link
• Per — transaction limits
• Pay-per — use APIs
• Real — time spending visibility
• One — click freeze
• Component — Technology
• Blockchain — Solana
• RPC — Helius
• Frontend — Next.js 16, React 19, TypeScript
• Backend — Express.js (Relayer)
• Problem — Cloaked Solution

Configuration

You will need one environment variable: CLOAKED_AGENT_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

The server ships on npm as @cloakedagent/sdk, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Cloaked's toolset — Zero, Per, Pay-per and 8 more — is a fair guide to whether it matches your workflow. It is maintained by cloakedagent; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Cloaked's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Cloaked.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the cloaked mcp server does with a few real requests.