Lumen vs TinyCTO — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Lumen vs TinyCTO
In-depth architectural comparison of the Lumen and TinyCTO 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
Lumen
Education · Remote HTTP/SSE
Quality: 41/100 (Fair) | Auth: No auth required
TinyCTO
Education · Local stdio
Quality: 43/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Lumen if you need specialized Education tools running via a hosted cloud SSE transport. Choose TinyCTO if your workspace requires Education integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Lumen when:
You need dedicated capabilities in the Education domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (BYOK (Pay Provider Direct)).
You have access to required keys: LUMEN_MCP_AUTH_TOKEN, DATABASE_URL.
Primary tools included: Nine MCP tools for learning workflows, Course-scoped RAG tutoring with citations, FSRS review management.
A free curriculum for CTOs and engineering leaders: 9 tracks, 81 lessons, sorted by company size. Also available as an MCP server for Claude Code, Claude Desktop, or ChatGPT.
Lumen is categorized under Education and uses a remote streaming HTTP/SSE transport. In contrast, TinyCTO belongs to Education using local stdio subprocess. Select Lumen when you need capabilities focused on education and TinyCTO when you require tools for education.