A side-by-side look at the Cubite LMS and Underlayer MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Cubite LMS for education work over a hosted endpoint; choose Underlayer for education over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
C
Choose Cubite LMS when
You need dedicated capabilities in the Education domain.
No tool names declared yet. Check the project README from the listing page.
Underlayer tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Cubite LMS is categorized under Education and uses a remote HTTP/SSE transport. Underlayer belongs to Education and uses a remote HTTP/SSE transport. Pick Cubite LMS for education work and Underlayer for education.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Cubite LMS has no declared pricing — check the project's own site. Underlayer has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add cubite-lms and underlayer as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Cubite LMS has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Underlayer has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.