Tools
MCP server
The CLI ships a Model Context Protocol server, so agents and automation can operate Cowl through a typed tool interface — read a shielded balance, generate a stealth address, or prepare a transfer, all under your keys.
Preview
The MCP tools below are the target surface. Read-only and local-crypto tools are testnet ready; shielded-pool tools light up as the contracts deploy.
Run it
cowl mcp serve # start the MCP server (stdio transport)
cowl mcp tools # list every tool and its parameters
cowl mcp config # print a config snippet for your MCP clientConnect a client
Add the server to any MCP-compatible client. The command runs locally and signs with your encrypted keystore — nothing leaves your machine except the transactions you approve.
{
"mcpServers": {
"cowl": {
"command": "cowl",
"args": ["mcp", "serve"],
"env": { "COWL_NETWORK": "arbitrum-sepolia" }
}
}
}Tools
| Tool | What it does |
|---|---|
cowl_balance | Read a native or shielded balance |
cowl_address | Generate a one-time stealth address |
cowl_viewkey | Return the public view key for disclosure |
cowl_send | Prepare a transfer for you to approve |
cowl_fees | Return the current fee schedule |
cowl_shield · cowl_trade | Shielded-pool operations (testnet-first) |
You stay in control
The server never holds your keys or auto-signs. Every state-changing tool returns an unsigned action for you to approve. See the security model.