Phantom wallet mcp
Execute wallet operations through the Phantom MCP server — get addresses, sign transactions, transfer tokens, buy tokens, and sign messages across Solana, Ethereum, Bitcoin, and SuiFrom its SKILL.md
npx -y skills add sendaifun/skills --skill phantom-wallet-mcpAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
2.0 KB, 435 tokens by cl100k_base, as published. Nobody here has run it
Phantom Wallet MCP
Use the phantom MCP server to interact with the user's Phantom wallet directly.
Available Tools
| Tool | Description |
|---|---|
get_wallet_addresses | Get blockchain addresses (Solana, Ethereum, Bitcoin, Sui) for the connected wallet |
sign_transaction | Sign a transaction (base64url for Solana, RLP hex for Ethereum) |
transfer_tokens | Transfer SOL or SPL tokens on Solana — builds, signs, and sends the transaction |
buy_token | Fetch Solana swap quotes from Phantom API; optionally sign and send |
sign_message | Sign a UTF-8 message with automatic chain-specific routing |
Setup
The phantom MCP server requires a PHANTOM_APP_ID environment variable from Phantom Portal. On first use, it opens a browser for OAuth authentication via Google or Apple login.
Supported Networks
| Chain | Networks |
|---|---|
| Solana | mainnet, devnet, testnet |
| Ethereum | Mainnet, Sepolia, Polygon, Base, Arbitrum |
| Bitcoin | Mainnet |
| Sui | Mainnet, Testnet |
Networks use CAIP-2 format (e.g., solana:mainnet, eip155:1).
Examples
Get wallet addresses
Ask the phantom MCP to retrieve the user's wallet addresses, then use them for transactions.
Transfer SOL
Use transfer_tokens to send SOL to a recipient address. The MCP handles transaction building, signing, and submission.
Sign a message
Use sign_message for wallet verification or authentication flows. The MCP routes to the correct chain based on the network parameter.
Important Notes
- Sessions persist locally in
~/.phantom-mcp/session.json - This is preview software — use a separate wallet with minimal funds for testing
- The MCP server runs via stdio transport (launched by
npx -y @phantom/mcp-server)
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most mcp tooling skills give in 435 tokens
Counted across 780 of the 1,136 authors here whose files we hold, read 2026-09-06
- Use Zod for input validationin 34 of 780, across 21 files
- Use stdio for local clientsin 27 of 780, across 10 files
- Restart Claude Code after configurationin 26 of 780, across 23 files
- Verify MCP server connection before using toolsin 23 of 780, across 17 files
- Define input schemas for every toolin 20 of 780, across 11 files
- Use Streamable HTTP for remote clientsin 18 of 780, across 8 files
- Pin SDK version in package.jsonin 17 of 780, across 6 files
- Keep server logic independent of transportin 16 of 780, across 6 files
- Verify SDK methods against official documentationin 15 of 780, across 5 files
- Format evaluation results as an XML filein 15 of 780, across 12 files
- Test servers using the MCP Inspectorin 15 of 780, across 14 files
- Create ten complex and independent evaluation questionsin 14 of 780, across 11 files
Said here and by no other author read
- Use the phantom MCP server for wallet interactions
- Retrieve wallet addresses before performing transactions
- Use CAIP-2 format for network specifications
- Authenticate via browser OAuth on first use
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.