Hosting

both

Transport

Not documented

Endpoint

https://mcp.nodit.io/mcp

Authentication

Preferred hosted connection uses OAuth: sign into a Nodit account with at least one RUNNING project and ACTIVE API key; API keys are retrieved server-side and should not be placed in the MCP URL or model context. The optional local server instead accepts NODIT_API_KEY in its environment. Current Nodit docs also describe x402 for API usage, but do not document it as this hosted MCP login flow.

Requirements

• For hosted MCP: Nodit account with at least one RUNNING project and one ACTIVE API key, plus a client supporting Streamable HTTP and OAuth
• For local mode: Node.js and npx plus a Nodit API key
• Multiple projects may require specifying a project ID for API calls

Setup steps

1. Preferred hosted setup: add https://mcp.nodit.io/mcp in a Streamable HTTP and OAuth-capable client, then sign into Nodit and approve the connection.
2. Claude Code: claude mcp add --transport http nodit https://mcp.nodit.io/mcp; sign in when the browser opens on first tool call.
3. For project-level Claude Code configuration, use a root .mcp.json entry with type http and url https://mcp.nodit.io/mcp.
4. To run locally instead, configure npx @noditlabs/nodit-mcp-server@latest and NODIT_API_KEY as an environment variable.
5. Verify with list_nodit_projects or list_nodit_api_categories. If multiple active projects exist, select one and pass its projectId to calls that require it.

Nodit’s current quickstart documents listing projects and API categories, retrieving specs, and calling APIs; the stored 10 identifiers include the documented Aptos Indexer counterparts. OAuth remote endpoint is https://mcp.nodit.io/mcp; calls can consume project compute units or use x402 where supported.

• list_nodit_projects

  List Nodit projects associated with the signed-in account.

  01
• list_nodit_api_categories

  List available API categories.

  02
• list_nodit_node_apis

  List Node API operations.

  03
• list_nodit_data_apis

  List Web3 Data API operations.

  04
• list_nodit_webhook_apis

  List Webhook API operations.

  05
• list_nodit_aptos_indexer_api_query_root

  List Aptos Indexer API operations.

  06
• get_nodit_api_spec

  Retrieve detailed specification for a Nodit API operation.

  07
• get_nodit_aptos_indexer_api_spec

  Retrieve detailed specification for an Aptos Indexer API operation.

  08
• call_nodit_api

  Call a Nodit API operation.

  09
• call_nodit_aptos_indexer_api

  Call an Aptos Indexer API operation.

  10

• Hosted access requires OAuth and an account project with an active key; the key is fetched by Nodit and is not passed in the MCP URL.
• When the account has multiple running projects, specify the intended project because API calls consume that project's quota.
• Local mode uses API-key environment authentication and exposes the key to the local process.
• Nodit docs recommend MCP for MCP clients and Skills for AI coding-agent workflows; these are distinct integration paths.
• No runtime connection test performed.

• official tool reference

  Nodit’s current quickstart documents listing projects and API categories, retrieving specs, and calling APIs; the stored 10 identifiers include the documented Aptos Indexer counterparts. OAuth remote endpoint is https://mcp.nodit.io/mcp; calls can consume project compute units or use x402 where supported.

• official documentation or source

  Nodit’s current quickstart documents listing projects and API categories, retrieving specs, and calling APIs; the stored 10 identifiers include the documented Aptos Indexer counterparts. OAuth remote endpoint is https://mcp.nodit.io/mcp; calls can consume project compute units or use x402 where supported.

Documentation checked 2026-10-28T14:15:00.000Z. Connection has not been runtime tested.