DEV Community

Cover image for MCP Server Setup: Connect WAIaaS to Claude Desktop in 3 Commands
Wallet Guy
Wallet Guy

Posted on

MCP Server Setup: Connect WAIaaS to Claude Desktop in 3 Commands

Claude's Model Context Protocol (MCP) lets you add custom tools to your AI agent, but most MCP servers handle basic tasks like file management or web scraping. What if your Claude agent could execute onchain transactions, manage DeFi positions, and handle crypto payments automatically? With WAIaaS as your MCP server, Claude Desktop transforms into a crypto-native AI agent with wallet capabilities in just three commands.

Why MCP + Wallet Matters

The Model Context Protocol creates a bridge between AI agents and external systems, but the crypto ecosystem has been largely untapped. Developers building AI agents for DeFi, NFT trading, or payment automation currently face a choice: build wallet infrastructure from scratch or limit their agents to read-only blockchain queries.

Meanwhile, every major AI framework is adopting MCP as the standard for tool integration. Claude Desktop already ships with MCP support, and frameworks like Cline, Roo-Cline, and others are following suit. The opportunity is clear: whoever provides the best MCP wallet server wins the AI × crypto integration space.

The WAIaaS MCP Solution

WAIaaS operates as a native MCP server with 45 tools spanning wallet management, DeFi protocols, NFTs, and payment automation. Unlike REST APIs that require custom integration, WAIaaS speaks MCP natively—add one server to your Claude config, and your agent immediately understands how to send tokens, swap on DEXes, and manage lending positions.

The architecture works through three layers: the WAIaaS daemon provides the wallet infrastructure, the MCP server (@waiaas/mcp package) translates between MCP protocol and daemon API, and Claude Desktop consumes the tools through standard MCP channels.

Here's what the 45 MCP tools cover:

  • Wallet tools: get-balance, get-address, send-token, list-transactions
  • DeFi tools: get-defi-positions, action-provider (15 protocols)
  • Policy tools: get-policies, approve-token (21 policy types with 4 security tiers)
  • NFT tools: list-nfts, transfer-nft, get-nft-metadata
  • Payment tools: x402-fetch (HTTP 402 payment protocol)

Quick Setup Process

WAIaaS provides a three-command setup that handles daemon installation, wallet creation, and MCP registration:

npm install -g @waiaas/cli
waiaas quickstart
waiaas mcp setup --all
Enter fullscreen mode Exit fullscreen mode

The quickstart command creates your daemon configuration, starts the service on localhost:3100, and generates both Ethereum and Solana wallets with session tokens. The mcp setup --all command auto-detects your Claude Desktop installation and writes the MCP server configuration.

Manual MCP Configuration

For advanced setups or non-standard Claude installations, you can manually configure the MCP server. Add this to your claude_desktop_config.json:

{
  "mcpServers": {
    "waiaas": {
      "command": "npx",
      "args": ["-y", "@waiaas/mcp"],
      "env": {
        "WAIAAS_BASE_URL": "http://127.0.0.1:3100",
        "WAIAAS_SESSION_TOKEN": "wai_sess_eyJhbGciOiJIUzI1NiJ9...",
        "WAIAAS_DATA_DIR": "~/.waiaas"
      }
    }
  }
}
Enter fullscreen mode Exit fullscreen mode

The session token provides wallet access to Claude while maintaining security boundaries. Each MCP server instance can target a specific wallet through the WAIAAS_SESSION_TOKEN environment variable.

Multi-Wallet MCP Setup

For complex scenarios requiring multiple wallets (trading vs. treasury, different chains, etc.), configure separate MCP servers:

{
  "mcpServers": {
    "waiaas-trading": {
      "command": "npx",
      "args": ["-y", "@waiaas/mcp"],
      "env": {
        "WAIAAS_BASE_URL": "http://127.0.0.1:3100",
        "WAIAAS_AGENT_ID": "019c47d6-51ef-7f43-a76b-d50e875d95f4",
        "WAIAAS_AGENT_NAME": "trading-agent",
        "WAIAAS_DATA_DIR": "~/.waiaas"
      }
    },
    "waiaas-treasury": {
      "command": "npx",
      "args": ["-y", "@waiaas/mcp"],
      "env": {
        "WAIAAS_BASE_URL": "http://127.0.0.1:3100",
        "WAIAAS_AGENT_ID": "019c4cd2-86e8-758f-a61e-9c560307c788",
        "WAIAAS_AGENT_NAME": "treasury-wallet",
        "WAIAAS_DATA_DIR": "~/.waiaas"
      }
    }
  }
}
Enter fullscreen mode Exit fullscreen mode

Each server targets a different wallet through unique agent IDs, allowing Claude to understand context ("use the trading wallet for swaps, treasury wallet for large transfers").

Real-World MCP Examples

Once configured, Claude Desktop gains immediate access to all wallet capabilities. Here are practical examples of what becomes possible:

Portfolio Management: "Show me my DeFi positions across all protocols" triggers the get-defi-positions tool, returning lending positions from Aave, staking balances from Lido, and LP positions from Uniswap.

Automated Trading: "Swap 0.1 SOL for USDC when the price hits $200" combines the get-balance tool for current holdings, market data analysis, and the action-provider tool targeting Jupiter swap.

Payment Automation: "Pay for this API call automatically" uses the x402-fetch tool, which handles HTTP 402 Payment Required responses by executing token transfers and retrying requests.

NFT Operations: "Transfer my Solana NFT to this address" leverages list-nfts for discovery and transfer-nft for execution, with metadata fetching through get-nft-metadata.

Security Through Policy Integration

The MCP tools respect WAIaaS's policy engine, which enforces security through 21 policy types and 4 security tiers. When Claude attempts a transaction, the policy engine evaluates rules like spending limits, token whitelists, and time restrictions.

For example, a SPENDING_LIMIT policy with INSTANT tier ($10), NOTIFY tier ($100), and DELAY tier ($1000) means:

  • Small transactions execute immediately
  • Medium transactions execute with notifications
  • Large transactions queue for 15-minute delays
  • Transactions above $1000 require human approval

This policy enforcement happens transparently through MCP—Claude receives appropriate responses based on policy evaluation, learning to adapt its behavior to security constraints.

Quick Start Guide

Here's the complete setup process for getting Claude Desktop connected to WAIaaS:

  1. Install and initialize WAIaaS:
   npm install -g @waiaas/cli
   waiaas init
   waiaas start
Enter fullscreen mode Exit fullscreen mode
  1. Create wallets and sessions:
   waiaas quickset --mode mainnet
Enter fullscreen mode Exit fullscreen mode
  1. Register with Claude Desktop:
   waiaas mcp setup --all
Enter fullscreen mode Exit fullscreen mode
  1. Restart Claude Desktop to load the new MCP server configuration

  2. Test the integration by asking Claude: "What's my wallet balance?" or "Show me my DeFi positions"

The setup process creates both Ethereum and Solana wallets by default, with session tokens that provide read/write access through the MCP tools. You can fund the wallets and immediately start testing onchain operations.

Advanced MCP Features

Beyond basic wallet operations, WAIaaS MCP integration supports advanced features that demonstrate the power of native MCP design:

Batch Operations: The send-batch tool accepts arrays of transactions, enabling Claude to optimize gas costs by bundling operations. For example, "approve USDC and then add liquidity to Uniswap" becomes a single batch transaction.

Simulation Mode: Every transaction tool accepts a dryRun parameter, letting Claude test operations before execution. This enables sophisticated agent behavior like "simulate this swap to check slippage before executing."

Real-time Monitoring: The list-incoming-transactions and get-incoming-summary tools provide incoming payment detection, enabling agents to react to received funds automatically.

Cross-chain Operations: Tools like action-provider with LI.FI and Across protocols enable bridge operations, while the policy engine ensures proper network restrictions.

WAIaaS stands out in the MCP ecosystem because it was designed as an MCP server from the ground up, not adapted from a REST API. This native approach means better error handling, proper tool discovery, and seamless integration with Claude's reasoning capabilities.

For additional context on WAIaaS architecture and capabilities, check out Building AI Agents That Actually Handle Money: The WAIaaS Architecture and Policy Engine Deep Dive: 4-Tier Security for AI Agent Wallets.

What's Next

With Claude Desktop connected to WAIaaS through MCP, you've unlocked the full spectrum of onchain operations for your AI agent. Start with simple balance queries and token transfers, then explore DeFi integrations as you build confidence in the system. The 45 MCP tools provide comprehensive coverage of crypto operations while the policy engine ensures security at every step.

Ready to give your Claude agent wallet superpowers? Clone the repository at https://github.com/minhoyoo-iotrust/WAIaaS to get started, or visit https://waiaas.ai for comprehensive documentation and examples.

Top comments (0)