MCP Server

The JAW CLI includes an MCP (Model Context Protocol) server that lets AI agents interact with JAW smart accounts programmatically.

Setup with Claude Desktop

Add this to your claude_desktop_config.json:

{
  "mcpServers": {
    "jaw": {
      "command": "npx",
      "args": ["-y", "@jaw.id/cli", "mcp"],
      "env": {
        "JAW_API_KEY": "YOUR_API_KEY",
        "JAW_CHAIN_ID": "8453"
      }
    }
  }
}

The MCP server runs on stdio transport — no ports or URLs to configure.

Available Tools

Tool	Description
`jaw_rpc`	Execute any RPC method (`method`, `params?`, `chainId?`, `session?`)
`jaw_config_show`	Display current configuration (secrets redacted)
`jaw_config_set`	Update a configuration value (`key`, `value`)
`jaw_status`	Check relay session status and configuration in use
`jaw_session_status`	Check local session-key (auto mode) status
`jaw_disconnect`	Close relay session and browser tab

jaw_rpc

The primary tool. Executes any EIP-1193 RPC method through the browser bridge.

{
  "method": "wallet_sendCalls",
  "params": {
    "calls": [{ "to": "0x...", "value": "0x..." }]
  },
  "chainId": 8453
}

Methods that require signing (e.g., wallet_sendCalls, personal_sign) will open the browser for passkey confirmation on first use. The session persists across multiple tool calls.

The chain is resolved in this order: the chainId argument, the JAW_CHAIN_ID environment variable, the configured defaultChain, then Ethereum mainnet (1).

Autonomous signing with session keys

If a session key exists (created with jaw session setup), pass session: true to sign without opening the browser:

{
  "method": "wallet_sendCalls",
  "params": {
    "calls": [{ "to": "0x...", "value": "0x..." }]
  },
  "session": true
}

Set JAW_SESSION=true in the MCP server's env block to make session mode the default (a per-call session: false still routes through the browser). Session mode supports eth_requestAccounts, eth_accounts, wallet_sendCalls, wallet_getCallsStatus, personal_sign, and eth_signTypedData_v4. Use jaw_session_status to check whether a session key exists and when it expires.

jaw_config_set

{
  "key": "defaultChain",
  "value": "8453"
}

Valid keys: apiKey, defaultChain, keysUrl, ens, relayUrl, sessionExpiry

Available Resources

The MCP server exposes documentation resources that AI agents can read for context.

Resource URI	Description
`jaw://api-reference`	Index of all supported RPC methods
`jaw://api-reference/{method}`	Detailed documentation for a specific method

Agent Skills

For AI coding assistants that support skills, there's an official skill package that provides deep knowledge of the JAW CLI and SDK.

Repository: github.com/JustaName-id/jaw-skills

Install

npx skills add JustaName-id/jaw-skills --skill jaw-cli

This installs two skills:

Skill	Description
`jaw-cli`	CLI usage patterns and best practices
`jaw-sdk-best-practices`	SDK development patterns and architectural guidance

Once installed, AI assistants automatically apply JAW-specific guidance when working with CLI commands or SDK integration code.