Console
Access & MCP
API keys for the /ask API, and connecting external MCP clients.
How applications and external AI clients get access to a project.
API Keys
The project's SDK credentials (egox_live_*) used to call the /ask API
from your own backend. Create keys (with a name, scopes, and expiry), rotate them safely
(no-overlap warning), and revoke them. A newly created or rotated key's secret is shown
once, at that moment, with an environment snippet to copy.
MCP
MCP lets external AI clients (such as coding assistants) connect to a project and use its tools and knowledge base.
- Connections — the main MCP screen: connect an agent via SSO (the primary, no-token path), see which agents are currently connected, and review recent connection activity.
- Authorization — the consent screen shown when an outside client requests to connect; the user picks which project to grant, then approves or denies. A connection is always scoped to a single project.
- Troubleshooting — a reference guide for connecting a client and fixing common issues.
Connecting is SSO-first; manual connection tokens exist as a fallback and are managed alongside the project's API keys.