Run your school from Claude.
The Course Engine connector lets a school's administrators work in Course Engine from Claude: look up a student, explain an order, moderate the forum, edit the catalogue or follow a course being built. Claude acts as you, with the permissions you already have, and nothing that reaches students happens without your confirmation.
Your school's admin, in a conversation.
Ask in plain language. Claude finds the right records in your school, explains what it sees and, when you ask for a change, shows you exactly what it will do first.
Answer student questions
"Why can't she open lesson 3?" Claude reads the student's enrollments, progress, orders and certificates and tells you, in one step.
Run the day to day
Coupons, reviews, forum moderation, account emails and order notes, without hunting through admin pages.
Build and edit courses
Follow a course project, read outlines and lessons, answer the expert's open questions, propose fixes and edit the catalogue. Drafts stay drafts until a person publishes them.
Three steps, about a minute.
You need a Course Engine administrator account and a Claude plan that supports connectors.
- 01
Add the connector in Claude
In Claude, open Settings, then Connectors, and add Course Engine: from the Connectors Directory once it is listed there, or as a custom connector with the address below.
- 02
Sign in to Course Engine
Claude sends you to course-engine.com. Sign in with Google, or with your password and your two-step verification code.
- 03
Approve the connection
The approval screen names your account and your school. Approve, and you are back in Claude, connected. Try "Who am I connected as?"
https://mcp.course-engine.com/mcpSchool administrators, signed in strongly.
- Administrators of a Course Engine school
Anyone with an administrator role in the school can connect. Students, members and instructors cannot.
- Google sign-in or two-step verification
A password alone is not enough to approve a connection. Sign in with Google, or turn on two-step verification in Course Engine under Settings, Two-Factor Authentication.
- One school per connection
The connection is tied to the school you were signed in to when you approved it. Claude can never read or change another school's data.
- Your own permissions, checked every time
Your role is read again on every request. When an owner removes your admin role, the connector stops working for you on the next request.
Nothing reaches a student without your yes.
Reading is immediate. Changes that are visible to students, send email or cannot simply be undone follow a preview and confirmation step.
Preview first
The first request returns a preview of the change and a one-time confirmation code. Nothing has happened yet.
Confirm with the code
The change happens only when the same request is sent again with that code, within 10 minutes. The code works once, for your account, and only for exactly the change that was previewed.
No records are deleted
No tool deletes a course, a student, an order or a ticket. The few actions that cannot be undone, such as resetting a student's progress or merging two tickets, always show a preview and need your confirmation code.
Every change is logged
Changes are written to your school's audit log under your name, marked as made through the assistant.
No money moves
The connector cannot refund payments or change prices. It cannot switch an ad campaign on or change a live campaign's budget: campaigns it drafts stay paused. Those stay in the web admin.
No AI media generation
The connector does not generate images, audio or video. Course text that Course Engine's generator writes is shown to you as a draft.
What Claude can reach.
Read tools return data; write tools change it. Each tool states which it is, so Claude can ask before it writes.
Students and access
Find a student, see their enrollments, progress, orders and certificates, grant or remove course access, send account emails, and reset a student's progress (confirmed first: it cannot be undone).
Orders, subscriptions and coupons
Look up orders and subscriptions, add internal notes, resend an email Course Engine already sent (a receipt, for example), create and disable coupons.
Catalogue
List courses, lessons, topics and products; create a draft course, add lessons and topics, enroll a learner.
Course building
Project status, outlines and lessons, the expert's open questions, comments and proposed fixes, approving drafts, and the school's AI spend.
Community and reviews
Read forum topics; pin, close, reopen, move or hide them; read reviews, reply to them and change their status.
Reports
The dashboard, the email log and who is online now.
Add-ons, when connected
Schools that use the Unison marketing CRM or the Support CX help desk also get those tools. A school without them does not see them.
What the connector keeps, and for how long.
Course Engine processes your school's data for your school, under its agreement with us. The connector adds very little of its own.
Sign-in tokens
The tokens Claude uses to call Course Engine. Access tokens expire after one hour and refresh tokens after 30 days. They are stored hashed, and the connection details (your account, school and email) encrypted.
Confirmation codes
Each preview stores a code with a fingerprint of the change, for 10 minutes or until it is used.
Add-on sessions
For a school with Unison or Support CX, a short session with that app is kept for up to 6 hours so each request does not sign in again.
Audit log
Each change made through the connector, with your account, the time and what was changed, kept for the period your school sets (365 days unless it chooses otherwise).
Technical logs
Our hosting provider, Cloudflare, processes request data such as IP addresses to deliver and protect the service. Our own error logs do not record your conversation.
Not collected
Course Engine never sees your Claude conversation, memory or files: only the requests Claude sends to the connector. What a tool returns enters your conversation in Claude, under your own agreement with Anthropic.
In short: access tokens last one hour and refresh tokens 30 days; confirmation codes last 10 minutes; add-on sessions last up to 6 hours; the audit log is kept for the period your school sets, 365 days by default. Course Engine does not sell this data and does not use it to train AI models.
Course Engine is operated by Laboratoires de Solutions Web Inc. (SolutionLabs), 125 Rue Lamarche, Laval, Quebec H7X 4E6, Canada (NEQ 1175501601). Person in charge of the protection of personal information: Charles Lapointe, President, hello@course-engine.com.
Our published privacy policy currently covers the course-engine.com website; for the connector, the facts on this page apply. Read the website privacy policy.
Things to ask.
- “Who am I connected as, and which school?”
- “Find the student jane@example.com and tell me what she is enrolled in and how far she got.”
- “Show the status of our course projects and the questions waiting for me.”
- “Create a 20% coupon WELCOME20 for five uses, ending next Friday.”
- “List this week's new forum topics and pin the welcome thread.”
Questions and troubleshooting
The approval page says I cannot connect.
You need an administrator role in the school, and you must have signed in with Google or with two-step verification. Turn it on under Settings, Two-Factor Authentication, sign in again and retry.
A tool says a confirmation code expired.
Codes last 10 minutes and work once. Ask Claude to run the change again: you will get a fresh preview and a new code.
Claude says my school has no Unison or Support CX connected.
Those tools only work for schools that use those apps. Everything else in the connector works without them.
How do I disconnect?
In Claude, open Settings, Connectors, and disconnect Course Engine. A school owner can also end your access at any time by removing your admin role.
Can I use it for more than one school?
A connection belongs to one school. If you administer two, connect while signed in to the one you want to work on.
Something not working?
Write to us and include the time and what you asked Claude. We answer within one business day.
Not on Course Engine yet?
The connector works with every Course Engine school. See the platform on your own catalogue.
Book a demoWe reply within one business day.