Skip to main content
Glama
devlimelabs

MCP Troubleshooter

by devlimelabs

check-mcp-server-process

Verify the process status of an MCP server to diagnose and resolve operational issues. Input the server name to analyze logs, validate configurations, and ensure seamless functionality.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serverNameYesName of the MCP server to check

Implementation Reference

  • Full implementation of the 'check-mcp-server-process' tool handler. Reads Claude Desktop config, parses JSON to find server command, then uses platform-specific commands (tasklist on Windows, ps/grep on Unix) to check if the process is running and returns details or status.
    server.tool(
      "check-mcp-server-process",
      {
        serverName: z.string().describe("Name of the MCP server to check")
      },
      async ({ serverName }) => {
        try {
          // Read configuration to get the command for this server
          try {
            await fs.access(configPath);
          } catch (error) {
            return {
              content: [{ type: "text", text: `Configuration file not found at ${configPath}.` }]
            };
          }
    
          const configContent = await fs.readFile(configPath, 'utf-8');
          let configObject;
          
          try {
            configObject = JSON.parse(configContent);
          } catch (error) {
            return {
              isError: true,
              content: [{ type: "text", text: `Invalid JSON in configuration file: ${error.message}` }]
            };
          }
          
          if (!configObject.mcpServers || !configObject.mcpServers[serverName]) {
            return {
              content: [{ type: "text", text: `Server '${serverName}' not found in configuration.` }]
            };
          }
          
          const serverConfig = configObject.mcpServers[serverName];
          const command = serverConfig.command;
          
          if (!command) {
            return {
              content: [{ type: "text", text: `Server '${serverName}' has no command specified in configuration.` }]
            };
          }
          
          // Check if process is running (platform specific)
          const platform = os.platform();
          let processCheckCommand;
          
          if (platform === "win32") {
            processCheckCommand = `tasklist /FI "IMAGENAME eq ${command}*"`;
          } else {
            processCheckCommand = `ps aux | grep "${command}" | grep -v grep`;
          }
          
          try {
            const { stdout } = await execAsync(processCheckCommand);
            
            if (stdout.trim()) {
              // Process is likely running
              return {
                content: [{ 
                  type: "text", 
                  text: `Process for server '${serverName}' appears to be running.\n\nProcess details:\n\`\`\`\n${stdout}\n\`\`\`` 
                }]
              };
            } else {
              return {
                content: [{ type: "text", text: `No running process found for server '${serverName}'.` }]
              };
            }
          } catch (error) {
            // Process not found or error checking
            return {
              content: [{ 
                type: "text", 
                text: `No running process found for server '${serverName}', or error checking process: ${error.message}` 
              }]
            };
          }
        } catch (error) {
          return {
            isError: true,
            content: [{ type: "text", text: `Error checking server process: ${error.message}` }]
          };
        }
      }
    );
  • Input schema for the tool using Zod: requires 'serverName' string parameter.
    {
      serverName: z.string().describe("Name of the MCP server to check")
    },
  • src/index.ts:560-644 (registration)
    Registers the tool on the MCP server instance with name, schema, and handler.
      "check-mcp-server-process",
      {
        serverName: z.string().describe("Name of the MCP server to check")
      },
      async ({ serverName }) => {
        try {
          // Read configuration to get the command for this server
          try {
            await fs.access(configPath);
          } catch (error) {
            return {
              content: [{ type: "text", text: `Configuration file not found at ${configPath}.` }]
            };
          }
    
          const configContent = await fs.readFile(configPath, 'utf-8');
          let configObject;
          
          try {
            configObject = JSON.parse(configContent);
          } catch (error) {
            return {
              isError: true,
              content: [{ type: "text", text: `Invalid JSON in configuration file: ${error.message}` }]
            };
          }
          
          if (!configObject.mcpServers || !configObject.mcpServers[serverName]) {
            return {
              content: [{ type: "text", text: `Server '${serverName}' not found in configuration.` }]
            };
          }
          
          const serverConfig = configObject.mcpServers[serverName];
          const command = serverConfig.command;
          
          if (!command) {
            return {
              content: [{ type: "text", text: `Server '${serverName}' has no command specified in configuration.` }]
            };
          }
          
          // Check if process is running (platform specific)
          const platform = os.platform();
          let processCheckCommand;
          
          if (platform === "win32") {
            processCheckCommand = `tasklist /FI "IMAGENAME eq ${command}*"`;
          } else {
            processCheckCommand = `ps aux | grep "${command}" | grep -v grep`;
          }
          
          try {
            const { stdout } = await execAsync(processCheckCommand);
            
            if (stdout.trim()) {
              // Process is likely running
              return {
                content: [{ 
                  type: "text", 
                  text: `Process for server '${serverName}' appears to be running.\n\nProcess details:\n\`\`\`\n${stdout}\n\`\`\`` 
                }]
              };
            } else {
              return {
                content: [{ type: "text", text: `No running process found for server '${serverName}'.` }]
              };
            }
          } catch (error) {
            // Process not found or error checking
            return {
              content: [{ 
                type: "text", 
                text: `No running process found for server '${serverName}', or error checking process: ${error.message}` 
              }]
            };
          }
        } catch (error) {
          return {
            isError: true,
            content: [{ type: "text", text: `Error checking server process: ${error.message}` }]
          };
        }
      }
    );
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/devlimelabs/mcp-troubleshooter-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server