ows-mcp-wallet
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ows-mcp-wallet What's my wallet balance?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
π OWS MCP Wallet - Agent Treasury with Spending Limits
MCP server that exposes OpenWallet Standard to Claude with built-in policy engine and spending limits.
Hackathon Tracks: #05 (Agent Treasury) + #06 (MCP Wallet Server)
π― What It Does
Allows AI agents (like Claude) to:
β Check wallet balances across multiple chains
β Send transactions with policy enforcement
β Automatic spending limit protection
β Multi-chain support (Ethereum, Solana, Base)
β Session-scoped security
Demo: Agent can't overspend even if instructed to!
Related MCP server: AgenticBTC MCP
π Quick Start (15 Minutes!)
New: Auto-generate test wallets! No need for MetaMask/Phantom.
# 1. Install dependencies
cd ~/ows-mcp-wallet
npm install
# 2. Generate test wallet (creates addresses + private keys)
npm run generate
# 3. Copy output to .env file
# (Script tells you exactly what to copy)
# 4. Get testnet tokens
# Visit faucets (links in output)
# 5. Test it works
npm test
npm run cli balance
# 6. Send real testnet transaction!
npm run cli send ethereum-sepolia 0x000... 0.01π Full walkthrough: See QUICKSTART.md for detailed 15-min guide
π Documentation
QUICKSTART.md β - 15-minute setup guide (start here!)
SETUP-GUIDE.md - Detailed step-by-step setup
ENV-VARIABLES.md - Complete environment variable reference
MOBILE-PLAN.md - Mobile-friendly hackathon guide
GETTING-STARTED.md - Friday build schedule
π§ New Commands
npm run generate # Generate test wallet
npm run test # Verify configuration
npm run cli balance # Check balances
npm run cli policy # View spending limits
npm run cli send # Send test transaction
npm run build # Build for production
npm run dev # Run in watch modeπ§ Configure Claude Desktop
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on Mac):
{
"mcpServers": {
"ows-wallet": {
"command": "node",
"args": ["/path/to/ows-mcp-wallet/dist/mcp-server.js"],
"env": {
"ETH_ADDRESS": "0xYourAddress",
"SOL_ADDRESS": "YourSolanaAddress"
}
}
}
}Restart Claude Desktop.
π¬ Demo Script
Test 1: Check Balance
You: "What's my wallet balance?"
Claude: *calls get_balance tool*
Response: Shows balances across all chainsTest 2: Send Transaction (Allowed)
You: "Send 0.01 ETH to 0x123... on Sepolia"
Claude: *calls send_transaction*
Response: β
Transaction approved and preparedTest 3: Overspending (Blocked)
You: "Send 100 ETH to 0x456..."
Claude: *calls send_transaction*
Response: β DENIED - Exceeds $50 per-transaction limitTest 4: Check Policy
You: "What are my spending limits?"
Claude: *calls check_policy*
Response: Shows daily limit, spent amount, remaining allowanceπ Policy Engine
Default limits (configurable):
Daily limit: $100 USD
Per-transaction limit: $50 USD
Allowed chains: Sepolia, Devnet, Base Sepolia
Optional: Address whitelist
ποΈ Architecture
Claude (AI Agent)
β
MCP Protocol
β
OWS MCP Server
β
Policy Engine (checks limits)
β
Wallet Manager (prepares transaction)
β
OWS (signs & broadcasts)
β
Blockchainπ Project Structure
ows-mcp-wallet/
βββ mcp-server.ts # MCP server implementation
βββ wallet-manager.ts # Multi-chain wallet interface
βββ policy-engine.ts # Spending limits & policy
βββ package.json
βββ tsconfig.json
βββ .env.example
βββ testnet-setup.md # Testnet token guide
βββ README.mdπ¨ Development Checklist
Morning (Setup - 1-2 hours)
Project structure created
Dependencies installed
Get testnet tokens (ETH, SOL, Base)
Create OWS wallet
Update .env with addresses
Build project
Afternoon (Core Features - 3-4 hours)
Wallet Manager implemented
Policy Engine implemented
MCP Server implemented
Test with real testnet addresses
Verify policy enforcement works
Test all 3 tools with Claude
Evening (Demo & Polish - 2-3 hours)
Record 2-min demo video
Create submission materials
Deploy to GitHub
Write clear documentation
Submit to hackathon
π₯ Demo Video Outline
2-Minute Demo:
0:00 - Introduction
"AI agents need wallets. But they also need guardrails."
0:20 - Show the problem
"Without limits, an agent could drain your wallet"
0:40 - Show the solution
Live demo of Claude checking balance
Claude sending small transaction (approved)
Claude trying to overspend (blocked)
1:30 - Show the tech
Quick code walkthrough
Policy engine enforcement
Multi-chain support
1:50 - Call to action
"Built on OWS. Local-first. Self-custody."
GitHub link
π Production Roadmap
If this wins/scales:
Phase 1: Polish MVP
Add actual OWS integration
Broadcast to real testnets
Transaction history tracking
Phase 2: Enhanced Features
Custom policy templates
Multi-user support
Audit logging dashboard
Phase 3: Monetization
Free tier: Personal use
Pro ($49/mo): Team policies
Enterprise: White-label solution
π€ Contributing
Built for the OpenWallet Standard Hackathon - April 3, 2026
π License
MIT
π Links
OpenWallet Standard: https://openwallet.sh/
Hackathon: https://hackathon.openwallet.sh/
MCP Docs: https://modelcontextprotocol.io/
Available Tools
3 toolscheck_policyA
Check current spending limits and policy status
Inputs: no named parameters.
get_balanceA
Get wallet balance across all supported chains
Inputs: no named parameters.
send_transactionB
Send cryptocurrency to an address (subject to policy limits)
Inputs: to (required), chain (required), amount (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: fetching balances, sending transactions, and checking policies. No overlap or ambiguity exists between them.
All tools follow the same verb_noun snake_case pattern (get_balance, send_transaction, check_policy), making the naming fully consistent and predictable.
With only 3 tools, the server is tightly scoped to basic wallet operations. Each tool handles a core function without redundancy.
The set covers balance queries, transactions, and policy checks, but lacks features like transaction history or address generation. These are minor gaps for a policy-limited wallet.
Maintenance
Related MCP Connectors
Give AI agents a wallet with a spending limit. Non-custodial USDC on Base, server-enforced limits.
Crypto wallet for AI agents: balances, payments, swaps and trading with owner controls.
Provide AI agents and automation tools with contextual access to blockchain data including balanceβ¦
Wallets and rails that let AI agents spend money safely.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to analyze Ethereum wallets, simulate transactions, and draft transfers with deterministic policy and risk scoring, requiring human approval before on-chain execution.12 npmISC
- AlicenseAqualityCmaintenanceConnects AI agents to Bitcoin payment rails with owner-defined spending policies and limits.2622 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to create and manage contract-guarded USDC wallets on Base with enforceable per-payment, daily, and monthly caps, vendor allowlists, escalation thresholds, and freeze controls. It provides read-only policy checks plus unsigned transaction proposals for payments, funding, vendor management, wallet creation, and module deployment without holding keys or broadcasting.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to send ETH and tokens, approve token spending, and make contract calls while every transaction is decoded, simulated, checked against policy, threat lists, and user intent, with suspicious actions blocked or escalated for human approval.MIT