@provablehq/shield-mcp
v0.1.2
Published
Local MCP companion for Shield Wallet Agent Access
Maintainers
Keywords
Readme
Shield MCP
Connect AI assistants to your Shield wallet through the Model Context Protocol. Read balances, send payments, swap tokens and execute Aleo programs, with permissions managed in Shield.
Get started
Requires Node.js 22+ and Shield Extension with Agent Access in Chrome 120+.
npm install --global @provablehq/shield-mcp
shield-mcp setup --client claude-code- Open Shield → Settings → Agent Access (MCP). First-time users go directly to setup.
- Paste the pairing code from your terminal into Enter pairing code. Shield enables Agent Access and connects automatically.
- Compare the client fingerprint and approve the permissions you want to grant.
- Start or restart your MCP client. Try asking: “What is my Shield wallet balance?”
For other clients, replace claude-code with claude-desktop, codex or manual. The manual option prints an MCP configuration you can copy into your client.
Already configured Shield? Enable Agent Access if it is off. Going back during client review keeps the request pending; choose Continue setup in Agent Access to resume, or Cancel connection to reject it. Existing companion pairing and client permissions are preserved when you reuse the same pairing code.
If you use Dev and installed Shield side by side, enable Agent Access only in the installation you intend to use. Each companion connects to one wallet at a time; setup and doctor show the connected extension ID.
How it works
The companion connects your MCP client to Shield over local WebSockets. It starts automatically; keep Chrome running, but no extra browser tab or open wallet panel is needed. Signing and proving are handled by Shield.
Choose which actions require approval in Shield. Access pauses when the wallet locks unless you authorize a background session. Disable Agent Access in Shield to stop wallet access.
Useful commands
shield-mcp doctor # Check the connection and component versions
shield-mcp repair # Update client paths after moving the installation
shield-mcp --help # See all commandsDevelopment
Source development requires a compatible shield-core checkout at ../shield-core. The npm package includes the required Core code.
See implementation notes for companion lifecycle and developer diagnostics.
npm ci
npm run setup -- --client manual
npm run typecheck
npm test
npm run test:packageLicense
Proprietary. Personal and commercial use, including through automated agents,
is permitted under the Shield MCP license. Separately licensed
components retain their own license terms, included in dist/THIRD_PARTY_NOTICES.txt.
