MCP setup and governance

Nexus Rooms exposes a streamable MCP endpoint for external LLM agents. V1 uses scoped Nexus Rooms tokens rather than full MCP OAuth.

Endpoint

Use the public MCP endpoint shown in Nexus Rooms settings:

https://mcp.rooms.auroramind.fr/mcp

Generate one token per user and per LLM workspace. Tokens are shown once, hashed server-side and revocable.

Tools

• list_my_rooms
• list_rooms_requiring_attention
• describe_nexus_rooms_capabilities
• resolve_room
• get_room_context
• get_room_updates
• get_room_timeline
• list_room_documents
• get_document_text
• upload_room_text_document
• prepare_browser_document_upload
• create_room_document_upload
• append_room_document_upload_chunk
• commit_room_document_upload
• publish_validated_response
• request_human_validation
• notify_room_participants

Documents

Supported formats are txt, md, html, pdf, docx, xlsx and pptx.

Use upload_room_text_document for txt, md and html.

For pdf, docx, xlsx and pptx, the recommended workflow is now prepare_browser_document_upload:

1. Ask the agent to call describe_nexus_rooms_capabilities if it is unsure about supported formats.
2. Ask the agent to resolve the Room with resolve_room or pass a room_ref directly.
3. Ask the agent to call prepare_browser_document_upload with the Room reference and filename.
4. Open the returned Nexus Rooms upload URL in a browser.
5. Upload the original file outside the LLM conversation.
6. Wait for extraction, then read with list_room_documents and get_document_text.

room_ref can be the Room UUID, a public reference such as NXR-2026-0003, or an unambiguous Room title.

Chunked upload remains available for compatible MCP clients that can reliably compute and send binary chunks:

1. Compute the SHA-256 checksum and byte size.
2. Call create_room_document_upload.
3. Send ordered base64 chunks with append_room_document_upload_chunk.
4. Call commit_room_document_upload.
5. Wait for extraction, then read with list_room_documents and get_document_text.

Do not paste large binary files as base64 into the LLM when the client does not explicitly support robust blob transfer.

Notification behavior

publish_validated_response accepts a notification intent:

• none: publish without notifying.
• default: follow the Room notification settings.
• notify: request notification immediately in the specified channels.
• ask_user: publish and ask the user to confirm notification separately.

notify_room_participants remains available for explicit Room-scoped notifications. When channels are omitted, Nexus Rooms attempts email and SMS, then filters by preferences, configured Brevo integrations and available contact data.

The tool does not expose generic send_sms or send_email behavior.

ChatGPT

1. Open the ChatGPT connector or custom GPT configuration that supports remote MCP.
2. Add the Nexus Rooms MCP endpoint.
3. Paste the user token as bearer authentication.
4. Scan tools and confirm the tools listed above.
5. Ask the agent to list Rooms requiring attention before publishing anything.
6. For documents, use text upload for txt, md or html; use browser upload preparation for Office and PDF files.

Claude

1. Add Nexus Rooms as a remote MCP server where your Claude environment supports MCP connectors.
2. Use the same endpoint and bearer token model.
3. Verify that read tools and publish tools are visible.
4. Keep human validation mandatory before publish_validated_response.
5. Prefer browser upload preparation for binary files unless your Claude environment can send real blobs through MCP.

Gemini

1. Configure the MCP-compatible tool bridge available in your Gemini environment.
2. Register the Nexus Rooms MCP endpoint and token.
3. Map tool results as structured JSON, especially for Room references and upload URLs.
4. Test with list_my_rooms, then get_room_context.

Mistral

1. Configure a connector or tool bridge to the Nexus Rooms MCP endpoint.
2. Use a dedicated Nexus Rooms token for that Mistral workspace.
3. Verify read tools first, then test request_human_validation.
4. Enable notification tools only for agents allowed to request Room notifications.
5. Prefer room_ref references over raw UUIDs in user prompts.

Videos in help pages

Fumadocs pages can embed videos through MDX. Use a local component or an iframe for hosted videos. Keep videos as setup aids only; the MCP server and scoped tokens remain the source of access control.

Auditability

MCP calls enforce permissions and write audit logs. Recipient details are masked in traces.