MCP for Claude
Connect Claude to your Niravi video corpus. Once added, Claude can search, recall, chat, and read every analysis on your videos — as native tools. Built on the Model Context Protocol; the tools are generated from the same OpenAPI spec as the SDKs, so they always track the API. Read-only.
Two ways to add it
| Remote connector | Local (stdio) | |
|---|---|---|
| Works in | Claude web · desktop · mobile | Claude Desktop only |
| Setup | paste a URL | edit a config file |
| Requires | nothing | Node.js installed |
| Best for | most people | local/offline, advanced |
Both expose the same 24 read-only tools, scoped to the workspaces your API key can reach.
Step 1 · Get an API key
Go to app.niravi.io → Settings → API access →
Create key → set scope to Read → copy the nv_… secret (it’s shown once).
Use a dedicated read-only key for Claude — you can revoke it any time from the same page.
Step 2 · Option A — Remote connector (recommended)
In Claude: Settings → Connectors → Add custom connector, then fill in:
| Field | What to enter |
|---|---|
| Name | Niravi |
| Remote MCP server URL | the URL below (with your key) |
| OAuth Client ID (advanced — optional) | leave blank |
| OAuth Client Secret (advanced — optional) | leave blank |
Copy this into the Remote MCP server URL field, replacing nv_YOUR_KEY_HERE:
https://mcp.niravi.io/?key=nv_YOUR_KEY_HERE
Click Add — the Niravi tools appear.
Why the key is in the URL: the connector dialog has no separate key field, so the key rides on the URL. Leave the OAuth fields empty (Niravi doesn’t use OAuth yet). Always use a read-only key here.
Point it at a specific workspace (optional) — append &workspace=<id>. Your key defaults
to its home workspace; account-scoped keys can target any workspace you belong to, or a demo:
https://mcp.niravi.io/?key=nv_YOUR_KEY&workspace=demo_content
Step 2 · Option B — Local (Claude Desktop)
Claude Desktop → Settings → Developer → Edit Config, and add:
{
"mcpServers": {
"niravi": {
"command": "npx",
"args": ["-y", "@niravi-io/mcp"],
"env": { "NIRAVI_API_KEY": "nv_YOUR_KEY_HERE" }
}
}
}
Save and restart Claude Desktop. (Requires Node.js; the @niravi-io/mcp
package is fetched automatically by npx.)
Try it
Ask Claude things like:
- “Search my Niravi videos for a sunset over water.”
- “What does video X say about pricing?”
- “Summarize the speakers and topics in my latest upload.”
The tools (24, read-only)
Search — search (pass workspace_ids to search several workspaces at once — hits merge
into one ranked list, each tagged with its workspace_id), magic_search (character / location
/ music / emotion) ·
Chat & recall — chat, recall_ask, recall_evidence ·
Videos — list_videos, get_video ·
Analysis — transcript, scenes, shots, faces, characters, speakers, sounds,
sound_events, audio_segments, music_tracks ·
Exports — screenplay, storyboard, subtitles_srt, subtitles_vtt ·
Account — list_workspaces (what the key can reach), me, health.
Every call is scoped to the workspaces your key can reach. Writes (upload/delete) are intentionally excluded.
Troubleshooting
- No tools show up → check the URL has
?key=nv_…and the key is active (Settings → API access). - “No API key” in a tool result → the
?key=is missing or empty. - A search times out → rare; searches can be slow on a cold corpus. Retry.
Links
- Get a key → app.niravi.io/settings/developer
- Packages →
@niravi-io/mcp·@niravi-io/sdk(npm) - Source → github.com/Niravi-io/niravi-sdk
- API reference → /reference · SDKs → Python · TypeScript