Juno Journey is a talent development platform that combines an LMS, an on-demand learning catalog, goals, events, and an AI assistant.
Agen.co connects to Juno Journey through Juno's own hosted MCP server as an Official connector. Each user signs in with their own Juno account, and every action runs with that account's existing role and permissions. There is no OAuth client ID or secret to create, and nothing to register on the Juno side.
Prerequisites
Prerequisites
- A Juno Journey account for each person whose agents will use the connector.
- Your Juno workspace name — the subdomain you sign in to. For
acme.junojourney.com, the workspace isacme.
- In the Agen.co portal, go to Connectors → My connectors and click Add connector.
- In the Select connector drawer, search for
Junoand select Juno Journey. The Add Juno Journey panel opens. - Fill in the fields:
| Field | Required | Description |
|---|---|---|
| Instance Slug | Yes | Namespaces this instance — it prefixes each imported tool as slug__tool, so several instances of the same MCP can coexist. Prefilled with junojourney. Use lowercase kebab-case. You can change it later from the connector's settings. |
| Juno workspace | Yes | Your Juno subdomain — for acme.junojourney.com, use acme. |
- Click Connect. Juno opens in a new tab, and the panel shows Waiting for authorization — complete it in the opened tab…
- Sign in to Juno with your own account and approve access.
- Back in Agen.co, the panel switches to Select the tools to import from Juno Journey. Every tool is toggled on; turn off any you don't want to import, then click Add.
The connector is created and its tools imported only when you click Add. If you close the panel before that, nothing is saved, even if the Juno tab reported success.
Each connector instance connects to exactly one Juno workspace. To connect a second workspace, add Juno Journey again with its own Instance Slug and Juno workspace.
Juno decides which tools each user gets from that user's role, the modules enabled for the organization, and admin settings. Tools a user is not permitted to use are not offered at all. According to Juno's MCP documentation (checked 2026-10-08):
| Area | What it covers |
|---|---|
| Search and read | Search the Juno library and read a unit's full text |
| Courses, quizzes, and Journeys | Plan, create, edit, and publish courses, quizzes, surveys, and Journeys |
| Interactive lessons | Build, preview, and version HTML lessons |
| Pages | Design channel, company academy, and catalog pages |
| Learning data | Query learning activity and dashboards (Managers and Admins by default) |
Changes to a course, quiz, or survey are saved as a draft and stay invisible to learners until published. Some groups, such as assigning and notifying learners, may not be enabled for your organization, and Juno does not publish a fixed tool list. The tool selection screen after Connect shows exactly what your account serves. If an admin enables a capability later, disconnect and reconnect so the new tools load.
Enabling the Juno Journey connector isn't enough on its own. Tool calls remain denied until you create a policy that grants access to the specific tools you want to expose.