Skip to content
Quigo
All posts

Quigo MCP: Build Training Modules from Claude, Cursor or Any MCP Client

Quigo now ships a Remote MCP server. Connect it once and your AI assistant can turn any PDF, deck, link or prompt into a branded, interactive training module and hand back a share link and a SCORM file.

Quigo Team ยท 5 min read

Key takeaways

  • Quigo MCP is a Remote Model Context Protocol server: any MCP client (Claude, Cursor, custom agents) can create Quigo Text and Video Modules without opening the Quigo app.
  • Five tools: create_module, module_status, list_modules, get_module and scorm_download. Sources can be raw text, a public URL or a base64 file (PDF, DOCX, PPTX, TXT up to 20 MB).
  • Authentication is standard OAuth 2.1 with PKCE. You sign in with your Quigo account (Google or email) and can revoke the connection from Connected Apps at any time.
  • Modules built through MCP land in your normal Quigo library with your last-used branding, full source citations and SCORM 1.2 export.
  • The connector is included in the Business plan.

Quigo MCP is a Remote Model Context Protocol (MCP) server that exposes Quigo's AI module maker as a set of tools your AI assistant can call. Connect it to Claude, Cursor or any MCP-compatible agent and you can say "turn this policy PDF into a compliance module" and receive a finished, branded, interactive module with a share link and a SCORM 1.2 package, without opening a browser tab.

What is MCP and why does it matter for L&D?

The Model Context Protocol is an open standard that lets AI assistants call external tools in a consistent way. Instead of copying content between ChatGPT, Claude and six SaaS tabs, the assistant calls the tool directly, gets structured results back and keeps working. For learning teams this is the difference between "AI wrote me a course outline" and "AI shipped a trackable module into my library while I reviewed the brief".

Most L&D work already happens next to an AI assistant: summarising SME documents, drafting objectives, rewriting questions. Quigo MCP closes the loop by making the production step callable too. The assistant that understands your source material can also build the module from it.

What can the Quigo MCP server do?

The server exposes five tools. Together they cover the full lifecycle of a module: create, wait, fetch, export.

  1. 1create_module: start a build. Choose kind="text" for an interactive Text Module (reading sections with quick checks, hotspots, sorting and scenario questions) or kind="video" for a narrated Video Module. Give one source: text, a public URL or a file. An optional title and brief steer the result.
  2. 2module_status: poll the job. Builds take one to five minutes depending on length; status reports the stage (reading, planning, building sections, illustrating) and progress.
  3. 3list_modules: see your recent modules with titles, kinds and links.
  4. 4get_module: fetch a module's share link, editor link, section list and SCORM URL.
  5. 5scorm_download: get a signed URL for the SCORM 1.2 zip so the agent can hand it to your LMS.

How do I connect Quigo MCP to Claude or Cursor?

  1. 1In your MCP client, add a remote server with the URL https: //quigo.tech/api/mcp. Claude calls these Connectors; Cursor and most agents accept a remote MCP URL in their config.
  2. 2The client discovers Quigo's OAuth metadata automatically and registers itself. You are redirected to a Quigo sign-in page. Use Google or your email and password.
  3. 3Approve the connection. Quigo issues a short-lived access token with PKCE; no API keys to paste or rotate.
  4. 4Ask your assistant to build something: "Create a Quigo text module from the attached onboarding deck, aimed at new warehouse staff, eight sections max."
  5. 5The assistant calls create_module, polls module_status and returns the share link. Open it in Quigo to review, edit or translate; the module behaves exactly like one created in the app.

To disconnect, open your account menu in Quigo, choose Connected Apps and revoke the client. The token stops working immediately.

What happens inside a module built through MCP?

The same production pipeline as the app. Quigo reads the entire document, not just the first pages, and builds a knowledge sheet of every fact, figure and rule. It plans sections against that sheet and runs a coverage check so nothing important is dropped. Each section is written with source citations that appear as chips in the editor and footnotes for learners. Diagrams, charts and pictures in the source are extracted and placed in the sections that discuss them; remaining visuals are generated to match the topic and judged for relevance before use.

Branding comes from your last module (colours, font, logo, narrator), so a batch of modules created by an agent looks like one coherent programme. Video Modules add an animated opener, narration in any of 90+ languages and captions.

Who should use the MCP connector?

  • L&D teams who already draft in Claude and want production in the same conversation.
  • Operations and compliance leads who need a module every time a policy changes, created from the change itself.
  • Agencies and consultancies producing modules for many clients, where an agent can batch dozens of sources overnight.
  • Developers building internal agents that watch a document repository and keep training current automatically.

Security and governance

Quigo MCP uses OAuth 2.1 with PKCE and dynamic client registration. Tokens are scoped to the signed-in user, inherit that user's plan and credits, and can be revoked at any time. Modules are owned by the user who authorised the connection and are subject to the same sharing controls as any other module. Uploaded files are stored in encrypted object storage, never in the database, and are only used to build the module you asked for.

Related terms and definitions

  • Model Context Protocol (MCP): an open standard for connecting AI assistants to external tools and data.
  • Remote MCP server: an MCP server reached over HTTPS rather than running on your machine, secured with OAuth.
  • OAuth 2.1 with PKCE: the authorisation flow Quigo uses so clients never see a password or static API key.
  • Dynamic client registration: how an MCP client introduces itself to Quigo before the first sign-in.
  • SCORM 1.2: the LMS packaging standard Quigo exports so completions and scores are tracked.
  • Connected Apps: the Quigo account page where you can see and revoke MCP clients.
Try Quigo free

Turn a file, URL, or idea into interactive training in minutes.

Get started

Frequently asked questions about Quigo MCP

What is Quigo MCP?
Quigo MCP is a Remote Model Context Protocol server that lets AI assistants such as Claude and Cursor create Quigo Text and Video Modules from text, links or files, check build status and download SCORM packages.
Which MCP clients work with Quigo?
Any client that supports remote MCP servers with OAuth, including Claude (web and desktop Connectors), Cursor and custom agents built on the official MCP SDKs.
Do I need an API key?
No. Authentication is OAuth 2.1 with PKCE. You sign in with your Quigo account using Google or email and password, approve the client once, and revoke it from Connected Apps whenever you like.
What file types can I send through MCP?
PDF, DOCX, PPTX and TXT up to 20 MB as base64, plus public URLs and Google Drive links, or plain text of at least ten characters.
How long does a module take to build?
Typically one to five minutes. Text Modules from long documents take longer because Quigo reads and cites the entire source; Video Modules add narration and animation time.
Does MCP output support SCORM?
Yes. scorm_download returns a SCORM 1.2 package for any completed module, ready for Moodle, Cornerstone, SuccessFactors, TalentLMS and other LMSs.
Which plan includes the MCP connector?
The Business plan. Credits used by MCP builds are the same credits used in the app.
Back to all posts