Your LMS inside ChatGPT and Claude — with each person's own permissions
Every admin and teacher links their own AI account to the institution. The assistant reads reports, builds lessons, records grades and updates settings as if it were that person in the admin panel — no shared key, no copy-paste, everything audited.
Short answer
Studeia exposes a Model Context Protocol (MCP) server for every institution. Administrators, coordinators, pedagogues and teachers connect their own ChatGPT, Claude or Claude Code account through OAuth 2.1, and the assistant can pull reports, build lessons, record grades and adjust settings with exactly that person's permissions — 130 tools, every call audited, revocable in one click.
AI is already in the school. The LMS just doesn't talk to it.
Teachers and coordinators use ChatGPT and Claude every day — copying LMS data into the chat and pasting results back, with no trail and no control.
Copy-pasting reports
Export the grade sheet, paste it into the chat, ask for the analysis, redo it all next week. For every class.
A shared API key
One institutional key passed around gives everyone access to everything, with no way to tell who did what.
AI that doesn't know your institution
The assistant writes a generic lesson plan because it has no idea who the students are or what was already taught.
Student data out of control
Without explicit consent or logging, nobody knows which minors' data ended up with which provider.
The assistant acts as the real user — no more, no less
Studeia's MCP connector is an OAuth link between a person's AI account and their account at the institution.
Real permissions, by role
Teachers only see and edit the courses and class groups they teach; coordinators and pedagogues see the institution; administrators also configure it. No global key.
130 read and write tools
Courses, modules, lessons with type-validated content, teacher guides, class groups, enrollments, grades, competencies, question banks, reports, live classes, gamification and automations.
Reports on demand
"Which students in class B are at risk, and why?" — student, course and tutor-efficacy reports from real data, without exporting anything.
Lesson creation and review
Generate slides, quizzes and teacher guides in bulk, rewrite content in simpler language, run the AI review of an entire course.
Works in ChatGPT, Claude and Claude Code
MCP plugin in ChatGPT (Developer mode), custom connector in Claude (web, Desktop and mobile) and claude mcp add in the terminal — same link, same server.
Audit and one-click revocation
Every tool call is logged (name, ids, outcome — never the content). Users revoke from their profile; admins revoke any link or switch the whole connector off.
From the admin panel to the chat in five steps
- 1
1. Enable the connector
An admin turns on 'Allow MCP connections' under Settings → AI connectors and decides whether teachers can connect too.
- 2
2. Copy the URL
https://your-school.studeia.com/api/mcp — or your verified custom domain.
- 3
3. Add it to the assistant
ChatGPT: Settings → Plugins → Developer mode → + New plugin. Claude: + → Connectors → Add connector. Claude Code: claude mcp add.
- 4
4. Authorize
Log in to the institution and review the consent screen: permissions, role and a plain-language notice about data processing by the AI provider.
- 5
5. Ask
"List the lessons without a teacher guide and write one for lesson 4." The assistant calls the tools; writes ask for confirmation.
LMS without an MCP server × Studeia
| — | LMS without an MCP server | Studeia with the MCP connector |
|---|---|---|
| How AI reaches the data | Copy-pasting exports into the chat | Direct link with the person's own login |
| Permissions | A global API key, or none | The user's real role, re-checked on every call |
| Writing to the LMS | Manual, after copying the answer | 68 write tools, confirmed in the assistant |
| Traceability | None | One audit event per tool call |
| Revocation | Rotate the key or the password | One click in the profile or the admin panel |
| Supported assistants | — | ChatGPT, Claude (web, Desktop, mobile) and Claude Code |
Connector numbers (no rounding)
Security and privacy by design
- OAuth 2.1 with PKCE and dynamic client registration — no typed keys, no secrets in the browser.
- Opaque, short-lived tokens: only the hash is stored; 1-hour access token, rotating refresh with reuse detection, links capped at 30 days.
- Bound to the institution's address: a token issued on your domain is not valid on any other host.
- Explicit consent: the authorization screen states, in plain language, that the data the assistant reads (including minors' data) is processed by the AI provider of the user's account — the institution remains the controller and decides whether teachers may connect.
- Out of reach by construction: billing, SSO/SCIM, provider keys, uploads and the connector's own configuration are never exposed to the AI.
Technical details, the full tool catalog and troubleshooting live in the connector documentation.
Included in every plan
The MCP connector has no extra cost. Your ChatGPT or Claude plan is purchased from the respective provider.
Demo: 1,000 calls per hour per link. Paid plans: 5,000 per hour. Enterprise limits and terms are set by contract.
Try it with your own AI account
Demo without a card
Create the institution, enable the connector and link your ChatGPT or Claude the same day.
Switch it off any time
Disabling the connector revokes every link immediately. Nothing is locked in.
Open standards
MCP and OAuth 2.1 are public standards — the same server serves any compatible client the institution authorizes.
Frequently asked questions
Is the MCP connector a plugin or a custom GPT?+
No. It is a remote MCP (Model Context Protocol) server that ChatGPT, Claude and Claude Code use as a native connector. It speaks the standard protocol with OAuth 2.1 and does not depend on any plugin or published GPT.
Do I need an OpenAI or Anthropic API key?+
No. Each person uses their own ChatGPT or Claude account and authorizes the link by logging in to Studeia. The institution shares no key — and the assistant plan is purchased from the provider.
Does a connected teacher see the whole school's data?+
No. The assistant acts with the person's real role: teachers only see and edit the courses and class groups they teach (67 of the 130 tools). Coordinators, pedagogues and administrators see the whole institution; platform-level global admins cannot connect.
Can I switch it off or limit it?+
Yes. The administrator enables and disables the connector, decides whether teachers may connect and revokes any link. Each user revokes their own from the profile. In Claude you can disable individual tools; in ChatGPT, with the default permission, every write asks for confirmation.
Does student data go to OpenAI or Anthropic?+
The data the assistant reads is processed by the provider of the user's account, outside Studeia — the consent screen says so explicitly. The institution remains the data controller and every call is audited, without the content.
Does it require a specific plan?+
No. The connector is available on every plan, including the free demo. The only per-plan limit is the hourly call rate per link.
Does it work with Copilot, Gemini or other assistants?+
Today the server accepts the OAuth callbacks of ChatGPT, Claude and local clients (Claude Code). Other MCP clients with OAuth may work technically, but only those three have been validated.
Link your ChatGPT or Claude to your institution today
Create the demo, enable the connector and ask for the first report in under ten minutes. If it doesn't fit, switch it off — nothing is locked in.
Free · No card · Connector included in every plan