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_apisB | Lists available Nodit API operations. |
| list_nodit_data_apisA | Lists available Nodit Data API operations. |
| list_nodit_webhook_apisA | 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_specA | Returns the GraphQL specification for a specific query root in the Nodit Aptos Indexer API. |
| call_nodit_aptos_indexer_apiA | Calls 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_specA | Gets the fully resolved spec details for a Nodit Blockchain Context API operationId. Returns details as a JSON string. |
| call_nodit_apiA | This 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. |
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 9 tools
Each tool has a clearly distinct purpose: two call tools target different APIs, two spec tools provide details for those APIs, and five listing tools enumerate different categories of API operations. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern using snake_case, with verbs like call, get, and list, and nouns specifying the API type (e.g., nodit_api, nodit_aptos_indexer_api). No mixing of conventions.
With 9 tools, the set is well-scoped for a server that provides access to multiple Nodit APIs and their metadata. Each tool earns its place, covering both discovery and execution.
The tool surface covers the full workflow: listing available APIs, getting specifications, and making calls. There are no obvious gaps for the stated domain of interacting with Nodit blockchain APIs.