Nodit MCP
Connect your AI agent to on-chain data
Your AI client finds and calls Nodit APIs as tools to get live chain state and indexed history.
SEE IT IN ACTION
From a Question to a Real API Call
Ask in plain language
Describe the on-chain data you need.
Find the right API
Your agent finds a matching Nodit API and checks how to call it.
Call the API
It sends the request through Nodit MCP.
Use the result
It uses the returned data in its answer or workflow.
WHAT YOU CAN ASK
Ask for On-Chain Data in Plain Language
Your agent can discover Nodit API specifications, call supported Node APIs and Data APIs, and organize the returned on-chain data for its response or workflow.
Example Prompt
Use Nodit to get the latest block on Ethereum Mainnet.Return the block number, block hash, timestamp, and transaction count.
CONNECT
Connect Remotely or Run It Locally
Use Nodit’s hosted server, or run the published MCP package in your own environment.
# Nodit-hosted MCP serverhttps://mcp.nodit.io/sse?apiKey={YOUR_API_KEY}
CONNECTION DETAILS
Clients, Keys, and Coverage
- Compatibility
- Claude Desktop · Cursor · other MCP-compatible clients
- Authentication
- Both Remote MCP and Local MCP require a Nodit API Key
- Available APIs
- Supported operations from Node API, Data API, Webhook API, and Aptos Indexer API
- Chain coverage
- API availability varies by chain and network.See supported chains and APIs
- Listing
- Official on Glama.aiView on Glama
- Source
- github.com/noditlabs/nodit-mcp-serverView on GitHub
FAQ
Use Remote MCP to avoid running a local server. Use Local MCP if your client needs a local server or you want to manage the runtime yourself. Both require a Nodit API Key. See the setup guide for your client.
Connect Nodit MCP to your AI client
Follow the setup guide, then try a prompt in your AI client.