MCP SERVER · OFFICIAL PROJECTReach Nodit's blockchain node, data and webhook APIs by discovering the operation you need, reading its spec, then calling it — with a separate path for the Aptos Indexer GraphQL API.
LABSCO SUMMARY
Nine tools stand in for Nodit's whole API surface because the operations are treated as data: list categories, resolve an operationId to a spec, then call it. That keeps the tool definitions small however many endpoints Nodit adds, at the cost of two or three discovery calls before the one you actually wanted.
A nine-tool front end to the Nodit Blockchain Context APIs, built as catalogue, specification and call rather than a tool per endpoint.
NODIT_API_KEY. The two calling tools consume your Nodit API quota; the discovery and spec tools are what you use to avoid spending it on a malformed request.
One command plus a key — npx @noditlabs/nodit-mcp-server@latest, then supply credentials
USE CASES
Start at the categories, which the other API tools require first, narrow to the data API operations, resolve the operation you want into a full spec, then make the call with the chain, network and parameters that spec names.
The webhook surface is discovered the same way as the rest: list its operations, read the spec for the one that registers a subscription so the request body is right first time, then send it.
The Aptos Indexer is GraphQL, so it gets its own route: list the query roots, fetch the GraphQL specification for the root you need, and send the query against a network.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
call_nodit_apiThis function calls a specific Nodit Blockchain Context API using its operationId. Before making the call, it's recommended to verify the detailed API specifications using the 'get_nodit_api_spec' tool. Please note that using this tool will consume your API quota.
call_nodit_aptos_indexer_apiCalls a Nodit Aptos Indexer API. Returns the API response. Before making the call, it's recommended to verify the detailed API specifications using the 'get_nodit_aptos_indexer_api_spec' tool. Please note that using this tool will consume your API quota.
get_nodit_api_specGets the fully resolved spec details for a Nodit Blockchain Context API operationId. Returns details as a JSON string.
get_nodit_aptos_indexer_api_specReturns the GraphQL specification for a specific query root in the Nodit Aptos Indexer API.
list_nodit_api_categoriesLists available Nodit API categories from Nodit Blockchain Context. To use the Nodit API tool, you must first call this tool.
list_nodit_aptos_indexer_api_query_rootLists all query roots available in the Nodit Aptos Indexer GraphQL API.
list_nodit_data_apisLists available Nodit Data API operations.
list_nodit_node_apisLists available Nodit API operations.
list_nodit_webhook_apisLists available Nodit Webhook API operations.
BEFORE YOU INSTALL
9 tools when we connected. Most of the surface is reached through call_nodit_api with an operationId, including writes such as transaction submission and webhook creation. A hosted SSE endpoint is also documented at https://mcp.nodit.io/sse.
CONTEXT COST
Rated by the size of the 9 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
npx @noditlabs/nodit-mcp-server@latest{
"mcpServers": {
"nodit": {
"command": "npx",
"args": [
"@noditlabs/nodit-mcp-server@latest"
],
"env": {
"NODIT_API_KEY": "<YOUR_NODIT_API_KEY>"
}
}
}
}~/.cursor/mcp.json
{
"mcpServers": {
"nodit": {
"command": "npx",
"args": [
"@noditlabs/nodit-mcp-server@latest"
],
"env": {
"NODIT_API_KEY": "<YOUR_NODIT_API_KEY>"
}
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json
claude mcp add nodit-mcp-server npx @noditlabs/nodit-mcp-server
export NODIT_API_KEY=<YOUR_NODIT_API_KEY>
claude{
"mcpServers": {
"nodit": {
"url": "https://mcp.nodit.io/sse?apiKey=<YOUR_API_KEY>"
}
}
}MCP servers
subsquid-labs
fengshanshan
boray
nirholas