Summary
A catalogue read at runtime, instead of one tool per endpoint.
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.
What it is
A nine-tool front end to the Nodit Blockchain Context APIs, built as catalogue, specification and call rather than a tool per endpoint.
What you get
- list_nodit_api_categories is the required entry point, returning the categories the other API tools work from
- Operation lists split by surface: node APIs, data APIs and webhook APIs
- get_nodit_api_spec resolves one operationId into fully resolved spec details before you call it
- call_nodit_api issues the call with chain, network, operationId, path parameters, query parameters and a request body
- The Aptos Indexer GraphQL API gets its own route: query roots listed, one root's GraphQL specification fetched, then the query sent
Requirements
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.
Setup effort
One command plus a key — npx @noditlabs/nodit-mcp-server@latest, then supply credentials