Skip to main content
Glama
devlimelabs

MCP Environment & Installation Manager

by devlimelabs

uninstall-mcp

Remove MCP server packages from your environment. Specify a package name to uninstall it, optionally forcing removal even if referenced by configurations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packageNameYesPackage name to uninstall
forceNoForce uninstallation even if referenced by configs

Implementation Reference

  • Registration of the 'uninstall-mcp' MCP tool, including input schema (packageName, optional force) and the inline handler function that performs validation, safety checks, uninstallation via PackageManager, and structured response.
    server.tool(
      "uninstall-mcp",
      {
        packageName: z.string().describe("Package name to uninstall"),
        force: z.boolean().optional().describe("Force uninstallation even if referenced by configs")
      },
      async ({ packageName, force = false }, extra) => {
        if (!packageName.trim()) {
          throw new Error("Package name cannot be empty");
        }
        
        const pkg = packageManager.getInstalledPackage(packageName);
        
        if (!pkg) {
          throw new Error(`Package not installed: ${packageName}`);
        }
        
        // Check if package is used by any configs
        if (pkg.usedByConfigs.length > 0 && !force) {
          throw new Error(`Package is used by ${pkg.usedByConfigs.length} configurations. Use force=true to override.`);
        }
        
        const success = await packageManager.uninstallPackage(packageName);
        
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify({
                success,
                packageName
              }, null, 2)
            }
          ]
        };
      }
    );
  • PackageManager.uninstallPackage helper method invoked by the tool handler. Executes package manager remove command, cleans up registry entry, returns success boolean.
    async uninstallPackage(packageName: string): Promise<boolean> {
      const existing = this.getInstalledPackage(packageName);
      if (!existing) {
        return false;
      }
      
      try {
        const packageDir = path.dirname(path.dirname(existing.localPath));
        
        // Uninstall the package
        const uninstallCmd = `${this.preferredPackageManager} remove ${packageName}`;
        await exec(uninstallCmd, { cwd: packageDir });
        
        // Remove from registry
        delete this.registry.packages[packageName];
        await this.saveRegistry();
        
        return true;
      } catch (error) {
        console.error(`Failed to uninstall package ${packageName}:`, error);
        return false;
      }
    }
  • src/server.ts:33-33 (registration)
    Top-level call to registerInstallationTools function during server initialization, which includes registration of the 'uninstall-mcp' tool.
    registerInstallationTools(server, configService, packageManager);
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