mcp

This MCP server exposes a multi-network data access layer for Pocket Network’s public RPC endpoints, providing 63 networks including Ethereum, Polygon, Arbitrum, Optimism, Base, Solana, NEAR, Sui, Cosmos, and more. It supports natural language queries, live JSON-RPC method calls, domain resolution, token analytics, transaction inspection, and multi-chain comparisons, all accessible via an MCP client such as Claude Desktop, Claude Code CLI, or MCP Inspector. You can ask questions like a natural language query (e.g., “get the latest height for ethereum”), execute direct RPC calls, or perform cross-chain analyses and token lookups across supported networks. Built-in safety features help prevent overly large responses and offer safe alternatives when needed.

To use, configure your MCP client to point at the local or deployed MCP pocket-network server configuration, then start querying with your chosen client. For example, you can ask for balances, block details, token metadata, or cross-chain comparisons across all 63 networks. The server also supports domain resolution (ENS and Unstoppable Domains), transaction and block queries, and a suite of specialized tools across EVM, Solana, Sui, and Cosmos ecosystems.

Prerequisites:

• Node.js 18+ (and npm)
• Access to the MCP server repository (clone or download from GitHub)

Install and build the MCP server:

# Clone the repository
git clone https://github.com/pokt-network/mcp.git
cd mcp-pocket

# Install dependencies
npm install

# Build the project
npm run build

Configure the MCP client to connect to this server (example paths may vary by environment):

# Claude Desktop (example config)
# JSON at ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%/Claude/claude_desktop_config.json (Windows)
{
  "mcpServers": {
    "pocket-network": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-pocket/dist/index.js"]
    }
  }
}

Launch the server and start querying using your MCP client, then you can issue natural language questions to retrieve blockchain data, or call RPC methods directly through the client.

Notes and tips:

• Ensure Node.js version is 18 or newer to match the build requirements.
• The provided mcp_config uses a Node server entry point at dist/index.js; adjust the absolute path to your build output accordingly.
• If you run into environment variable issues, you can add sensible defaults under env in the mcp_config, for example to set API keys or network endpoints if required by your deployment.
• This MCP server targets 63 networks; some queries may be gated by safety rules to prevent large context windows or costly scans. When blocked, you’ll receive guidance and safe alternatives.
• Use the built-in safety features to avoid long-running or high-volume queries; for large history queries, consider using current-state queries or limited blocks.
• The available tools span Core Blockchain, Domain Resolution, Transactions & Blocks, Tokens, Multi-Chain & Historical Analysis, Smart Contract interactions, Utility tools, Endpoint management, and specialized modules for Solana, Sui, and Cosmos.