Blog

The Thought Industries MCP puts your AI to work in the academy

Georgina Ford
November 19, 2026

With the Thought Industries MCP, Claude or any other MCP-compatible AI tool can handle enrollments, run live training, and clear grading queues in your academy, all using the admin permissions you set.

Summary

The Thought Industries MCP is a connector that lets Claude, Cursor, and other MCP-compatible AI tools carry out academy admin work. Admins describe a task, review the plan, and confirm. The AI then enrolls cohorts, runs live training logistics, clears grading queues, and drafts course updates, all within that admin’s existing permissions.

  • Why it matters: Live programs such as workshops, office hours, and certification cohorts take most admin hours. Handing off scheduling, rosters, waitlists, attendance, and grading gives that time back to programs that drive product adoption.
  • How control works: Every request runs as the signed-in admin, within that admin’s role. Clients such as Claude ask before any change, sensitive changes show a preview first, and a read-only connection is available.
  • What changes for your team: Admins work from the AI tool they already have open, with nothing new to learn. On the consent page, they choose which areas the AI can touch.

Customer education teams have heard plenty about what AI could do. So far, most of it has been about asking: what’s overdue, which course to recommend, how last quarter’s enrollments looked. You get the answer, close the chat, and go back to clicking through tasks.

The work is still there on Monday morning. A customer signed last week, and 40 users need accounts. Onboarding 101 needs a cohort. Tuesday’s workshop needs scheduling, and the waitlist needs sorting. A stack of quiz attempts needs grading, and three courses still show last quarter’s screens.

None of that is strategic, but it’s all urgent. In the 2024 State of Customer Education Report, 53% of customer education teams said they’re overloaded. Work like this is a big reason why, and it’s exactly the work AI for customer education should take off their plate.

What is an MCP server for an LMS?

An MCP server for an LMS is a connector that lets AI tools such as Claude and Cursor work directly inside a learning platform. It uses the Model Context Protocol (MCP), an open standard, so the AI can sign in, read academy data, and carry out admin tasks.

The Thought Industries MCP is an LMS MCP server built for academy admins.

Think of it as a universal plug. Lots of software is adding MCP connections, so two questions matter more than the label: what can the connector actually do, and whose permissions does it act with? Those answers decide whether it changes how your team works.

Answers were the first step

The first wave of AI in learning platforms focused on answers. Learners could see what was due. Admins could pull reports without building them by hand. That was useful, and it was a good place to start.

Reading about a backlog still leaves the backlog, though. Knowing 40 users need onboarding doesn’t get them onboarded.

It’s built to do the work. An admin types a request into Claude, Cursor, or another AI tool that supports MCP:

“Create accounts for the 40 Acme users in this list, enroll them in Onboarding 101, and schedule their onboarding workshop for Tuesday.”

The AI lays out the steps, the admin checks and confirms, and the work happens in the academy.

Describe the job. Check the plan. Confirm.

Live training is where the hours go

Most AI connections in learning platforms started with the course catalog, because that’s where those platforms began. That leaves the heaviest work behind.

In customer education, live programs take the most admin hours. Every workshop, office hour, and certification cohort comes with scheduling, rosters, waitlists, attendance, quiz setup, and a grading queue. As live programs grow, so does that work. (Link to the post that owns “instructor-led training”)

So the Thought Industries MCP covers the work around live programs in Thought Industries Academy, from enrollment to the last attendance mark:

JobWhat admins can hand off
Onboard and enrollCreate, update, or disable learners. Enroll up to 100 people at a time in courses or learning paths.
Run live trainingCreate events, sessions, and webinars. Set seat limits, manage waitlists, check rosters, and mark attendance.
Keep certifications movingConfigure quizzes, edit questions and question banks, and work through the grading queue. Grade attempts, with results emailed to learners.
Keep content currentAsk the AI to find mentions of an old feature in courses you tag or list and draft the updated pages for review.

An AI connection that skips live programs covers only part of the week. Your admins need the live work covered too.

Is it safe to let AI make changes in your academy?

Yes, when the AI acts only with the admin’s own permissions and the admin approves changes before they run. The Thought Industries MCP runs every request as the signed-in admin, keeps course edits as drafts [CONFIRM Q1], and offers a read-only connection for teams that only want answers.

Security teams ask about this first, and they’re right to. Many teams experimenting with AI wire it up with a broad API key that can do anything and that no one can scope. That’s a quick way to get a hard no. The Thought Industries MCP works the opposite way:

  • Every request runs as the signed-in admin. Admins connect with their academy login or SSO, and each request stays within the roles and portals they already have. The AI can’t do anything the admin couldn’t do by hand.
  • The admin approves changes. Clients such as Claude ask before running any change, and sensitive ones, like grading a quiz or disabling a user, show a preview and run only after the admin confirms.
  • Course edits stay as drafts [CONFIRM Q1]. Changes to a published course stay hidden from learners until the admin publishes, so nothing half-finished goes live.
  • Read-only is an option. Teams that only want answers can use a separate read-only connection that never changes data.
  • Admins choose what the AI can touch. On the consent page, they can untick any area their role allows, but they’d rather keep it manual.

To be clear, this connector changes real data in your academy. That’s the point. It acts with the admin’s permissions and not a single one more.

Four problems it fixes

Slow onboarding puts renewals at risk. Customers who aren’t trained early adopt less, and accounts that adopt less are harder to renew and grow. Getting new users enrolled and learning right after they sign up shortens time to value. (Link: /guides/customer-onboarding/)

Admin hours go to logistics instead of programs. When enrolling a cohort, cleaning up records, or clearing a grading queue takes one request instead of an afternoon, LMS administration time drops, and your team can run more programs.

Stale content and slow results erode trust. A course with outdated screens or a quiz result stuck in a queue tells learners the program isn’t keeping up. Faster refreshes and grading keep them moving.

Unapproved AI creates risk. Every change runs as a named admin within existing permissions, so AI adoption can pass a security review instead of working around it.

No new tool to learn

Your team probably already has an AI tool open all day. The Thought Industries MCP works with AI tools that support remote MCP connectors with sign-in, and setup steps cover Claude, Claude Code, Cursor, and VS Code. There’s nothing new to buy or learn. Your academy becomes something the AI you already use can work in.

Thought Industries Academy is part of the Customer Knowledge AI Platform. Academy builds expertise. Lens applies it in the moment.

The question has changed

For the past couple of years, the question in customer education was, “Can AI tell me about my academy?” That question has been answered, and the answer is yes.

The question now is, “Can AI run my academy safely, including the live programs that take up most of my team’s week?”

We built the Thought Industries MCP so the answer to that one is yes, too. See it run your next cohort, workshop, or grading queue in a personalized demo.

See Thought Industries in action

Get a personalized demo of the Customer Knowledge AI Platform, built around your products and your customers.

Book a personalized demo

Frequently asked questions

What is an MCP server for an LMS?

An MCP server for an LMS is a connector built on the Model Context Protocol, an open standard that lets AI tools work directly inside a learning platform. The Thought Industries MCP lets Claude or Cursor enroll learners, schedule live sessions, and grade quizzes in your academy.

What can academy admins do with the Thought Industries MCP?

Admins can create, update, or disable learners, enroll up to 100 people at a time, create events, sessions, and webinars, manage seat limits, waitlists, and attendance, configure quizzes and question banks, grade attempts, and draft updates to outdated courses.

Can the AI make changes without admin approval?

No. Clients such as Claude ask before running any change. Sensitive changes, like grading a quiz or disabling a user, also show a preview and run only after the admin confirms. Each operation runs only if the admin’s role allows it.

What permissions does the Thought Industries MCP use?

It uses the signed-in admin’s permissions. Each request stays within that admin’s role and portals, and an operation runs only if the role has the permission it needs. On the consent page, admins can also untick areas they’d rather keep manual.

Which AI tools work with the Thought Industries MCP?

It works with AI tools that support remote MCP connectors with sign-in, and setup steps cover Claude, Claude Code, Cursor, and VS Code. Teams that only want answers can use a separate read-only connection that never changes academy data.

How does an MCP reduce LMS administration time?

It turns multi-step admin work into one request. Creating 40 learner accounts, enrolling them in a course, or clearing a grading queue takes one described task and one approval, so admins spend fewer hours on logistics and more on running programs.

How is the Thought Industries MCP different from Lens?

The Thought Industries MCP carries out admin work inside Thought Industries Academy. Lens is a governed AI knowledge layer that delivers trusted and accurate product guidance and answers across every channel. Academy builds expertise. Lens applies it in the moment.