Reactive Resume vs Ttctl — MCP Server Comparison | AllMCPs
Reactive Resume vs Ttctl
A side-by-side look at the Reactive Resume and Ttctl MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Reactive Resume for workplace & productivity work over a hosted endpoint; choose Ttctl for workplace & productivity as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Reactive Resume when
You need dedicated capabilities in the Workplace & Productivity domain.
No tool names declared yet. Check the project README from the listing page.
Ttctl 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.
Reactive Resume is categorized under Workplace & Productivity and uses a remote HTTP/SSE transport. Ttctl belongs to Workplace & Productivity and uses a local stdio subprocess. Pick Reactive Resume for workplace & productivity work and Ttctl for workplace & productivity.
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.
Reactive Resume has no declared pricing — check the project's own site. Ttctl is listed as free. Auth: other. 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 reactive-resume-2 and ttctl as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Reactive Resume has a quality signal of 48/100 (Fair) with 1 views, 0 installs and 44,327 GitHub stars. Ttctl has 44/100 (Fair) with 3 views, 0 installs and 0 GitHub stars.