Skip to main content
Glama
devlimelabs

MCP Troubleshooter

by devlimelabs

update-mcp-config

Modify JSON configuration files for MCP server diagnostics to resolve issues, validate settings, and test connections. Essential for maintaining server performance and troubleshooting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
configYesJSON configuration to write (entire file content)

Implementation Reference

  • The handler function for the 'update-mcp-config' tool. Validates the input JSON string, backs up the existing Claude Desktop configuration file if it exists, ensures the config directory is present, writes the new configuration to the platform-specific path, and returns a success message or error details.
    async ({ config }) => {
      try {
        // Validate the JSON
        try {
          JSON.parse(config);
        } catch (error) {
          return {
            isError: true,
            content: [{ type: "text", text: `Invalid JSON configuration: ${error.message}` }]
          };
        }
    
        // Create backup of existing config if it exists
        try {
          const existingConfig = await fs.readFile(configPath, 'utf-8');
          const backupPath = `${configPath}.backup.${Date.now()}`;
          await fs.writeFile(backupPath, existingConfig);
        } catch (error) {
          // Ignore if no existing config
        }
    
        // Ensure directory exists
        await fs.mkdir(path.dirname(configPath), { recursive: true });
        
        // Write new config
        await fs.writeFile(configPath, config);
        
        return {
          content: [{ 
            type: "text", 
            text: `Configuration successfully updated at ${configPath}.\n\nNote: You'll need to restart Claude Desktop for changes to take effect.` 
          }]
        };
      } catch (error) {
        return {
          isError: true,
          content: [{ type: "text", text: `Error updating configuration: ${error.message}` }]
        };
      }
    }
  • The Zod input schema for the 'update-mcp-config' tool, defining a single 'config' parameter as a string containing the full JSON configuration to write to the file.
    {
      config: z.string().describe("JSON configuration to write (entire file content)")
    },
  • src/index.ts:326-371 (registration)
    The registration of the 'update-mcp-config' tool on the MCP server instance using server.tool(), specifying the tool name, input schema, and handler function.
    server.tool(
      "update-mcp-config",
      {
        config: z.string().describe("JSON configuration to write (entire file content)")
      },
      async ({ config }) => {
        try {
          // Validate the JSON
          try {
            JSON.parse(config);
          } catch (error) {
            return {
              isError: true,
              content: [{ type: "text", text: `Invalid JSON configuration: ${error.message}` }]
            };
          }
    
          // Create backup of existing config if it exists
          try {
            const existingConfig = await fs.readFile(configPath, 'utf-8');
            const backupPath = `${configPath}.backup.${Date.now()}`;
            await fs.writeFile(backupPath, existingConfig);
          } catch (error) {
            // Ignore if no existing config
          }
    
          // Ensure directory exists
          await fs.mkdir(path.dirname(configPath), { recursive: true });
          
          // Write new config
          await fs.writeFile(configPath, config);
          
          return {
            content: [{ 
              type: "text", 
              text: `Configuration successfully updated at ${configPath}.\n\nNote: You'll need to restart Claude Desktop for changes to take effect.` 
            }]
          };
        } catch (error) {
          return {
            isError: true,
            content: [{ type: "text", text: `Error updating configuration: ${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