EduBase/MCP

This repository contains the **implementation of the Model Context Protocol** (MCP) server **for the EduBase platform**. It allows MCP clients (for example Claude Desktop) and LLMs to interact with your EduBase account and perform tasks on your behalf. It supports stdio, SSE and streamable HTTP transport protocols.
What is EduBase?
EduBase is an innovative, modular, online educational platform that makes learning more enjoyable, simpler and interactive, suitable for educational institutions or enterprises.
Why choose EduBase?
EduBase revolutionizes digital learning with its unique combination of features:
* **Advanced Quiz System** with parametrization allowing infinite variations of the same question, real-time cheating detection, beautiful LaTeX typesetting, advanced STEM-support and automatic grading
* **Unified Learning Environment** that centralizes all your educational content — videos, exams, documents, and SCORM modules — in one intuitive system
* **Enterprise-Grade Security** with features like SSO integration, fine-grained access controls, comprehensive auditing, and GDPR compliance
* **Integration** with your existing systems through LTI, comprehensive API, and custom integration options
* **AI-Assisted Tools**, such as EduBase Assistant, that can instantly transform your existing content into interactive quizzes and assessments, or translate your materials from one language to another
From higher education institutions to corporate training departments, EduBase scales to meet your specific needs while maintaining an intuitive user experience across all devices.
Demo video
Collaboratively creating and uploading questions, scheduling exams and analyzing user results with Claude:
Obtaining your API credentials
Once logged in, on your Dashboard, search for the Integrations menu, click "add integration" and choose the type "EduBase API".
**If you don't see this option**, enter the MCPGITHUB activation code or feel free to contact us to request access at info@edubase.net.
Tools
Each documented API endpoint is available as a tool, named edubase_ _ . For example, the tool for the GET /user:me endpoint is named edubase_get_user_me. The tag, permission and transfer endpoints work the same way for every content type, so they share a single tool per method with a type argument (e.g. edubase_post_content_tag for POST /exam:tag, POST /quiz:tag, etc.). See our developer documentation for more information.
Toolsets
Tools are grouped into toolsets, so you can expose only the tools you need. Fewer tools use less of the model's context and make it easier for the model to pick the right one. Every toolset is enabled by default.
| Toolset | Tools for |
|---|---|
| files | Temporary file uploads (always enabled) |
| questions | Questions |
| quizzes | Quiz sets, their questions, settings and grading presets |
| exams | Exams, their settings, users, certificates, branding and journeys |
| results | Quiz and exam results, certificate downloads |
| users | Users, their names, groups and login links |
| classes | Classes and class memberships |
| organizations | Organizations, members, departments, competencies and webhooks |
| integrations | Integrations and their keys |
| tags | Tags and tag attachments of contents |
| permissions | User permissions on contents and ownership transfers |
| metrics | Custom metrics |
Select toolsets with a comma-separated list in EDUBASE_TOOLSETS (e.g. questions,quizzes,exams). Set EDUBASE_READONLY=true to expose only the tools that read data (the get tools, and the tools that only generate download links, like edubase_post_question_export).
Set EDUBASE_DYNAMIC_TOOLSETS=true to enable toolsets on demand: sessions start with only the critical tools, and the model enables the toolsets it needs with the edubase_enable_toolsets tool (listed with edubase_list_toolsets). This keeps the initial tool list small for clients that load every tool upfront, but needs a client that refreshes the tool list when notified about changes.
When an HTTP transport is used, clients can narrow the configuration further for their own session with the EduBase-Mcp-Toolsets, EduBase-Mcp-ReadOnly and EduBase-Mcp-Dynamic headers, or the toolsets, read_only and dynamic_toolsets query parameters (e.g. https://domain.edubase.net/mcp?toolsets=exams&read_only=true). A session can never enable toolsets or write tools that the server configuration disables.