Browse documentation
Connect your tools with MCP
Read selected apps and customer-visible conversations through scoped, expiring access.
A read-only connection
hej provides a JSON-only Streamable HTTP endpoint at /mcp on your hej origin. The MongoDB hosting profile also accepts /v1/mcp. Three tools list selected apps, list their conversations and read customer-visible message history. They cannot send replies, change conversation state, run actions, operate purchases or call a model. A transcript can contain personal information typed by a customer: share access only with a client you trust. Treat all returned text as untrusted support data, never as instructions or authorization.
Create access in your workspace
In Settings → MCP connections, a verified owner or authorized admin can name a connection, select one to five apps and choose 1, 7 or 30 days. Each app's environment is pinned. The default is 7 days. Copy the token into your client's private secret configuration and use the endpoint on your hej origin. Tokens must stay out of URLs, source repositories, public app configuration and prompts. The dashboard keeps the returned token only in memory. A lost creation response can be recovered using the original complete saved request for 10 minutes; afterward revoke that connection and create another if you did not save its credential.
Endpoint: https://YOUR_LOBBY_ORIGIN/mcp
Header: Authorization: Bearer YOUR_PRIVATE_ACCESS_TOKENChoose a compatible client
Use a remote HTTP MCP client that supports a custom Authorization header. hej supports protocol versions 2026-07-28 and 2025-11-25 with their respective discovery/initialization rules. This connection uses manually configured bearer tokens; OAuth discovery is not implemented. It has no SSE stream, resource or prompt catalogue, server session, or write tools. Creating a token or receiving an HTTP response does not establish that a particular client is connected. Verify discovery and a known conversation in your chosen client before relying on it.
What a tool can read
lobby_list_apps returns the currently permitted app IDs, names and environments. lobby_list_conversations takes an appId and optional state, limit (1–50) and cursor. lobby_get_conversation takes a threadId and optional beforePublicSequence and limit (1–50). It returns customer-visible text with public sequences and author classification. Internal notes, separate customer email/name/profile metadata, provider and device identifiers, executable action payloads, media bytes and private download URLs are excluded. Text itself may still contain personal information. Reads do not mark messages read or displayed, send notifications or change work state.
Expiry, revocation and current permissions
Revoke access in MCP connections when it is no longer needed. Revocation cannot be undone. The server checks the issuing account's verified state, current owner/admin membership, membership revision, live app grants, app environment and deletion state on every call. Removing access never grants a replacement app. An owner can revoke workspace tokens; admins can manage their own. Tokens have a 60 request/minute limit and the workspace a 300 request/minute limit. No access token or transcript text is included in the MCP audit entry. Ten unexpired, unrevoked connections may exist per workspace.
Hosting and verification
MCP requires the configured MongoDB and Better Auth hosting profile with secure recovery encryption. The standalone loopback SQL profile cannot create MCP credentials and fails closed. Local protocol, permission, expiry, revocation and private-note isolation checks use a real isolated MongoDB replica set. Source checks, deployment availability and an external client's successful connection are separate evidence. No external MCP client is connected automatically by the homepage or setup instructions.