Setup

​

Features

• Device-code authentication: Browser-based Phantom sign-in with device authorization. No App ID or Phantom Portal setup required.
• Dedicated agent wallets: Each agent gets its own wallet on authentication — separate from your personal wallet.
• Session persistence: Automatic session management with stamper keys stored in ~/.phantom-mcp/session.json.
• Session refresh: On HTTP 401, the shared CLI wrapper refreshes the session once and retries that call. If the refresh fails, it clears the local session and returns AUTH_EXPIRED. Call login, then retry the tool yourself. A submission failure (submission-failed or error code -32009) does not clear the session. In @phantom/cli@3.0.0, wallet_addresses catches the client error and throws a new error that keeps only the message, so that wrapper never sees the 401. The call fails as Failed to get wallet addresses: ... with no refresh and no AUTH_EXPIRED. The sign, send, and transfer handlers in that release do the same. This is a defect in the published package.
• Multi-chain support: Works with Solana, supported EVM networks, Bitcoin, and Sui networks. Sui support has been deprecated. Arbitrum sends are rejected by evm_send, transfer, buy, and perps_deposit; it remains valid for perps withdrawals. BNB Smart Chain (eip155:56) is unsupported. See the supported networks.
• Simulation-first wallet flows:
  • solana_send, evm_send, and transfer can preview asset changes and warnings before submitting.
• 30 wallet, swap, and perp tools. See the tool reference for full parameter documentation.
  • Wallet: wallet_status, wallet_addresses, wallet_balances, price, transfer, solana_send, evm_send, solana_sign, evm_sign, evm_sign-typed, simulate, evm_allowance, login, logout, pay.
  • Swaps: buy (Solana, supported EVM networks, and cross-chain, no fees), wallet_rebalance (no fees).
  • Perps: perps_markets, perps_account, perps_positions, perps_orders, perps_history, perps_deposit, perps_open, perps_close, perps_cancel, perps_leverage, perps_transfer, perps_withdraw, perps_withdraw-hl-spot.

​

Installation

​

Option 1: npx (recommended)

npx -y @phantom/mcp-server@latest

​

Option 2: Global install

npm install -g @phantom/mcp-server@latest

phantom-mcp

​

Setup guides

{
  "mcpServers": {
    "phantom": {
      "command": "npx",
      "args": ["-y", "@phantom/mcp-server@latest"]
    }
  }
}

{
  "mcpServers": {
    "phantom": {
      "command": "phantom-mcp"
    }
  }
}

{
  "mcpServers": {
    "phantom": {
      "command": "npx",
      "args": ["-y", "@phantom/mcp-server@latest"]
    }
  }
}

claude mcp add phantom -- npx -y @phantom/mcp-server@latest

claude mcp list

​

Environment variables

​

Authentication flow

1. Start Phantom’s device authorization flow.
2. Open your default browser so you can sign in with Google or Apple and approve the wallet session.
3. Save your session to ~/.phantom-mcp/session.json.

​

Agent wallets

• Existing prompts or workflows that assumed access to your personal wallet may no longer behave the same way.
• Newly authenticated agents must be funded before they can transfer tokens, swap, or perform other on-chain actions.
• Use wallet_addresses after authenticating to check the agent’s wallet address. Before funding it, confirm that the intended operation supports the network. BNB Smart Chain (eip155:56) is unsupported; an EVM address can receive BSC assets that the MCP cannot move. Balance visibility and quote availability do not prove sending support.

​

Session management

rm ~/.phantom-mcp/session.json

​

Security

• Device-code authentication: Secure browser-based sign-in flow with no local callback server.
• Session security: Session files have restrictive Unix permissions (user-only read/write, 0o600).
• Request signing: OIDC stamper signs KMS requests to prevent tampering.
• HTTPS: All API requests use HTTPS.

​

Testing

npx @modelcontextprotocol/inspector npx -y @phantom/mcp-server@latest

​

Troubleshooting

​

Related resources