Add the address
Paste it into your chat's connector settings. The client discovers Numen's secure sign-in on its own.
Numen in your AI chat
Numen lives behind one address. Any chat that speaks MCP can open it. Your chat performs the safety review, voice transcription and translation under your own subscription; Numen only organizes and routes what you confirm. It cannot send or reply without your confirmation.
https://relay.numenhuman.space/mcpPaste it into your chat's connector settings. The client discovers Numen's secure sign-in on its own.
Sign in to your Numen account and read the exact permissions requested. You can deny or revoke at any moment.
Say “make this a Numen moment.” The assistant may prepare it; only you release, resonate, reply or report.
The same address, a different door. Pick the client you already use.
Setup · Address field
Open Settings → Connectors → Add custom connector in Claude — app and web.
Paste the Numen address and choose the Streamable HTTP transport.
https://relay.numenhuman.space/mcpSign in to Numen in the window that opens and approve the exact access.
Ten tools and three resources. Nothing else is exposed.
glimmer_prepareglimmer_arrivalsglimmer_gardenglimmer_account_statusglimmer_exportglimmer_releaseglimmer_resonateglimmer_let_passglimmer_replyglimmer_report_and_blockglimmer://guideglimmer://safetyglimmer://gardenCheck that the address ends with /mcp and that the transport is Streamable HTTP, not SSE. Then remove the connector and add it again so the sign-in runs from the start.
Numen has no API keys. It only uses a browser sign-in. Leave any key field empty and choose OAuth, or “authenticate in browser”.
Use the local bridge command. It runs on your machine and forwards to the same address; your account stays with Numen.
Remove the connection in your chat and revoke the client in your Numen account. The very next call from that client returns 401.