Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.phantom.com/llms.txt

Use this file to discover all available pages before exploring further.

The Phantom OpenClaw plugin (@phantom/phantom-openclaw-plugin) gives OpenClaw agents direct access to a Phantom wallet. Once installed, agents can check balances, fetch addresses, transfer tokens, sign messages, swap assets, and use the rest of the Phantom MCP tool surface from inside OpenClaw.

​
Install

Install the plugin: 
openclaw plugins install @phantom/phantom-openclaw-plugin
If you are testing a local checkout instead of the published package: 
openclaw plugins install -l /absolute/path/to/packages/phantom-openclaw-plugin

​
Enable the plugin

Add the plugin to your OpenClaw config at ~/.openclaw/openclaw.json: 
{
  "plugins": {
    "allow": [
      "phantom-openclaw-plugin"
    ],
    "entries": {
      "phantom-openclaw-plugin": {
        "enabled": true
      }
    }
  }
}
If you already have other plugins configured, add phantom-openclaw-plugin to your existing allow array and entries object.

​
Optional: associate tool calls with your app

If you registered your app in Phantom Portal, you can add your App ID to the plugin entry so tool calls made through the plugin are attributed to your application: 
{
  "plugins": {
    "entries": {
      "phantom-openclaw-plugin": {
        "enabled": true,
        "PHANTOM_APP_ID": "your-app-id",
        "PHANTOM_CLIENT_ID": "your-client-id"
      }
    }
  }
}
Both keys are optional. PHANTOM_CLIENT_ID is only needed if your app uses a Phantom Connect Client ID. Without either value, the plugin authenticates with the default device-code flow and tool calls are not attributed to a specific app.

​
Authenticate on first use

After installing and enabling the plugin:
  1. Restart OpenClaw.
  2. Ask the agent to perform a wallet action such as What are my Phantom wallet addresses?
  3. OpenClaw will trigger Phantom’s browser-based authentication flow.
  4. Sign in, approve the wallet session, and return to OpenClaw.
The session is stored locally and reused across restarts until it is deleted or expires.

​
What the plugin exposes

The plugin wraps the Phantom MCP server and exposes the same wallet tool surface inside OpenClaw, including:
  • get_connection_status
  • get_wallet_addresses
  • get_token_balances
  • send_solana_transaction
  • send_evm_transaction
  • sign_solana_message
  • sign_evm_personal_message
  • sign_evm_typed_data
  • simulate_transaction
  • get_token_allowance
  • transfer_tokens
  • buy_token
  • portfolio_rebalance
  • phantom_login
  • pay_api_access
  • The Phantom perp tools for Hyperliquid-backed trading flows (deposit_to_hyperliquid, open_perp_position, close_perp_position, cancel_perp_order, update_perp_leverage, transfer_spot_to_perps, withdraw_from_perps)
See the tool reference for the current tool behavior and parameters.

​
Notes

  • No manual MCP server wiring is required inside OpenClaw.
  • The plugin uses Phantom’s authentication flow automatically.
  • Transaction sends and transfers use simulation-first flows where supported. Review the preview before approving execution.

​
Troubleshooting

  • Confirm the plugin is present in both plugins.allow and plugins.entries.
  • Verify the entry is enabled: "enabled": true.
  • Restart OpenClaw after config changes.
  • Trigger a wallet action such as get_wallet_addresses.
  • Ensure the machine can open a browser window.
  • Check that OpenClaw is using the expected installed plugin copy if you are testing a local path install.
  • Make sure the installed plugin copy matches the version of the manifest you expect.
  • If you are testing a local path install, reinstall or resync the plugin so OpenClaw validates against the current manifest.

Phantom MCP Server setup

Standalone MCP server setup for Claude Desktop, Cursor, and Claude Code

Tool reference

Parameters and behavior for the current Phantom wallet tool surface