MCP Autostarter
Related Servers
Alternatives to MCP Autostarter
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceAn MCP server that bridges Claude Desktop with Claude Code, allowing users to delegate tasks to Claude Code directly from Claude Desktop conversations, supporting both synchronous and background execution with session reuse.7 npmMIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that lets you switch between different MCP configuration profiles directly from inside Claude Desktop.-
- FlicenseNot gradedqualityDmaintenanceAn MCP server that lets Claude manage long-running development processes across frameworks like Flutter, Next.js, Spring Boot, and Vite, with lifecycle control, log streaming, and hot reload support.1-
- AlicenseNot gradedqualityDmaintenanceA local MCP server that connects Claude Desktop to execute custom local code, such as generating custom greetings.5 npmISC
- AlicenseCqualityDmaintenanceMCP server for Claude Code self-management, enabling hot restart and context compaction commands.12MIT
- AlicenseNot gradedqualityDmaintenanceA production-ready MCP server with file management, HTTP requests, system info, and environment variable tools, plus a management UI and dual transport for Claude Desktop and Claude.ai.205 npmMIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose with no overlap. get_mcp_status checks process status, restart_claude restarts the full application, and restart_mcp restarts only the MCP handler. The descriptions explicitly differentiate when to use each tool.
All three tools follow a consistent verb_noun pattern (get_mcp_status, restart_claude, restart_mcp). The naming is perfectly uniform and predictable across the set.
Three tools is ideal for this focused domain of MCP/Claude Desktop process management. Each tool serves a specific, necessary function without redundancy or bloat.
The tool set provides complete coverage for the server's purpose: checking status (get_mcp_status) and restarting at both the MCP handler level (restart_mcp) and full application level (restart_claude). No gaps exist for this narrow scope.