nodit

Nodit MCP Server connects AI agents and developers to Nodit's Web3 infrastructure, providing normalized, context-ready multi-network blockchain data via a lightweight, modular toolset. The server exposes a set of tools that AI agents can discover and invoke through JSON-RPC over standard input/output. Core capabilities include listing API categories, listing API operations across Node APIs, Data APIs, Aptos Indexer APIs, and Webhook APIs, retrieving detailed API specifications, and performing actual API calls. This enables agents to reason over blockchain data without needing direct access to raw RPCs or chain-specific formats. The server communicates using the MCP JSON-RPC protocol, and you can interact with it by sending JSON-RPC payloads to the running process (e.g., through npx invocation or a local build). When integrated with clients like Cursor or Claude Desktop, users can discover Nodit tools, query data, and execute actions across multiple networks (Ethereum, Base, Optimism, Polygon, Aptos, Bitcoin, Dogecoin, XRPL, and more). You can also connect to Nodit’s Remote MCP Server for cloud-based access. To start locally with npx, you’ll need to provide your Nodit API key, which authenticates your requests to Nodit’s services. Once running, you can request the list of available tools, then call specific tools such as list_nodit_api_categories or list_nodit_node_apis to explore capabilities and parameters. The server also supports sending requests directly via JSON-RPC over stdio, which you can test with simple echo commands piped into node build/index.js (for a local build) or via the npx invocation for the latest release.

Prerequisites:

• Node.js 18 or newer
• npm (comes with Node.js)
• Nodit API Key (sign up at Nodit Console and obtain an API key)

Option A: Quick start using npx (recommended)

1. Ensure you have a Nodit API key ready.
2. Run the MCP server via npx (no local install required): npx @noditlabs/nodit-mcp-server@latest
3. When prompted or in your environment, set the API key environment variable: export NODIT_API_KEY=your-api-key

Option B: Local build from source

1. Clone the repository (or use your preferred fork): git clone --recurse-submodules https://github.com/noditlabs/nodit-mcp-server.git
2. Move into the project directory and install dependencies: cd nodit-mcp-server npm install
3. Build the project: npm run build
4. Start the server from the built entry point and provide the API key: node build/index.js (Alternatively, run with an environment variable: export NODIT_API_KEY=your-api-key)

Verifying setup:

• Ensure the Nodit API key is set as an environment variable (NODIT_API_KEY).
• You should be able to send a JSON-RPC payload to the running server, for example: {"method":"tools/list","params":{},"jsonrpc":"2.0","id":1}.

Tips and common issues:

• Environment variable: Always ensure NODIT_API_KEY is set before starting the server. Without proper authentication, API requests will fail.
• Running locally: The server communicates via JSON-RPC over stdio. You can test with direct node input, or pipe commands using echo to interact with build/index.js when running a local build.
• Remote usage: If you prefer to use Nodit's remote MCP endpoint, you can connect to https://mcp.nodit.io/sse?apiKey=INSERT_YOUR_API_KEY for cloud-powered access.
• Claude/Cursor integrations: You can connect to the Nodit MCP server from Cursor or Claude Desktop by configuring the mcp.json settings with the nodit server entry and providing your API key.
• Supported networks: Nodit MCP Server supports a broad set of networks (EVM and non-EVM) via Node APIs, Data APIs, and Aptos Indexer APIs. Review the Nodit Developer Documentation for API limits and rate limiting.