MCP Autostarter
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| restart_mcpA | Intelligently restarts only the MCP handler process without disrupting Claude Desktop UI |
| restart_claudeA | Fully restarts Claude Desktop application (use only if MCP restart fails) |
| get_mcp_statusB | Check if MCP handler and Claude Desktop processes are running |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.