Skip to main content
Glama
devlimelabs

MCP Environment & Installation Manager

by devlimelabs

set-env-var

Set environment variables in MCP server profiles to configure applications and manage sensitive data securely across different deployment environments.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profileIdYesProfile ID to set environment variable in
keyYesEnvironment variable key
valueYesEnvironment variable value
sensitiveYesWhether the value is sensitive and should be encrypted
descriptionNoOptional description of the environment variable

Implementation Reference

  • Handler function that validates input parameters, checks profile existence, sets the environment variable using configService.setEnvVar, and returns a success response.
    async ({ profileId, key, value, sensitive, description }, extra) => {
      if (!profileId.trim()) {
        throw new Error("Profile ID cannot be empty");
      }
      
      if (!key.trim()) {
        throw new Error("Environment variable key cannot be empty");
      }
      
      const profile = configService.getProfile(profileId);
      if (!profile) {
        throw new Error(`Profile not found: ${profileId}`);
      }
      
      configService.setEnvVar(profileId, key, value, sensitive, description);
      
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({
              success: true,
              profileId,
              key,
              sensitive
            }, null, 2)
          }
        ]
      };
    }
  • Zod input schema defining parameters: profileId (string), key (string), value (string), sensitive (boolean), description (optional string).
    {
      profileId: z.string().describe("Profile ID to set environment variable in"),
      key: z.string().describe("Environment variable key"),
      value: z.string().describe("Environment variable value"),
      sensitive: z.boolean().describe("Whether the value is sensitive and should be encrypted"),
      description: z.string().optional().describe("Optional description of the environment variable")
    },
  • MCP server.tool registration for 'set-env-var', specifying the tool name, input schema, and handler function.
    server.tool(
      "set-env-var",
      {
        profileId: z.string().describe("Profile ID to set environment variable in"),
        key: z.string().describe("Environment variable key"),
        value: z.string().describe("Environment variable value"),
        sensitive: z.boolean().describe("Whether the value is sensitive and should be encrypted"),
        description: z.string().optional().describe("Optional description of the environment variable")
      },
      async ({ profileId, key, value, sensitive, description }, extra) => {
        if (!profileId.trim()) {
          throw new Error("Profile ID cannot be empty");
        }
        
        if (!key.trim()) {
          throw new Error("Environment variable key cannot be empty");
        }
        
        const profile = configService.getProfile(profileId);
        if (!profile) {
          throw new Error(`Profile not found: ${profileId}`);
        }
        
        configService.setEnvVar(profileId, key, value, sensitive, description);
        
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify({
                success: true,
                profileId,
                key,
                sensitive
              }, null, 2)
            }
          ]
        };
      }
    );
  • src/server.ts:31-31 (registration)
    Top-level call to registerEnvironmentTools, which registers the set-env-var tool among others.
    registerEnvironmentTools(server, configService);
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