How to Connect Helius to Cursor via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Helius, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

Helius + Cursor

Solana blockchain data through Helius: SOL and token balances, NFTs and tokens of a wallet (DAS API), readable transaction history, single transactions, wallet identity and funding source. Read-only.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

HELIUS_API_KEY

Step 1 — Get credentials

Setting up takes about 2 minutes. You need a Helius account; the Free plan works.

1. Sign up at https://dashboard.helius.dev.
2. Open API Keys and copy a key into HELIUS_API_KEY: only the key (a UUID such as 1a2b3c4d-...), not the whole RPC URL. It is sent as the api-key query parameter.
3. Install the connector and run helius_get_epoch_info: it shows the current Solana epoch, slot and block height, which confirms the key works.

What it reads: Solana mainnet through Helius, using standard Solana RPC, the DAS API for NFTs and tokens, Enhanced Transactions for a human-readable history and the Wallet API (beta). That covers the SOL balance of an account; everything a wallet holds (NFTs, compressed NFTs, SPL and Token-2022 tokens with balance, decimals and price where known, plus SOL); one asset or token by its mint address, with metadata, collection, royalties, creators and supply; token accounts by owner or mint; the transaction signatures of an address and single transactions with parsed instructions, balances and logs; a readable history with types such as TRANSFER, SWAP or NFT_SALE; a USD-valued portfolio, the balance changes per transaction and the incoming and outgoing transfers of a wallet; and who a known wallet belongs to (exchanges, protocols, institutions, also by .sol domain) and who first funded it with SOL.

Units and times: SOL amounts from RPC are lamports, 1,000,000,000 per SOL. Token amounts from token accounts are raw integers that the AI divides by 10^decimals of the mint. blockTime and timestamp are Unix seconds (UTC), and the AI converts them before quoting a time. USD prices in the Wallet API are hourly estimates for about the top 10,000 tokens and can be missing.

Credits: every Helius plan has monthly credits (Free: 1 million). A standard RPC call costs 1 credit, DAS and Enhanced calls more, and every Wallet API call 100 credits. The AI uses the RPC and DAS tools for routine questions and the Wallet API only for what it alone answers, such as USD values, identity and funder.

Read-only: every tool only reads, so there is nothing to confirm and no tool is switched off at install. No transaction is signed or sent; helius_parse_transactions only turns signatures into readable transactions.

Limits: on the Free plan RPC allows 10 requests a second, the DAS and Enhanced APIs 2 a second. Histories come up to 100 per call (raw signatures up to 1,000), and the AI pages with the last signature or the cursor it received. Only mainnet is configured. Enhanced Transactions is in maintenance mode at Helius, and the Wallet API is beta, so its formats may change.

Common errors: 401 means a missing or wrong API key, often the whole RPC URL pasted instead of the key. 429 means the plan rate limit or the monthly credits are used up; check the usage in the Helius dashboard. RPC errors come back as a JSON-RPC error object, for example for an invalid address. The Wallet API answers 404 when it knows no identity or funder for a wallet.

The connector does not sign or send transactions, set up webhooks or streams, estimate priority fees or read devnet.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Cursor

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Cursor reads MCP servers from ~/.cursor/mcp.json. Add this entry:

{
  "mcpServers": {
    "anythingmcp": {
      "url": "https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID",
      "headers": { "X-API-Key": "YOUR_MCP_API_KEY" }
    }
  }
}

1. Create an MCP API key in AnythingMCP under MCP Servers → your server → API keys, and paste it in place of YOUR_MCP_API_KEY.
2. Save the file and restart Cursor.
3. Open Cursor → Settings → MCP and check that anythingmcp is listed and connected.
4. Start chatting: the agent can now call the Helius tools.

Available tools

Example prompts

• "What does this Solana wallet hold? List SOL, tokens and NFTs with their amounts."
• "Show the last 20 transactions of this wallet in plain words: swaps, transfers and NFT sales."
• "What is the USD value of this wallet's token portfolio right now?"
• "Who is this wallet, and who first funded it with SOL?"
• "Look up this token mint: name, symbol, decimals, supply and price."

FAQ

Does Cursor support custom MCP servers on the free tier? Yes, MCP is available on Hobby, Pro and Business plans.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT
• Connect to Gemini
• Connect to Meta Muse
• Connect to Microsoft Copilot