Connect via MCP
How to connect an assistant such as Claude to your workspace, what it can do once connected, and which AI actually builds the course.
Create a connection in your workspace settings, add the connection URL to your assistant, and sign in once to authorise it. From then on the assistant can create and manage courses in that workspace, using over 50 tools. Course generation itself runs on Coassemble's own AI, so a course built through your assistant behaves the same as one you build in the app.
Building through an assistant needs a plan that includes the Coassemble agent. On the legacy Flow plan an assistant can connect, but it can't create or edit courses.
How do I connect an assistant?
- Open Settings, then MCP under the Developer section.
- Create a connection. Coassemble gives you a connection URL.
- Add that URL to your assistant as a remote MCP server.
- Sign in once when the assistant prompts you, to authorise it against your workspace. The screen lists what the assistant will be able to do: see your content, create and edit it, publish, delete, and generate with your AI allowance. Untick anything you don't want it to do.
- The assistant appears in your list of authorised connections, and you're ready to go.

It's one sign-in. You don't need an API key, and you don't need to paste credentials into the assistant.
The connection starts in the workspace you authorised it from, and the assistant can switch to any other workspace you belong to. It can only build and edit in workspaces where you're an owner, admin or creator. You can connect more than one assistant, and remove any of them without affecting the others.
What can a connected assistant do?
Close to what you'd do yourself in the app:
- Create courses from a brief or from a document, at any of the three source fidelity levels. You can name the course language in plain words, such as French or Spanish.
- Edit content screen by screen and block by block, including individual quiz questions.
- Restructure courses, reorder screens, and organise courses into collections and folders.
- Publish and share, including getting a share link.
- Read analytics, including course and screen level results, so you can ask what's working.
- Work with branding, themes, translations, and Start and Finish narration.
- Place and generate images, including images already in your workspace library.
- Upload your own images, so you can give it an image and it adds it to your media library with alt text, then uses it for the course cover or an image block.
- Review with Course Coach, so it can review a course and fix what it finds. Screens are numbered from 1, the same way as when it edits.
- Preview learner screens, so it can see a screen the way a learner does and check its own work. A preview of unchanged content is reused. Each workspace can only request a limited number of new previews a minute, so if you hit that limit, the assistant is asked to try again shortly.
- Export SCORM, wherever SCORM export is available to you in the app. The export is queued, and the assistant checks on it until the package is ready.
What does my assistant do, and what does Coassemble do?
Your assistant drives Coassemble. It decides what to ask for and calls the right tools, using over 50 tools covering course creation, editing, publishing and analytics. When it asks for a course to be generated, that generation runs on Coassemble's AI.
The practical effect is that you get to work in the assistant you prefer, while the quality and behaviour of a generated course stays consistent whichever way you asked for it.
How do I see or remove a connection?
Your Settings list every assistant you've authorised, each with its name and icon. Disconnect any of them at any time and it immediately loses access to your workspace.
The name and icon come from the application itself when it connects, so treat them as a label rather than proof of identity. If you see a connection you don't recognise, disconnect it.
Does an assistant use my AI allowance?
Yes. Anything that consumes your workspace allowance still consumes it when an assistant does it rather than you. Image generation is the clearest example. When your allowance is limited, the assistant tells you what an image or narration will cost and waits for you to say yes. Building courses and translating them also use your AI allowance.
Which assistants can I connect?
Any assistant that supports connecting to a remote MCP server and signing in. MCP is an open standard, so this isn't a fixed list, and support depends on the assistant.
Can I drive the agent from my own product?
Yes. If you deliver Coassemble inside your own application, there's a second path. Your backend mints an agent token from your workspace API key and your application drives the Coassemble agent over MCP or REST, so your users get the agent without leaving your product. Create the API key in the Developer console, under Developer, then API keys. You can pin a token to a single course, allowlist which tools it may use, or make it read-only.
The connection described above is different: it's one person authorising their own assistant against their own workspace.
What is MCP?
MCP, the Model Context Protocol, is an open standard for connecting AI assistants to external tools and data. It means an assistant can work with Coassemble through a documented, permissioned connection instead of a one-off custom integration built for a single product.
Frequently asked questions
Can I choose which AI model generates my course content?
No. Course generation runs on Coassemble's AI whichever assistant you connect. What you choose is the assistant you work in and the model it runs on.
Does connecting an assistant replace Coassemble's built-in AI?
No. Coassemble's built-in AI features work exactly as they do now. A connected assistant is an additional way to reach them.
How long does a course take to build through an assistant?
A build runs in the background and can take a few minutes for a longer course. Your assistant starts the build, then checks on it until it finishes, so you don't need to keep asking. The finished course appears in your workspace.
Can I connect more than one assistant?
Yes. Each one appears separately in your list of authorised connections, and you can remove any of them without affecting the others.
Can an assistant read my results as well as build?
Yes, on plans that include the Coassemble agent. The tool set covers analytics, so a connected assistant can read course and screen level data and answer questions about it.
Can an assistant upload documents to Coassemble?
No. An assistant can add images you give it to your media library, but it can't upload documents. To build from a document, upload it to your media library first, or give the assistant a public link to it.
Why does my assistant say it doesn't have permission?
It can only do what you ticked when you approved the connection. To change that, disconnect it in Settings, then MCP, and connect again, ticking the permissions you want.