MCP and CLI login - NDI Platform API

NDI speaks Model Context Protocol. Hosted and local servers expose the same tool catalog. Prefer uvx ndi-mcp. The terminal CLI is a separate package: pip install ndi-cli, then ndi login. See NDI CLI for parse, extract, workspaces, and search from the shell.

Hosted

{
  "mcpServers": {
    "ndi": {
      "type": "http",
      "url": "https://ndi-api.nace.ai/v1/mcp",
      "headers": { "X-API-Key": "ndi_sk_..." }
    }
  }
}

The hosted server cannot see your filesystem. Pass a public URL, or run local.

Local CLI

uvx ndi-mcp login
claude mcp add ndi -- uvx ndi-mcp

ndi-mcp login opens the console, then stores the minted key in ~/.ndi/config.toml. --api-key or $NDI_API_KEY skips the browser. Device-code routes (what the CLI uses):

POST /v1/cli/device/code
POST /v1/cli/device/token

Do not call these from application code — use an API key. Cursor — .cursor/mcp.json:

{
  "mcpServers": {
    "ndi": {
      "command": "uvx",
      "args": ["ndi-mcp"]
    }
  }
}

Tool names map 1:1 to the Python SDK (parse_document → client.documents.parse). Ask get_documentation with a topic before writing integration code. See MCP.