Reads only
glimmer_prepareglimmer_arrivalsglimmer_gardenglimmer_account_statusglimmer_export
Free · adults only · one recipient
Connect Numen to a compatible personal AI chat. 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.
Life happens everywhere
These scenes show what a connected chat can carry. Every real release begins with the participant's own moment and confirmation.








About one minute
One address. No API key. It works inside the chat you already pay for.
Numen is not tied to one AI company. Choose where it suits you to talk to it — Numen never checks which chat that is, and never asks for the API key of any provider.
Numen stays the same layer of your life. The chat is only the door, and the model behind it can change without losing a single moment.
Your Numen MCP addresshttps://relay.numenhuman.space/mcp
Sign in to your Numen account and review the exact permissions requested. You can deny or revoke access.
Say “make this a Numen moment.” The assistant can prepare it; only you perform the final release, resonance, reply or report.
See what happens nextNothing here is developer work. You are adding one address to your chat, once, the way you would add an account to a mail app.
A door between your chat and one service. Your chat learns a few new actions — prepare a moment, show arrivals — and nothing else. It is not an app to install and not a subscription to buy.
Each company put the setting in its own place and calls it its own name: Connectors, MCP servers, Tools. The address is always the same one; only the path to the field changes. Pick your chat above and the exact path appears.
After you paste the address, a browser window opens once and asks you to sign in to Numen and approve. That window is the whole setup. If nothing opens, the address or the transport is wrong — the questions below cover it.
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 below. 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.