About the Thought Industries MCP

The Thought Industries MCP brings your academy into the AI assistant you already use, like Claude or Cursor. Instead of moving from screen to screen to enroll a cohort, update a course, or manage a workshop waitlist, you describe what you need in a conversation. The assistant works out the steps, shows you its plan, and once you confirm, carries out the work in your academy with the same permissions you already have.


Feature flag: Open Beta

The Thought Industries MCP is in Open Beta. To turn it on, navigate to Apps > Labs. On the MCP Connector (Beta Access) tile, select Show Flags and turn on the MCP Connector (BETA) toggle. To learn more, see Thought Industries Labs.

What is MCP?

MCP stands for Model Context Protocol. It's an open standard, which means it's a shared set of rules that any software company can follow. Those rules let AI assistants connect to other software and work with it.

Think of MCP like a universal power adapter. Your AI assistant is the device, and your academy is the outlet. MCP is the adapter in the middle that lets the two work together. You don't need to know how the wiring works to use it.

Without MCP, an AI assistant only knows what you paste into the chat. With MCP, it can look things up in your academy and make changes for you, but only the changes you ask for.

Note

Already familiar with MCP? The Thought Industries MCP is a hosted, remote MCP server with OAuth sign-in. There's nothing to install. Skip ahead to How to Set Up the Thought Industries MCP.

Key terms

AI assistant

The app you type into, such as Claude or Cursor. In MCP terms, this is the client.

The MCP (or connector)

The part of your academy that your AI assistant connects to. In MCP terms, this is the server.

Tool

A single action the connector offers, such as "find a user" or "enroll a user in a course." Your assistant picks the right tools based on what you ask.

Prompt

The request you type into your AI assistant, such as "Show me the courses in my catalog."

What is the Thought Industries MCP?

The Thought Industries MCP is built into your academy. After you connect your AI assistant to it, you describe a task, and the assistant picks the right tools and carries out the task in your academy.

For example, instead of opening several admin pages to create learner accounts and enroll them, you type:

"Create accounts for the five people in this list and enroll them in Onboarding 101."

The assistant creates the accounts, shows you what it plans to do, and makes the enrollments after you confirm.

An AI assistant's reply to a plain-language request to create accounts and enroll them in a course, showing its plan before making changes

Use Case Information

The MCP is for academy admins who want to spend less time in the admin UI on lookups, routine updates, and bulk changes.

The connector gives your AI assistant a set of tools for everyday admin work, like managing users and enrollments, updating courses, running events and webinars, and grading quizzes. The developer documentation has the full list of tools and what each one does.

View the MCP tools

What the MCP doesn't do

  • Delete users or courses. You can deactivate a user, archive an event session, or remove a question from a quiz instead.
  • Run reports or analytics.
  • Create or edit learning paths. You can enroll users in an existing learning path.
  • Manage licenses, SKUs, or coupons.

Who can use it

The MCP is for people with an Admin Level Account. It respects each user's permissions, so the assistant can only do what that person is allowed to do. Learners can't connect.

It works with any AI assistant that supports remote MCP connectors with sign-in. Thought Industries tests with Claude and Cursor.

Note

The MCP is free during Open Beta. Your AI assistant's usage is billed by your AI provider under your own subscription, not by Thought Industries.

How it keeps your academy safe

Your permissions set the limits

The MCP respects your user permissions. The assistant can only see and change what your account can see and change in the admin UI.

Changes are made as you

Every change runs under your own admin account, with the same permissions you have in the admin UI.

You confirm first

The assistant shows you its plan before it changes anything. Changes to users, enrollments, events, and quizzes take effect as soon as you confirm. Course creates and edits save as drafts and are only published when you ask.

Read-only option

A separate read-only connection lets the assistant look things up without changing anything.

Activity you can review

The MCP Connector page in your admin lists every connected assistant and logs what assistants do on admins' behalf for 180 days.

Your prompts stay private

Your prompts and the assistant's replies stay in your AI assistant. Thought Industries only receives the actions the assistant takes.

Warning

The MCP changes real data in your academy. AI assistants choose tools on their own and sometimes misread a request, so read the plan before you confirm, especially for bulk changes like enrolling or deactivating many users at once. If you only need answers, use the read-only connection.

How it's different from other Thought Industries AI tools

Thought Industries for Claude

A separate plugin that guides you through course authoring in Claude. The plugin and the MCP aren't connected, and the recommendation is to use one or the other. To compare them, see MCP or Plugin? Choosing the Right Thought Industries AI Tool.

Lens

Lens has its own MCP channel that answers questions from your knowledge sources. The Thought Industries MCP is for admins running the academy, not for answering customer questions.

Was this article helpful?
0 out of 0 found this helpful

More resources

  • Academy

    Go from beginner to expert with hands-on training

  • Community

    Ask questions, swap ideas, and learn from people like you

  • Developer Docs

    Reference guides and code samples for developers