Nodit MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODIT_API_KEY | Yes | Your Nodit API key (Sign up and get an API key at Nodit Console) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_nodit_api_categoriesA | Lists available Nodit API categories from Nodit Blockchain Context. To use the Nodit API tool, you must first call this tool. |
| list_nodit_node_apisC | Lists available Nodit API operations. |
| list_nodit_data_apisC | Lists available Nodit Data API operations. |
| list_nodit_webhook_apisC | Lists available Nodit Webhook API operations. |
| list_nodit_aptos_indexer_api_query_rootA | Lists all query roots available in the Nodit Aptos Indexer GraphQL API. |
| get_nodit_aptos_indexer_api_specB | Returns the GraphQL specification for a specific query root in the Nodit Aptos Indexer API. |
| call_nodit_aptos_indexer_apiA | Calls a GraphQL query from the Nodit Aptos Indexer API category — the query roots listed by 'list_nodit_aptos_indexer_api_query_root'. 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. API reference: https://developer.nodit.io/api/api-overview. Please note that using this tool will consume your API quota. |
| get_nodit_api_specB | Gets the fully resolved spec details for a Nodit Blockchain Context API operationId. Returns details as a JSON string. |
| call_nodit_apiA | Calls an operation from the Nodit Node API or Nodit Data API categories — the operations listed by 'list_nodit_node_apis' and 'list_nodit_data_apis', whose target chain and network go in the URL. Nodit Webhook API operations cannot be invoked with this tool. Before making the call, it's recommended to verify the detailed API specifications using the 'get_nodit_api_spec' tool. API reference: https://developer.nodit.io/api/api-overview. Please note that using this tool will consume your API quota. |
| list_nodit_multichain_apisA | Lists available Nodit Multichain API operations. Each one addresses several chains in a single request and names them inside the request body. |
| call_nodit_multichain_apiA | Calls an operation from the Nodit Multichain API category — the operations listed by 'list_nodit_multichain_apis'. These operations address several chains in one request and name them inside the request body rather than in the URL. Verify the request body shape with 'get_nodit_api_spec' before making the call. Please note that using this tool will consume your API quota. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
There are five listing tools (node, data, webhook, multichain, categories, aptos query roots) that all sound like 'list operations,' and the boundary between list_nodit_node_apis/data_apis/multichain_apis is only clarified by reading descriptions closely. call_nodit_api vs call_nodit_multichain_api vs call_nodit_aptos_indexer_api are distinguishable by target API family, but an agent may frequently pick the wrong list tool first.
Names follow a clear verb_nodit_noun pattern across list/get/call with snake_case throughout. The aptos indexer tools introduce longer variants (list_nodit_aptos_indexer_api_query_root) and 'query_root' rather than '_apis', a minor deviation from the otherwise uniform convention.
11 tools is well within a reasonable scope and each listing spec/calling group earns its place in a discover-then-invoke workflow. The set is neither bloated nor thin for a multi-category API gateway.
Discovery (categories, operations, specs) and invocation are covered for Node, Data, Multichain, and Aptos Indexer APIs, but Webhook APIs can be listed yet explicitly cannot be invoked by any tool — a real dead end. There is also no generic spec-getter path described for the Aptos query roots other than the dedicated one, leaving an inconsistent lifecycle.