LearnWorlds vs Openemis Pro — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
LearnWorlds vs Openemis Pro
In-depth architectural comparison of the LearnWorlds and Openemis Pro MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
LearnWorlds
Education · Remote HTTP/SSE
Quality: 41/100 (Fair) | Auth: No auth required
Openemis Pro
Education · Remote HTTP/SSE
Quality: 48/100 (Fair) | Auth: No auth required
Verdict Summary: Choose LearnWorlds if you need specialized Education tools running via a hosted cloud SSE transport. Choose Openemis Pro if your workspace requires Education integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose LearnWorlds when:
You need dedicated capabilities in the Education domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: LEARNWORLDS_BASE_URL, LEARNWORLDS_API_TOKEN, LEARNWORLDS_CLIENT_ID, MCP_AUTH_TOKEN.
Primary tools included: 94 OpenAPI-generated LearnWorlds API tools, Read-only, write, and destructive safety categories, stdio and Streamable HTTP transports.
LearnWorlds is categorized under Education and uses a remote streaming HTTP/SSE transport. In contrast, Openemis Pro belongs to Education using remote streaming HTTP/SSE transport. Select LearnWorlds when you need capabilities focused on education and Openemis Pro when you require tools for education.
Pings the configured instance and reports reachability. Performs a real login round-trip — if this passes, CRUD will work.
openemis_list_domains
Lists the curated OpenEMIS domains — Attendance, Assessment, Staff, Student, Institution, Schedule, Examination, Report — each with a one-line summary. The agent uses this to figure out *where* a question lives.
openemis_discover
Input: a topic string. Output: up to 30 endpoints relevant to that topic, drawn from the domain knowledge pack and the per-instance manifest. Keeps conversations small regardless of how large the underlying API is.
openemis_list_playbooks
Lists all 40 curated workflow playbooks with id, title, domain, and audience. The agent uses this to find the right step-by-step guide for a user-level task.
openemis_get_playbook
Input: a playbook id. Output: the full playbook — resources, ordered steps, guidance notes, and example queries.
openemis_get
Unified read tool. `{ resource, id?, params? }` — if `id` is present, fetches the singleton; otherwise lists with any combination of `_fields`, `_conditions`, `orderby`, `order`, `page`, `limit`, plus any ad-hoc filter key.
openemis_create
Create a new record. `{ resource, body }` — non-workflow resources only. Workflow-controlled resources (e.g. institution-staff-leave) are blocked and will redirect to the appropriate playbook.
openemis_update
Update an existing record by id. `{ resource, id, body }` — non-workflow resources only.
openemis_delete
Delete a record by id. `{ resource, id }` — non-workflow resources only.