Skip to main content
NDI speaks Model Context Protocol, so an agent can call parse, extract, search, and the rest as tools. Hosted and local servers expose the same catalog. Prefer uvx ndi-mcp (or pip install ndi-mcp). The older ndi-sdk[mcp] extra still resolves to that package.

Hosted

Paste this into the agent’s MCP config. Mint the key on the API keys page; do not commit it.
The hosted server runs in our cloud, so it cannot see your filesystem. upload_document and upload_file refuse a local path there. Pass a public URL, or run the local server.

Local

ndi-mcp login opens the NDI console in your browser. Approve there; the CLI stores the minted key in ~/.ndi/config.toml. Pass --api-key (or set $NDI_API_KEY) to skip the browser. Cursor — add to .cursor/mcp.json:
opencode — add to opencode.json:
$NDI_API_KEY is read first; otherwise the key saved by ndi-mcp login. Local files go through upload_document, then parse_document / extract_data with the returned upload_id.

Tools

Same catalog on hosted and local. Names map to the Python SDK: Ask get_documentation with a topic (parse, extract, auth, workspaces, …) before writing integration code.

Next steps