Campus Cli vs Time Machine
A side-by-side look at the Campus Cli and Time Machine MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
T
Time MachineEducationAI-powered corporate learning platform — manage courses, users, and insights via Claude.37FairAuth: not declaredVerdict: choose Campus Cli for education work as a local process; choose Time Machine for education. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Campus Cli when
- You need dedicated capabilities in the Education domain.
- You prefer a local stdio subprocess transport.
TChoose Time Machine when
- You need dedicated capabilities in the Education domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | T Time Machine | |
|---|---|---|
| Category | Education | Education |
| Quality signal | 47/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 11 | — |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Campus Cli | View Time Machine |
Tools & capabilities
Campus Cli tools
No tool names declared yet. Check the project README from the listing page.
Time Machine 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.
Campus Cli
{
"mcpServers": {
"campus-cli": {
"command": "npx",
"args": [
"-y",
"campus-cli@2.2.3"
]
}
}
}
Time Machine
No confirmed install command for Time Machine yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Campus Cli is categorized under Education and uses a local stdio subprocess. Time Machine belongs to Education and uses an install path we have not confirmed yet. Pick Campus Cli for education work and Time Machine 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. Time Machine has no confirmed install command yet — follow its own setup instructions.
Campus Cli has no declared pricing — check the project's own site. Time Machine 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 campus-cli and time-machine as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Campus Cli has a quality signal of 47/100 (Fair) with 0 views, 0 installs and 11 GitHub stars. Time Machine has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.