Seal Wallet MCP Server
MCP server for Seal smart wallet β exposes on-chain wallet operations as AI-agent tools
Ask AI about Seal Wallet MCP Server
Powered by Claude Β· Grounded in docs
I know everything about Seal Wallet MCP Server. Ask me about installation, configuration, usage, or troubleshooting.
0/500
Reviews
Documentation
On-chain autonomous wallet infrastructure for Solana.
Seal is an open-source smart wallet SDK with on-chain policy enforcement β session keys, spending limits, scoped agent delegation, and guardian recovery β built with Pinocchio for minimal deploy cost and maximum compute efficiency.
Demo
Watch: An AI agent (via OpenClaw) transfers SOL from a Seal wallet, authorized by a session key created in Sigil. No seed phrases, no raw keypairs β just a pairing token.
Sigil β Agent Wallet Management App
Seal gives you the on-chain program. But how does the agent actually get a wallet?
Sigil is the companion mobile app that makes it as easy as creating a Telegram bot:
- Open Sigil, connect your wallet
- Tap "New Agent" β set daily limit, per-tx cap, allowed programs
- Get a pairing token (
sgil_xxx) - Hand the token to your AI agent β done
The agent calls new SigilAgent({ pairingToken }) and it has full wallet access, scoped by the limits you set. You see every transaction in your activity feed. You can lock the wallet, revoke sessions, or withdraw funds from your phone at any time.
Skill file β© Pairing token β© Agent gets full wallet control from anywhere
Why Seal?
| Problem | Existing Solutions | Seal |
|---|---|---|
| AI agents need to sign transactions automatically | Raw keypair in memory (SendAI Agent Kit) β no guardrails | On-chain session keys with scope + expiry + spending limits |
| Wallet providers are vendor-locked | Phantom KMS, Crossmint API, Privy MPC β keys in their servers | Self-custodial, keys encrypted locally, program is open-source |
| Policy enforcement is server-side | Turnkey/Crossmint policies run on their servers β bypassable | On-chain enforcement by Solana runtime β impossible to bypass |
| No Flutter SDK for autonomous wallets | None of them have Flutter support | Native Dart SDK via flutter_rust_bridge + Codama |
| Signing costs money | Custodial providers charge per-signature or per-wallet fees | Zero per-signature cost |
Architecture
flowchart TD
P["programs/seal-wallet<br/>Pinocchio on-chain program"]
C["crates/seal-core<br/>Rust crypto + policy primitives"]
TS["sdk/seal-ts<br/>TypeScript SDK"]
D["sdk/seal-dart<br/>Flutter/Dart SDK"]
T["tests<br/>Rust + integration coverage"]
DOCS["docs<br/>Technical documentation + site"]
C --> TS
C --> D
P --> TS
P --> D
P --> T
TS --> DOCS
D --> DOCS
Quick Start
# Build the on-chain program
cd programs/seal-wallet
cargo build-sbf
# Run tests
cargo test
# Deploy to devnet
solana program deploy target/deploy/seal_wallet.so --url devnet
Key Concepts
Smart Wallet (PDA)
A program-derived account that holds your assets. Owned by the Seal program, controlled by your master key.
Session Keys
Ephemeral keypairs with scoped permissions: which programs to call, which instructions, how much to spend, when they expire. Agents use these to sign autonomously.
Agent Delegation
Register AI agents with specific scopes β e.g., "LP Bot can only call Meteora DLMM, max 5 SOL/day." The on-chain program enforces these limits.
Guardian Recovery
Set m-of-n guardians who can rotate your master key if you lose access.
Tech Stack
| Layer | Technology | Why |
|---|---|---|
| On-chain program | Pinocchio v0.10 | Zero-dep, ~10x smaller binary than Anchor, lower deploy cost |
| IDL & client gen | Codama | Multi-language client generation (JS, Rust, Dart) |
| Rust core | ed25519-dalek, aes-gcm | Battle-tested cryptographic primitives |
| Dart FFI | flutter_rust_bridge v2 | Flutter Favorite, auto binding generation |
| Testing | LiteSVM / Bankrun | Fast local Solana VM for testing |
License
Apache-2.0

