Skip to main content
Glama
devlimelabs

MCP Environment & Installation Manager

by devlimelabs

update-mcp

Update MCP server packages to specific versions, managing dependencies and configurations for the environment and installation manager.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packageNameYesPackage name to update
versionNoSpecific version to update to

Implementation Reference

  • Registration of the 'update-mcp' MCP tool, including Zod input schema (packageName, optional version) and handler that validates input and calls PackageManager.updatePackage, returning JSON result.
    server.tool(
      "update-mcp",
      {
        packageName: z.string().describe("Package name to update"),
        version: z.string().optional().describe("Specific version to update to")
      },
      async ({ packageName, version }, extra) => {
        if (!packageName.trim()) {
          throw new Error("Package name cannot be empty");
        }
        
        const result = await packageManager.updatePackage(packageName, version);
        
        if (!result.success) {
          throw new Error(`Failed to update package: ${result.error}`);
        }
        
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify({
                success: true,
                packageName: result.packageName,
                version: result.version,
                localPath: result.localPath
              }, null, 2)
            }
          ]
        };
      }
    );
  • MCP tool handler for 'update-mcp': validates packageName, calls packageManager.updatePackage(), handles errors, returns structured content response.
        if (!packageName.trim()) {
          throw new Error("Package name cannot be empty");
        }
        
        const result = await packageManager.updatePackage(packageName, version);
        
        if (!result.success) {
          throw new Error(`Failed to update package: ${result.error}`);
        }
        
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify({
                success: true,
                packageName: result.packageName,
                version: result.version,
                localPath: result.localPath
              }, null, 2)
            }
          ]
        };
      }
    );
  • Zod schema for 'update-mcp' tool parameters: required packageName (string), optional version (string).
      packageName: z.string().describe("Package name to update"),
      version: z.string().optional().describe("Specific version to update to")
    },
  • PackageManager.updatePackage(): core implementation that updates package via exec install command, refreshes metadata (version, binPath), updates registry. Falls back to install if not existing.
    /**
     * Updates an installed package
     * @param packageName Package name to update
     * @param version Optional target version
     */
    async updatePackage(packageName: string, version?: string): Promise<InstallResult> {
      const existing = this.getInstalledPackage(packageName);
      if (!existing) {
        return this.installPackage(packageName, version);
      }
      
      try {
        const packageDir = path.dirname(path.dirname(existing.localPath));
        
        // Update the package
        const updateCmd = this.getInstallCommand(packageName, version);
        await exec(updateCmd, { cwd: packageDir });
        
        // Get installed version
        const nodeModulesDir = path.join(packageDir, 'node_modules');
        const installedVersion = await this.getInstalledVersion(nodeModulesDir, packageName);
        
        // Find bin path if it exists
        const binPath = await this.findPackageBin(nodeModulesDir, packageName);
        
        // Update registry
        const now = new Date().toISOString();
        const localPath = path.join(nodeModulesDir, packageName);
        
        this.registry.packages[packageName] = {
          ...existing,
          version: installedVersion,
          localPath,
          binPath,
          updatedAt: now
        };
        
        await this.saveRegistry();
        
        return {
          success: true,
          packageName,
          version: installedVersion,
          localPath,
          binPath
        };
      } catch (error) {
        return {
          success: false,
          packageName,
          version: version || 'latest',
          localPath: existing.localPath,
          error: error instanceof Error ? error.message : String(error)
        };
      }
    }
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