HeyAnon MCP

What HeyAnon MCP MCP server does

HeyAnon MCP MCP server connects Cursor or Grok Bot to the remote HeyAnon MCP endpoint at https://api.heyanon.ai/mcp. It gives an agent access to wallet metadata, saved recipient addresses, supported protocols and networks, portfolio information, crypto research, and operations handled by Anon.

The read-oriented tools cover wallet lists, address books, projects, token holdings, transactions, DeFi positions, and CEX portfolio data. ask_gemma handles crypto research and returns an answer directly. ask_anon sends a self-contained request to Anon for activities such as balance checks, swaps, bridging, lending, staking, CEX operations, and scheduled automations.

The server can also send native coins or tokens with transfer_native and transfer_asset. These operations are irreversible, so they should be used only after checking the recipient, asset, network, and amount.

How it works

The plugin registers a remote MCP server rather than running an on-device service. The client authenticates each connection with an HeyAnon API key in the X-API-Key header over HTTPS. The repository contains configuration and an Agent Skill that guides wallet selection, complete request construction, background-task polling, and confirmation behavior.

Anon does not retain context between messages, so each ask_anon request must contain the information needed to perform the request. Anon processes one request at a time. Requests that create actions return a background task ID; the agent can use background_task, background_task_list, or isProcessing to monitor progress and retrieve results. Scheduled automations can be inspected with scheduled_task_list and scheduled_task_get.

Setup and configuration

HeyAnon MCP MCP server can be added through the Cursor Marketplace, where the API key is entered under the plugin’s setup values. Cursor users can also add the remote endpoint manually to .cursor/mcp.json in a project or to ~/.cursor/mcp.json, using the X-API-Key header.

Grok Bot users add it from Connect apps and enter the key in the secure field provided by the application. The key should not be pasted into a chat. Obtain it from the HeyAnon account settings under API keys. Cursor and Grok Bot store the credential on the client side; the repository does not store secrets.

Tools and capabilities

• Inspect EVM, Solana, and TON wallets with names, addresses, types, and labels.
• Resolve saved recipients through the address book.
• Check supported protocols and networks.
• Read per-wallet token, transaction, DeFi, and CEX portfolio data.
• Ask Gemma for direct crypto research answers.
• Send Anon requests for balances, swaps, bridging, lending, staking, CEX actions, and automations.
• Transfer native assets or tokens, monitor background work, and manage task or automation records.

Limitations and notes

The service can execute real transactions from attached wallets. ask_anon, transfer tools, abort, and task-deletion tools are destructive or state-changing; the accompanying skill instructs the agent to show the exact operation and wait for explicit confirmation. Cursor also asks before MCP calls by default, while Grok Bot reviews tool calls and supports “Ask first” rules.

The plugin depends on the remote HeyAnon service, an API key, and client support for the configured MCP connection. It does not run locally. Transfers are irreversible, and Anon’s lack of conversational context means follow-up requests must repeat relevant wallet, asset, network, and action details. The project is licensed under MIT.