The built-in API cards
MCP — plug the assistant into Claude and other AI tools
MCP (the Model Context Protocol) is the open standard AI tools use to reach outside systems. Naxis Assistant speaks it natively: point Claude, Cursor or any other MCP client at this deployment and it can ask the assistant questions — every answer grounded in your documents, access-controlled and audited exactly like the web chat — and, with an ingestion key, push documents into the knowledge base. Same keys, same access rules, same audit trail as the two HTTP APIs; MCP adds a protocol, never a new capability.
The endpoint and the keys
Everything lives at one address: your deployment's base URL plus /mcp. The Bearer key decides what the connected tool can do, and there are two kinds to hand out: an ADMIN key can do everything — ask, add documents, and run the console — while a PERSONAL key only asks, with that person's own document access. Both live on the API & MCP page (left menu, under Settings), together with the exact connection lines to paste into your client. The underlying catalog cards (the API channel and the API source, each with its own card-level key) still exist for advanced setups and are created automatically the first time they are needed.
Connecting from Claude
Claude Code (terminal):
claude mcp add --transport http assistant \
https://YOUR-DEPLOYMENT/mcp \
--header "Authorization: Bearer nx_ak_YOURKEY"Claude.ai and Claude Desktop accept the same URL as a custom connector; Cursor and other clients take it in their MCP settings with the Authorization header. The server is stateless HTTP — no session set-up, nothing to keep alive.
What a Messaging key unlocks (asking)
| ask | The complete pipeline: the assistant investigates the knowledge base with the caller’s document access and returns a cited answer or an honest “not in the documents”. Returns a conversation_id for follow-ups. |
|---|---|
| search_knowledge_base | The assistant’s own search instrument: numbered source excerpts with document, date, kind and state — for a connected agent that wants to dig itself. |
| read_document | One document’s full text, paged — for contracts and anything where exact wording matters. |
| list_documents | The corpus map: document records filtered by name, date window and kind — timelines, “everything about X”, open-items sweeps. |
A person’s own key sees exactly what that person may see; the shared channel key sees the channel’s guest groups (none chosen = it stays silent). The three investigation tools respect the same access on every call — a connected tool can never surface a passage its key holder couldn’t open in the web chat.
What an Ingestion key unlocks (pushing)
| push_document | Create or replace a document (inline text, or base64 for PDF/DOCX); it indexes into that source with the groups you name (default: the source’s own). |
|---|---|
| get_document_status / list_pushed_documents | One pushed document’s indexing status, or the listing. |
| delete_document | Remove a document; purge=true erases it immediately, index included. |
| sync_now / ingestion_status | Trigger indexing; store and index counts. |
What an Admin key unlocks (everything)
An Admin API/MCP key is the everything key. It carries all the tools above — asking with the owning admin's own document access, pushing into the automatically-created API documents source — plus fifty-odd management tools covering people and groups, sources and channels, documents and access, settings, keys, the knowledge graph and the audit trail. Connect Claude — Cowork, Desktop or Code — with one admin key and simply say what you want: “create a finance group, add these five people, connect our Notion, and issue Maria her own key” — the assistant does it tool by tool, each step validated and audited like a console click.
The key is minted on the API & MCP page and acts with the minting admin's OWN authority: every action lands in the audit log under that admin plus the key's mark, and the key dies the moment the account is deactivated, demoted or deleted. The same key also authenticates the whole admin REST surface and the two data APIs (send it as Authorization: Bearer against /api/admin or /api/v1) for scripts that prefer plain HTTP. Personal keys never gain any of this — they stay ask-only.
Rate limits and audit are shared with the HTTP APIs (60 questions/min per caller, 300 pushes/min per source key, 120 admin calls/min per admin key), and every question, push and change lands in the same audit trail. Model and vendor identifiers never appear on the wire.
Last updated 29 Aug 2026