Common issues connecting an assistant to the Juno MCP server, and how to fix them.
Not connected, or stuck in a sign-in loop
- Confirm your workspace slug is correct ā itās your Juno subdomain (e.g.
acmeforacme.junojourney.com). - Make sure you have access to that workspace, then re-run the sign-in.
- Check the server URL:
https://mcp-prod.the-juno.com/mcp?workspace=<your-workspace>.
āThat isnāt availableā, or a tool is missing
The capability isnāt enabled for your account. Tools you arenāt permitted to use donāt appear to your assistant.- Check the MCP tool reference to see who gets that group of tools. For example, page design for the company academy needs an Admin or a Platform area admin, and learning data needs a Manager or Admin by default.
- Ask your Juno administrator to enable chat access for that capability.
- If an admin just enabled it, reconnect the Juno server so the new tools load.
- In the meantime, the same actions are available in the Juno web app.
The assistant canāt find the server
- Double-check the JSON is valid and placed under the config key your client expects. Most use
mcpServers, but VS Code usesservers. - Confirm the transport is set to
"type": "http"ā except in Cursor, which takesurlon its own, and Gemini CLI, which useshttpUrl. - In ChatGPT, keep the
/mcppath in the URL and check that an admin published the app.
I donāt see the AI assistant button in Juno
The button that opens a ready-made prompt, described in Start from inside Juno, may not be enabled for your organization.- If itās on, you see Do this with your AI assistant once youāve connected an assistant, and Connect your AI assistant if youāre a Manager or Admin who hasnāt.
- Learners who havenāt connected an assistant donāt see the button.
- In the + Create menu, the button shows only when you hover a row.
- Ask your Juno administrator whether itās turned on.
Wrong or missing content
- Content is scoped to your permissions ā you only see what your Juno role allows.
- Confirm you signed in to the intended workspace.