Can I move my training results through MCP?

# Can I move my training results through MCP?

Support for working with your training data through MCP (the Model Context Protocol) is coming soon. It will let AI assistants and agents read your Coassemble results and write them into the tools you already use, so reporting and record-keeping can happen through the AI tools you work in. This page describes the intended approach and will be updated with exact steps when it ships.

MCP is an open standard for connecting AI assistants and agents to external tools and data. Working with your results through MCP means an AI agent could read your Coassemble training data and write it into the systems where you keep records, rather than you exporting it or building a custom integration for each tool.

## What this is for

Training results are most useful when they reach the systems your team actually works in: a CRM, an HR system, a data warehouse, or an internal dashboard. Today you get results out by exporting a CSV or pulling them through the API. MCP is intended to add a third way, where a connected AI agent can move the right data to the right place for you, and keep records updated, without a separate build for every destination.

## How it's intended to work

The plan is for Coassemble to make your training data available over MCP so a connected AI assistant or agent can read results and write them into your other tools. Because MCP is an open standard, this is intended to work across the AI tools that support it rather than being tied to a single assistant.

The exact setup, what's required, and which plans include it will be confirmed when the feature is released. We'll update this page with concrete steps then.

## Frequently asked questions

### Is this available now?

Not yet. Working with your data through MCP is coming soon. For now, you can export results as a CSV or pull them through the API. This page will be updated with setup steps when it's released.

### What is MCP?

MCP, the Model Context Protocol, is an open standard for connecting AI assistants and agents to external data and tools. It lets an AI tool read your results and write them elsewhere without a one-off custom integration.

### Which tools will this work with?

MCP is an open standard, so the intent is to support the AI assistants and agents that work with it. Specifics will be confirmed at release.

Write data back via MCP

Learners & tracking

Course analytics

Link analytics

SCORM usage

Reporting FAQ

Quiz results

Sentiment

Collection analytics

Analytics overview

Report dashboard

Webhooks

API events

Where results go

Getting started in 5 minutes

What is Coassemble?

Terminology

Workspace tour

Getting started FAQ

Sign up

Coassemble as an LMS

Migrate from other tools

Getting started

Supported file types

Create from a document

Create options compared

Cloud storage

Create from slides

Sources overview

Sources you build from

Folders

Creators

Transfer ownership of your workspace

Common questions: Workspaces

Managing account, workspace, and billing settings

Workspace management

Course Collections

Collections overview

Courses overview

End-user (learner) experience

Screens

Brand kit

Create from scratch

The Finish screen

Quizzes

Languages

Media: images

Which screen to use

Create a course

Course creation FAQ

Media: video

Publish a course

Themes

Manage & edit courses

Content curation

White-labeling

AI course creation

Custom fonts

Asset library

What you can build

Course links & access

Publish & share

Share to Slack

SCORM export

Sharing FAQ

Shareable templates

Email invitations

Custom domain

Embed in your product

Deploy via MCP

Where training goes

Flow

Pulse

Embed Core

Embed Automate

Embed Partner

Overage & rates

Usage limits

Payments & billing

Plans & pricing overview

Plan changes

Plans & billing

Explore best practices for sharing your knowledge.

Build the business case for Coassemble

Assessment: Best practice for quizzes

Best practices

SCORM files not loading

SCORM session errors on Apple devices

Why isn't my Embed screen working?

Common questions: Troubleshooting

What do I do if there is a bug?

Troubleshooting

Security & SOC 2

Accessibility

Our approach to AI

AI & data security

Trust

Loom

Stripe

Notion

YouTube

HubSpot

Arcade

Vimeo

Unsplash

360Learning

aNewSpring

Docebo

Integrations overview

Slack

Connect with the API

Connect your AI model

Integrations

Release notes

Updates

Resources specifically for Embed (previously referred to as Headless course creation). These are resources that previously lived on the Headless Resources Hub.

Coassemble Embed Partner Security, Data Protection & AI FAQ

Default usage caps for clients

Managing tenant caps

Accessibility guide

AI and Data Security for Coassemble Embed Partners

Coassemble vs. Articulate: Feature comparison guide for course authoring teams

Coassemble is WCAG 2.2 Level AA Conformant

Competitor analysis

Designing effective microlearning courses

How to access and interpret the Headless usage report

How to handle competitor objections when positioning your Embed solution

Guide to pricing models for Coassemble Embed and key competitor benchmarks

Sales enablement guide: Driving user adoption

Customer testimonials for Coassemble Embed course creation (sales enablement)

Our mission: Barrier-free knowledge transfer (partner-friendly positioning language)

Getting started guide

How to communicate Coassemble feature releases to your customers 

How to migrate courses from other authoring tools into Coassemble Embed

Guide to releases

Curate

AI Create

Customize

Learner experience

Self-hosting Coassemble Embed

Initial AWS requirements for self-hosting

Embed Partners

Coassemble's AI: how it builds courses, screens, quizzes, images and narration, and how you stay in control.