How you authenticate depends on your client:
- Claude connector — sign in when you connect. Your organization’s Jedify login page opens; sign in and return to Claude. Sessions refresh automatically.
- Local clients (Claude Desktop, Cursor, Claude Code running the
@jedify/mcp-auth proxy) — sign in when prompted. The first time you use a Jedify tool, your browser opens to your organization’s login page; sign in and return to your client. Sessions refresh automatically.
- Hosted agents and apps, and any headless or shared setup — use an API key.
A finished app or dashboard always uses an API key, since no one is present to sign in.
API keys
Create one in Jedify under Settings → API Keys: give it a name and, optionally, an expiry. The key is shown once — copy it then. Paste it into your platform’s API key (or token) field, or into JEDIFY_API_KEY for the local proxy (see Connect). Treat it like a password.
The key is bound to you — it carries your identity and permissions. Anyone can create keys for themselves; administrators can also see and revoke every key in the account.
Tools you get when you sign in. Signing in needs no mode setting — the server returns the tools your role in Jedify allows: Tenant Admins and Data experts get Asker, Editor, and Builder; Users get Asker.
Tools you get with an API key. A key created in the app runs in Asker mode regardless of your role. To use Editor or Builder tools with a key, select the mode in the server URL (?mode=editor or ?mode=builder) — REMOTE_MCP_URL for the local proxy, the server URL for a hosted agent. See Authenticate with an API key.
A published app uses one API key for everyone who opens it, so every viewer sees data at that key’s permission level — not their own. For sensitive data (HR, finance), use a key whose access matches what all viewers should see.
Security
- All traffic uses HTTPS.
- Access is scoped to the key’s (or signed-in user’s) permissions.
- Sign-in sessions refresh and expire automatically.
- Keys can be created with an expiry, and deactivated or revoked at any time under Settings → API Keys.
