Skip to main content
Glama
devlimelabs

MCP Environment & Installation Manager

by devlimelabs

export-env-vars

Export environment variables from a specific profile in dotenv, JSON, or shell format for configuration management and deployment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profileIdYesProfile ID to export environment variables from
formatYesExport format (dotenv, json, or shell)

Implementation Reference

  • The main execution logic for the 'export-env-vars' tool. Fetches environment variables for the given profile, formats them according to the specified format (dotenv, json, or shell), and returns a JSON response with the formatted output.
    async ({ profileId, format }, extra) => {
      if (!profileId.trim()) {
        throw new Error("Profile ID cannot be empty");
      }
      
      const profile = configService.getProfile(profileId);
      if (!profile) {
        throw new Error(`Profile not found: ${profileId}`);
      }
      
      const envVars = configService.getEnvVars(profileId);
      
      let output = '';
      
      if (format === 'dotenv') {
        // .env format
        for (const [key, envVar] of Object.entries(envVars)) {
          // Add comment if description exists
          if (envVar.description) {
            output += `# ${envVar.description}\n`;
          }
          
          // Add the variable
          output += `${key}=${formatDotEnvValue(envVar.value)}\n`;
        }
      } else if (format === 'json') {
        // JSON format
        const jsonObj: Record<string, string> = {};
        
        for (const [key, envVar] of Object.entries(envVars)) {
          jsonObj[key] = envVar.value;
        }
        
        output = JSON.stringify(jsonObj, null, 2);
      } else if (format === 'shell') {
        // Shell export format
        for (const [key, envVar] of Object.entries(envVars)) {
          // Add comment if description exists
          if (envVar.description) {
            output += `# ${envVar.description}\n`;
          }
          
          // Add the variable
          output += `export ${key}=${formatShellValue(envVar.value)}\n`;
        }
      }
      
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({
              profileId,
              profileName: profile.name,
              format,
              output
            }, null, 2)
          }
        ]
      };
    }
  • Zod input schema defining parameters: profileId (string) and format (enum: 'dotenv', 'json', 'shell').
    {
      profileId: z.string().describe("Profile ID to export environment variables from"),
      format: z.enum(['dotenv', 'json', 'shell']).describe("Export format (dotenv, json, or shell)")
    },
  • src/server.ts:31-31 (registration)
    Top-level registration call that invokes the function registering the 'export-env-vars' tool (and other environment tools) on the MCP server.
    registerEnvironmentTools(server, configService);
  • Helper function to properly format environment variable values for .env files, escaping quotes if necessary.
    function formatDotEnvValue(value: string): string {
      // If value contains spaces, newlines, or quotes, wrap in quotes
      if (/[\s"']/g.test(value)) {
        return `"${value.replace(/"/g, '\\"')}"`;
      }
      
      return value;
    }
  • Helper function to format values for shell export commands, properly escaping single quotes.
    function formatShellValue(value: string): string {
      // Escape single quotes with '\'' pattern
      return `'${value.replace(/'/g, "'\\''")}'`;
    }
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