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.- 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). - Confirm the transport is set to
"type": "http".
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.