Getting Started
The Hinkal MCP server lets any AI agent add privacy to on-chain transfers and settlement flows across Hinkal's supported chains - through the Model Context Protocol, the open standard for connecting AI assistants to tools.
It exposes Hinkal's private deposits, withdrawals and transfers as MCP tools, so an assistant like Claude can move funds between a user's public wallet and their private (shielded) balance from plain-language requests.
The server abstracts all privacy mechanics. The agent calls simple tools - Hinkal handles the proofs, relaying, and settlement.
@hinkal/mcp - the MCP server, runnable from any MCP client over stdio.
Model Context Protocol - the client/host standard the server implements.
What the Server Enables
With a single connection, an agent can support:
Confidential deposits and payouts Move funds into and out of a shielded balance without publicly revealing balances or amounts.
Private transfers between Hinkal users Send value with no on-chain link between sender and recipient.
Public-to-public private sends Pay one or many public addresses with no on-chain link back to the sender.
Design
No smart contract changes required
Works with any MCP client - Claude Desktop, Claude Code, or your own host
Every transaction is signed and broadcast server-side by Hinkal — nothing for the agent or user to sign
Withdrawals, transfers, and sends run server-side through a Hinkal relayer;
Compatibility
Node.js
✅
v18+
Transport
✅
stdio
MCP clients
✅
Claude Desktop, Claude Code, any MCP host
Chains
✅
Hinkal's supported chains - call list_chains for the live set
Last updated