Skip to main content
Glama
devlimelabs

MCP Environment & Installation Manager

by devlimelabs

configure-watcher

Monitor and automatically update Claude for Desktop and Cursor configuration files when changes occur, ensuring development environments stay synchronized.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
watchClaudeNoWhether to watch Claude for Desktop config
watchCursorNoWhether to watch Cursor config
claudeConfigPathNoPath to Claude for Desktop config file
cursorConfigPathNoPath to Cursor config file

Implementation Reference

  • Registers the configure-watcher tool with MCP server, including schema and inline handler function.
    server.tool(
      "configure-watcher",
      {
        watchClaude: z.boolean().optional().describe("Whether to watch Claude for Desktop config"),
        watchCursor: z.boolean().optional().describe("Whether to watch Cursor config"),
        claudeConfigPath: z.string().optional().describe("Path to Claude for Desktop config file"),
        cursorConfigPath: z.string().optional().describe("Path to Cursor config file")
      },
      async ({ watchClaude, watchCursor, claudeConfigPath, cursorConfigPath }, extra) => {
        const config = configService.getInstallationConfig();
        
        const updates = {
          watchers: {
            ...config.watchers
          }
        };
        
        if (watchClaude !== undefined) {
          updates.watchers.claude = {
            ...config.watchers.claude,
            enabled: watchClaude
          };
        }
        
        if (watchCursor !== undefined) {
          updates.watchers.cursor = {
            ...config.watchers.cursor,
            enabled: watchCursor
          };
        }
        
        if (claudeConfigPath !== undefined) {
          updates.watchers.claude = {
            ...config.watchers.claude,
            configPath: claudeConfigPath
          };
        }
        
        if (cursorConfigPath !== undefined) {
          updates.watchers.cursor = {
            ...config.watchers.cursor,
            configPath: cursorConfigPath
          };
        }
        
        const updatedConfig = await configService.updateInstallationConfig(updates);
        
        // Reinitialize watchers with new config
        await watcherService.initializeWatchers();
        
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify({
                success: true,
                watchers: updatedConfig.watchers
              }, null, 2)
            }
          ]
        };
      }
    );
  • The main handler logic for the configure-watcher tool: updates watcher configurations in installation config and reinitializes watchers via services.
    async ({ watchClaude, watchCursor, claudeConfigPath, cursorConfigPath }, extra) => {
      const config = configService.getInstallationConfig();
      
      const updates = {
        watchers: {
          ...config.watchers
        }
      };
      
      if (watchClaude !== undefined) {
        updates.watchers.claude = {
          ...config.watchers.claude,
          enabled: watchClaude
        };
      }
      
      if (watchCursor !== undefined) {
        updates.watchers.cursor = {
          ...config.watchers.cursor,
          enabled: watchCursor
        };
      }
      
      if (claudeConfigPath !== undefined) {
        updates.watchers.claude = {
          ...config.watchers.claude,
          configPath: claudeConfigPath
        };
      }
      
      if (cursorConfigPath !== undefined) {
        updates.watchers.cursor = {
          ...config.watchers.cursor,
          configPath: cursorConfigPath
        };
      }
      
      const updatedConfig = await configService.updateInstallationConfig(updates);
      
      // Reinitialize watchers with new config
      await watcherService.initializeWatchers();
      
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({
              success: true,
              watchers: updatedConfig.watchers
            }, null, 2)
          }
        ]
      };
    }
  • Zod schema defining optional boolean flags for enabling watchers and optional string paths for config files.
    {
      watchClaude: z.boolean().optional().describe("Whether to watch Claude for Desktop config"),
      watchCursor: z.boolean().optional().describe("Whether to watch Cursor config"),
      claudeConfigPath: z.string().optional().describe("Path to Claude for Desktop config file"),
      cursorConfigPath: z.string().optional().describe("Path to Cursor config file")
    },
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

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-env-manager-mcp'

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