A side-by-side look at the Inoh and Lukija MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Inoh for education work over a hosted endpoint; choose Lukija for education. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Inoh when
You need dedicated capabilities in the Education domain.
No tool names declared yet. Check the project README from the listing page.
Lukija 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.
No confirmed install command for Lukija yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Inoh is categorized under Education and uses a remote HTTP/SSE transport. Lukija belongs to Education and uses an install path we have not confirmed yet. Pick Inoh for education work and Lukija 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. Lukija has no confirmed install command yet — follow its own setup instructions.
Inoh has no declared pricing — check the project's own site. Lukija 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 inoh and lukija as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Inoh has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Lukija has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.