Intellum MCP Connectors

Anything your people do in Intellum, they do from their AI tool.

Learners, creators, admins and Evolve authors work in Intellum from Claude, Gemini or Copilot. What each person can do matches their role-based access and permissions, as you define them in Intellum.

Get a Demo
ClaudeLearner MCP connected
What changed in Automations before my renewal call?
Intellum ·Searching your courses· 2 lessons
Automations start on a trigger or schedule, so recurring work runs without anyone kicking it off. Lead with the hours it gives back. Source: Automations basics, Lesson 2.
Reply to Claude…

Every role gets its work done from one conversation.

Four connectors cover the platform, one for each way people use Intellum. Pick a role to see what changes for them and the work their connector reaches.

Learners · Learner MCP

Get answers in the tool they already have open.

Answers come from the courses each learner can open, with a link back to the lesson.

Creators · Creator MCP

Draft course pages in the tool they already use.

Page drafts land in their Intellum courses until a creator publishes them.

Admins · Manager MCP

Run programs from a conversation.

Enroll people, update users and groups, send communications and pull reports. The plan comes back for a yes before anything changes.

Evolve authors · Evolve MCP

Edit Evolve courses in plain language.

Build and update interactive Evolve courses under each author’s Evolve role.

The Intellum Platform
All four connectors
LMS
Catalog search
Answers from courses
Lesson explanations
Assessment review
Course page drafts
Users
Groups
Group rules
Enrollments
Filtered lists
Reports
Communications
Evolve
Build Evolve courses
Update Evolve courses

Prefer to work inside Intellum? Learner, Creator and Manager Agents are an optional way to get help right in the LMS and Evolve.

Learner AgentCreator AgentManager Agent

Every request runs under your access rules.

The AI tool and the connector sit outside Intellum. The connector carries each request in as the person who asked, so what they can do matches the role-based access and permissions you define in Intellum.

“Enroll the Partner admins, Q3 group in Partner certification.”
Partner program admin, in Copilot
Inside the admin’s access
Outside the admin’s access
Outside Intellum
1

Copilot plans it

Two steps: find the group, then enroll it
2

The connector carries it in

Signed in with the admin’s own Intellum account
Inside the Intellum Platform
3

Your access rules

Admin for the Partners audience, as you set it
4

The admin approves

Plan approved: 212 people, 1 path
5

Your audit log

The admin’s name · Manager MCP connector
Done. 212 people enrolled in Partner certification 2026.
Mass deletes and deactivations are refused, whatever an admin’s permissionsConversations stay under your company’s own AI agreement

What an LMS MCP connector should do.

Six tests for connecting AI tools to a learning platform. Intellum’s MCP connectors meet each one.

The testHow Intellum meets itIntellum
01

Covers everything people do

Anything your people do in Intellum, they do through the connectors.

Meets it
02

Serves every role

Learners, creators, admins and Evolve authors each have a connector.

Meets it
03

Follows your access rules

Each request runs inside the person’s role-based access and permissions.

Meets it
04

Asks before it changes anything

Changes wait until the person approves the plan.

Meets it
05

Keeps a named record

The audit log shows who made each change and through which connector.

Meets it
06

Works in the major AI tools

Claude, Gemini and Copilot.

Meets it

Enterprise security is at the core of Intellum.

AICPA SOC

SOC 2 Type II

Controls audited by an independent CPA firm.

W3C STANDARD

WCAG 2.1 AA

Every Level A and AA criterion supported, documented in our VPAT.

U.S. HEALTH DATA

HIPAA

Safeguards confirmed by third-party attestation.

CROSS-BORDER DATA

EU-U.S. DPF

Certified participant in the Data Privacy Framework.

99.9% uptime SLA · 24/7 support
Read the AI Use Policy

Questions about Intellum MCP connectors

What can I do through Intellum’s MCP connectors?

Anything your people do in Intellum. Learners, creators, admins and Evolve authors each have a connector, and what a person can do through it matches their role-based access and permissions in Intellum.

MCP, the Model Context Protocol, is an open standard that lets an AI tool connect to other software. Intellum’s MCP connectors link Claude, Gemini and Copilot to the Intellum platform, so people can ask for Intellum work in the AI tool they already use.

Claude, Gemini and Copilot. Each person adds the connector in their AI tool and signs in with their Intellum account.

Agents work inside Intellum. Learner Agent, Creator Agent and Manager Agent are an optional way to get help in the LMS and Evolve. MCP connectors sit outside Intellum and link the AI tool a person already uses to the whole platform: the AI tool plans the steps, and the connector carries each one in under that person’s role-based access and permissions.

No. Each person signs in as themselves, so the AI tool reaches only what their role-based access and permissions allow in Intellum. Every change shows in the audit log with the person’s name and the connector.

Yes, by design. Billing, SSO and e-commerce settings stay in Intellum, and each request is capped at five changes so no single ask can make changes at scale.

Several enterprise LMS vendors now publish MCP servers or connectors. Intellum offers four generally available MCP connectors, for learners, creators, admins and Evolve authors, that work in Claude, Gemini and Copilot. Our LMS comparisons cover how each vendor’s MCP differs.

Bring all of Intellum into the AI tools people already use.

Each person adds Intellum to Claude, Gemini or Copilot, signs in as themselves and asks for the work.

Get a Demo
Explore the platform