The Juno MCP server is built for enterprise use: OAuth 2.1 sign-in, revocable access tokens for automation, and access that never exceeds your existing Juno permissions.
Authentication
The server uses OAuth 2.1 with dynamic client registration. When your assistant first connects, a browser window opens to sign in to your Juno workspace and authorize access. Juno issues a scoped, refreshable token to that client.- Every connection acts as a specific Juno user — there are no shared service accounts.
- The authorization consent screen shows the requesting application’s name, so you know what you’re connecting.
- You can revoke a connection at any time from your MCP client.
Access tokens
For CI jobs and scripts that can’t open a browser, Admins with the IT Admin role can create an MCP access token instead of signing in. A token acts as the Admin who created it, works only with the MCP server — the Juno REST API rejects it — and is valid for 365 days. Any Admin with the IT Admin role can revoke a token, and revocation takes effect immediately. See Access tokens.Permission inheritance
Access is granted only to the data and actions your Juno role already permits. Connecting over MCP does not open up new categories of data — it makes the content and actions you already have easier to reach from an assistant.- Everything is scoped to your workspace.
- Which capabilities are available depends on your plan and admin settings. Tools you aren’t permitted to use simply don’t appear to your assistant.
- If an admin enables a capability mid-session, reconnect the server for the new tools to appear.
Admin controls
What your assistant can do depends on your Juno role, your organization’s modules, and a few admin settings.- Authoring, publishing, and interactive lessons — no separate admin setting. These tools need the Learning module and follow your own Juno permissions.
- Channel page design — available to anyone who can create channels, and only for channels they admin.
- Company academy and LXP catalog pages — available to Admins, and to anyone with admin access in the Platform area. The LXP catalog page also needs the LXP module.
- Learning data — on for Managers and Admins by default. Learners don’t see these tools. Results follow your role, and organization-wide numbers need an Admin.
- Management, company context, guided onboarding, and public academy pages — assigning and notifying learners, channel library changes, company context, the guided first-run flow, and public academy page tools may not be enabled for your organization.