Skip to main content
Glama
devlimelabs

MCP Environment & Installation Manager

by devlimelabs

install-mcp

Install MCP server packages to extend functionality, specifying package names and optional versions for automated setup.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packageNameYesPackage name to install
versionNoSpecific version to install

Implementation Reference

  • The MCP tool handler for 'install-mcp', registered inline with server.tool(). Validates input, calls PackageManager.installPackage(), handles errors, and returns structured success/error response.
    server.tool(
      "install-mcp",
      {
        packageName: z.string().describe("Package name to install"),
        version: z.string().optional().describe("Specific version to install")
      },
      async ({ packageName, version }, extra) => {
        if (!packageName.trim()) {
          throw new Error("Package name cannot be empty");
        }
        
        const result = await packageManager.installPackage(packageName, version);
        
        if (!result.success) {
          throw new Error(`Failed to install package: ${result.error}`);
        }
        
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify({
                success: true,
                packageName: result.packageName,
                version: result.version,
                localPath: result.localPath
              }, null, 2)
            }
          ]
        };
      }
    );
  • src/server.ts:33-33 (registration)
    Top-level call to register installation tools including 'install-mcp' on the MCP server instance.
    registerInstallationTools(server, configService, packageManager);
  • Core implementation of package installation in PackageManager class: creates directory, sets up package.json, executes npm/yarn/pnpm install, discovers version/bin path, updates registry, handles errors.
    async installPackage(packageName: string, version?: string): Promise<InstallResult> {
      try {
        // Create package-specific directory
        const packageDir = path.join(this.packagesDir, packageName.replace('/', '-'));
        await ensureDir(packageDir);
        
        // Create package.json if it doesn't exist
        const packageJsonPath = path.join(packageDir, 'package.json');
        if (!(await fileExists(packageJsonPath))) {
          await writeJsonFile(packageJsonPath, {
            name: 'mcp-package-wrapper',
            version: '1.0.0',
            private: true,
            type: 'module'
          });
        }
        
        // Install the package
        const installCmd = this.getInstallCommand(packageName, version);
        await exec(installCmd, { 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);
        
        // Add to registry
        const now = new Date().toISOString();
        const localPath = path.join(nodeModulesDir, packageName);
        
        const installedPackage: InstalledPackage = {
          name: packageName,
          version: installedVersion,
          localPath,
          binPath,
          installedAt: now,
          updatedAt: now,
          dependencies: [], // TODO: Extract dependencies
          usedByConfigs: []
        };
        
        this.registry.packages[packageName] = installedPackage;
        await this.saveRegistry();
        
        return {
          success: true,
          packageName,
          version: installedVersion,
          localPath,
          binPath
        };
      } catch (error) {
        return {
          success: false,
          packageName,
          version: version || 'latest',
          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