What you will learn
- How the MCP adapter exposes ISCL crypto operations to AI assistants
- How to configure Claude Desktop and Cursor for Clavion
- How to invoke tools like transfers, swaps, and balance checks
- Full parameter reference for all six MCP tools
Overview
The MCP (Model Context Protocol) adapter exposes ISCL’s crypto operations as MCP tools that AI assistants can invoke. When Claude Desktop or Cursor calls a tool likeclavion_transfer, the adapter constructs a TxIntent, sends it through the full ISCL pipeline (policy, preflight, approval, signing, broadcast), and returns the result.
Available tools
Prerequisites
Before setting up the MCP adapter, ensure you have:- ISCL Core running on
localhost:3100 - A wallet address imported into the ISCL keystore
- RPC configured for your target chain(s)
- Node.js 20+
- An MCP client (Claude Desktop, Cursor, or compatible IDE)
Setup
Tool parameters
Full parameter reference for each MCP tool.clavion_transfer
clavion_transfer_native
clavion_swap
clavion_balance
clavion_tx_status
clavion_approve
Approval modes
How the user approves transactions depends on the ISCL Core approval mode:Recommended for MCP: Use
ISCL_APPROVAL_MODE=web and keep the approval dashboard open in a browser tab. When Claude requests a transaction, you will see it appear in the dashboard for approval.Multi-chain configuration
ThechainId parameter on each tool defaults to 8453 (Base). To use other chains, ensure ISCL Core has the corresponding RPC URL configured:
Troubleshooting
Tools don’t appear in Claude Desktop
- Verify the config file path is correct for your OS
- Check that the
commandpath points to the built JS file - Restart Claude Desktop after config changes
- Check Claude Desktop logs for MCP server startup errors
”ISCL Core not reachable”
The MCP adapter checks ISCL Core health on startup. Ensure Core is running:Approval hangs
If usingcli mode, check the ISCL Core terminal for the readline prompt. If using web mode, open http://localhost:3100/approval-ui and approve the pending request.
Schema validation errors
The MCP adapter validates parameters using Zod schemas. Ensure:- Addresses are checksummed 0x-prefixed (40 hex chars)
- Amounts are string integers (no decimals, no “0x” prefix)
- Chain IDs are positive integers
Security notes
- All transactions go through the full ISCL pipeline: policy, preflight, approval, signing.
- The adapter communicates with ISCL Core over localhost HTTP only.
- Tool descriptions inform the AI about security properties (policy enforcement, human approval).
- No signing material is ever exposed to the MCP transport layer.
References
- Adapter Development Tutorial — How the MCP adapter was built
- API Reference — Underlying API endpoints
- Configuration Reference — Environment variables
- MCP Protocol Specification — Official MCP documentation