Adding Junior to an AI client is usually a one-time job for your IT administrator. Where the client supports workspace deployment, an admin can add it for everyone. Each person then signs in with their own Junior account.
Before you start
Your organization needs MCP access enabled by the Junior team. Contact your Junior representative to arrange this; there isn't a self-serve signup.
Enabling the connector doesn't give anyone new access. Each person can reach only the projects and calls they can already open in Junior.
Connector URL
Use this URL in your AI client's connector settings:
https://api.junior.ai/mcp
The URL is the same for every organization. At sign-in, enter the work email you use for Junior and you'll be routed to your workspace.
Claude web and desktop
- Open Settings → Connectors → Add custom connector.
- Paste the connector URL.
- Approve the Junior sign-in.
Workspace admins can deploy the connector for the whole organization so users don't need to add it individually.
Claude Code
Add the connector from your terminal:
claude mcp add --transport http junior https://api.junior.ai/mcp
Then run /mcp in Claude Code to sign in.
Codex CLI, desktop, and IDE
In a trusted project's .codex/config.toml or in ~/.codex/config.toml:
- Add a section named
[mcp_servers.junior]. - On the next line, set
url = "https://api.junior.ai/mcp".
Restart the client, then authenticate:
- CLI: run
codex mcp login junior. - Desktop or IDE: select Authenticate in the MCP settings.
Use /mcp to check the active connection.
Microsoft Copilot Studio
A maker adds Junior to an agent once. Each person using that agent then signs in to Junior with their own account.
If your tenant uses a sovereign cloud — GCC, GCC High, DoD, or China — tell your Junior representative before setup. Junior accepts the commercial-cloud callback by default; sovereign clouds use a different consent host that needs to be allowed.
Add Junior to an agent
- Open your agent and go to Tools → Add a tool → New tool → Model Context Protocol.
- Enter a Server name and Server description. The description helps the agent decide when to use Junior.
- Set Server URL to
https://api.junior.ai/mcp. - Choose OAuth 2.0 with type Dynamic discovery. Junior supports dynamic client registration and discovery, so Copilot Studio finds the sign-in endpoints automatically.
- Select Create, then Create a new connection and Add to agent.
- Publish the agent when you're ready to share it.
Sign in on first use
The first time someone uses a Junior tool, Copilot Studio asks them to create a connection. They approve the sign-in with their own Junior account and can access only their own projects and calls.
Other MCP clients
Junior supports streamable HTTP with OAuth 2.1, including dynamic client registration, PKCE, and RFC 8707 resource indicators. Point a compatible client at the connector URL and let it discover the authorization server.
Access and security
- Each person signs in separately: there isn't a shared credential or API key to distribute. Deactivating a Junior account removes that person's access.
- Access follows Junior's permissions: tools return only projects, calls, and entities the user can already open. New calls can be added to a project they belong to, or left unfiled for assignment later.
- Existing content can't be changed or deleted: five tools read data. The sixth,
ingest_call, adds a new call and transcript and requires the separatecalls:writescope. Declining that scope keeps the connection read-only. - Tokens are tied to one organization: a signed organization claim is fixed at sign-in, and every query is filtered to that organization on the server. Tokens are also bound to the connector URL they were issued for, preventing reuse against a different Junior endpoint.
- Credentials expire and rotate: access tokens expire after 60 minutes. Refresh tokens rotate on each use; reusing a retired refresh token revokes the whole token family.
- Your organization can revoke access: Junior can suspend MCP access for your organization, taking effect within one request without waiting for tokens to expire.
- Traffic uses HTTPS: connector requests go to
api.junior.ai. Claude's web and desktop clients connect from Anthropic's infrastructure, so adding the connector doesn't need a firewall change on your side.
If your security review requires an OAuth audience scoped to your workspace, ask your Junior representative about a per-workspace URL: https://api.junior.ai/mcp/<your-subdomain>.
Permissions
Each user approves the requested scopes when signing in.
| Scope | What it allows |
|---|---|
projects:read | List your projects and read their metadata. |
calls:read | Read your call records, summaries, and other call content. |
entities:read | Read companies, products, and other entities recognized in your calls. |
calls:write | Add new calls and transcripts. It can't change or delete existing content. |
Clients that offer call ingestion request calls:write separately. An existing read-only connection keeps working as before unless you reconnect and approve that scope.
Questions
Sign-in says MCP not enabled
Your organization hasn't been enabled yet. Contact your Junior representative.
Why are no tools showing?
Your client may have cached an older tool list. Disconnect and reconnect the connector to refresh it. Junior versions its tools so clients can detect changes.
Missing team calls?
Call lists default to calls you created. Ask for calls across the whole
team to widen the search to everything you can access. This uses
scope="all" on
list_calls; it doesn't
change your permissions.
Incomplete answers?
Full transcripts can exceed your assistant's context limit, and a response may cover only part of the project. Ask which calls it read, narrow the selection, or start with summaries and Key Takeaways. The tool reference explains pagination and response limits. There's no keyword or semantic search across transcript text; see What stays in Junior for the other limitations.