One tool per documented endpoint means a flow that normally spans several screens collapses into one conversation: draft the questions, group them into a quiz set, open an exam on that set with a window and an assigned cohort, then read the results back and issue the certificate. The same coverage runs through the administrative side — users, classes, organizations, permissions, webhooks — which is what makes the bulk work worth doing here rather than by hand.
EduBase's own server. Each documented endpoint of the EduBase API is its own tool, named edubase_<method>_<endpoint>, which covers the whole Quiz hierarchy — questions, quiz sets, exams — plus users, classes, organizations, tags, permissions, integrations and webhooks.
- Quiz questions published, updated, exported and deleted — the atomic level, and independent of any quiz set
- Quiz sets assembled from those questions, with question groups, skills and copy-from-existing
- Exams created on a quiz set with open and close times, branded, and assigned to named users
- Results at every grain: one play, one user on a quiz set, one user on an exam, or the raw answers behind an exam
- Certificates for a user on an exam, with a download link generated on request
- User accounts created, renamed, grouped, deactivated, and found by email, username or code — plus expiring login links
- Classes and organizations with their members, including many users assigned to many classes or organizations in one call
- Tags attached to classes, courses, events, exams, quizzes, SCORM materials, videos, integrations and organizations
- Per-object permission checks, grants and revocations, and ownership transfer
- Organizational webhooks created, updated and triggered on demand with a custom payload
- Files uploaded to EduBase temporary storage from a local path or a URL
- API and LMS integrations created, with their keys and secrets rotated
An EduBase integration app: on your dashboard open Integrations, add one of type "EduBase API", and if that option is not offered, the activation code MCPGITHUB unlocks it. Pass its App ID and secret as EDUBASE_API_APP and EDUBASE_API_SECRET, with EDUBASE_API_URL pointing at your deployment (it defaults to https://www.edubase.net/api). Runs over stdio through npx or the edubase/mcp Docker image. To serve it remotely, EDUBASE_SSE_MODE or EDUBASE_STREAMABLE_HTTP_MODE switches to HTTP on EDUBASE_HTTP_PORT, which defaults to 3000, and EDUBASE_OAUTH turns it into an OAuth 2.1 protected resource, so clients connect through an EduBase consent screen with no secret to copy. Accounts on www.edubase.net can instead point a client at the hosted endpoint, https://www.edubase.net/mcp.
One command plus a key — npx -y @smithery/cli install @EduBase/MCP --client claude, then supply credentials