Nodit MCP Server

What is Nodit MCP Server?

Nodit MCP Server is a Model Context Protocol server that connects AI agents and developers to structured, context-ready blockchain data across multiple networks through Nodit's Web3 infrastructure. It normalizes multi-chain data for AI reasoning and decision-making, allowing developers to build Web3-integrated applications without specialized blockchain expertise.

How to use Nodit MCP Server?

Install via npx @noditlabs/nodit-mcp-server@latest and set the NODIT_API_KEY environment variable. Run the server with node build/index.js after building locally, or integrate it with Cursor IDE or Claude Desktop by configuring mcp.json with the npx command and your API key. For remote integration, use the SSE endpoint https://mcp.nodit.io/sse?apiKey=INSERT_YOUR_API_KEY.

Key features of Nodit MCP Server

• Connects AI agents to normalized, multi-chain blockchain data
• Supports EVM-compatible (Ethereum, Base, Arbitrum, Polygon, etc.) and non-EVM networks (Aptos, Bitcoin, Dogecoin, TRON, XRPL, Sui, Solana)
• Provides RPC Node & Node APIs for real-time queries and transaction submissions
• Offers high-level Web3 Data APIs with processed datasets (token transfers, account summaries, etc.)
• Includes GraphQL Indexer APIs for detailed Aptos blockchain activities
• Tools for listing API categories, operations, and specs, plus executing API calls

Use cases of Nodit MCP Server

• Build AI agents that query and analyze real-time blockchain data across multiple networks
• Monitor on-chain activity such as token transfers and transaction volumes
• Retrieve account-level transaction histories and asset movements
• Develop Web3-integrated applications without raw RPC complexity
• Integrate blockchain data into AI reasoning workflows via natural language prompts

FAQ from Nodit MCP Server

What makes Nodit MCP Server different from directly calling blockchain RPCs?

It normalizes and structures multi-chain data for AI agents, eliminating the need to handle raw event logs, chain-specific data structures, or complex node RPCs.

What are the runtime requirements?

Node.js 18+ and a Nodit API key obtained from Nodit Console.

Where does the blockchain data come from?

Data is accessed through Nodit's professionally operated node infrastructure, Web3 Data APIs, and GraphQL indexing services across supported networks.

What transport protocols are supported?

For local server-client interaction, only stdio-based communication (JSON-RPC over stdio) is supported. Remote MCP integration uses SSE (Server-Sent Events) via the endpoint with an API key.

How is authentication handled?

Authentication requires a Nodit API key set as the NODIT_API_KEY environment variable for local setups, or passed as a query parameter (apiKey=INSERT_YOUR_API_KEY) for the remote SSE endpoint.