Skip to main content
Connect your favorite AI assistant — Claude, ChatGPT, and more — directly to your Juno workspace, so it can find your learning content and help you build and run training, all scoped to your own Juno permissions.

What is the Juno MCP server?

The official MCP server for Juno Journey lets your AI assistant work the full learning loop: search and reuse existing content, turn source material into courses, quizzes, surveys, and journeys — or gamified lessons built for you (games, simulations, branching scenarios) — then publish and assign them to the right people, with deadlines and reminders that drive completion. The Model Context Protocol (MCP) is an open standard that lets AI assistants securely connect to outside tools and data. Juno runs a hosted MCP server, so any MCP-compatible assistant can work with your workspace in a conversation — no copy-pasting, no API keys to manage. You sign in once with your Juno account, and the assistant can only ever see and do what your Juno role already allows.

What you can do

  • Find and reuse content — search your Juno library and external learning sources.
  • Author learning — plan and create courses, quizzes, surveys, and multi-course journeys.
  • Build interactive lessons — gamified, interactive HTML lessons, or import a SCORM package.
  • Run a program — publish content, target an audience, and notify learners.
What each assistant can do depends on your Juno plan and admin settings. Your client discovers the exact set of tools available to you automatically when it connects.

Connect in under a minute

Point your assistant at the Juno MCP server:
Replace <your-workspace> with your Juno subdomain — for acme.junojourney.com, use acme. On first use, a browser window opens to sign in to Juno and authorize access.

Choose your assistant

Claude

Add Juno as a custom connector in Claude — desktop, claude.ai, or Cowork.

ChatGPT

Add Juno as a connector in ChatGPT settings.

Cursor

Add Juno to your Cursor MCP configuration.

Other clients

Gemini Enterprise and any other MCP-compatible client.

Security in brief

The connection uses OAuth 2.1 — you sign in with your Juno account and the assistant acts only within your existing permissions. There are no shared credentials or API keys. See Security & permissions for the full picture.
Last modified on July 26, 2026