Skip to main content
Glama
aledlie

Doppler MCP Server

by aledlie

doppler_secrets_set

Set secret values in Doppler for secure configuration management. Specify secret name, value, project, and config to update your secrets store.

Instructions

Set a secret value in Doppler

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the secret to set
valueYesThe value to set for the secret
projectNoThe Doppler project name (optional if set via doppler setup)
configNoThe Doppler config name (optional if set via doppler setup)

Implementation Reference

  • Specific switch case implementing the logic for the doppler_secrets_set tool by constructing the Doppler CLI command: doppler secrets set name=value [--project proj] [--config config] --json
    case "doppler_secrets_set":
      parts.push("secrets", "set", `${getString("name")}=${getString("value")}`);
      if (getString("project")) parts.push("--project", getString("project")!);
      if (getString("config")) parts.push("--config", getString("config")!);
      parts.push("--json");
      break;
  • Input schema definition for the doppler_secrets_set tool, specifying required name and value, optional project and config.
    {
      name: "doppler_secrets_set",
      description: "Set a secret value in Doppler",
      inputSchema: {
        type: "object",
        properties: {
          name: {
            type: "string",
            description: "The name of the secret to set",
          },
          value: {
            type: "string",
            description: "The value to set for the secret",
          },
          project: {
            type: "string",
            description: "The Doppler project name (optional if set via doppler setup)",
          },
          config: {
            type: "string",
            description: "The Doppler config name (optional if set via doppler setup)",
          },
        },
        required: ["name", "value"],
      },
    },
  • src/index.ts:27-31 (registration)
    Tool list registration handler that exposes the doppler_secrets_set tool (via toolDefinitions) to MCP clients.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: toolDefinitions,
      };
    });
  • src/index.ts:34-51 (registration)
    Central callTool request handler that registers execution capability for all tools, including doppler_secrets_set, by dispatching to executeCommand(name, args).
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      const { name, arguments: args } = request.params;
    
      try {
        const result = await executeCommand(name, args || {});
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : String(error);
        throw new McpError(ErrorCode.InternalError, `Doppler CLI error: ${errorMessage}`);
      }
    });
  • Helper function executeCommand that runs the constructed Doppler CLI command using execSync, handles output parsing, and error handling.
    export async function executeCommand(
      toolName: string,
      args: DopplerArgs
    ): Promise<any> {
      const command = buildDopplerCommand(toolName, args);
    
      try {
        const output = execSync(command, {
          encoding: "utf-8",
          stdio: ["pipe", "pipe", "pipe"],
          maxBuffer: 10 * 1024 * 1024, // 10MB buffer
        });
    
        // Try to parse as JSON, if it fails return raw output
        try {
          return JSON.parse(output);
        } catch {
          return { output: output.trim() };
        }
      } catch (error: any) {
        // Handle execution errors
        const stderr = error.stderr?.toString() || "";
        const stdout = error.stdout?.toString() || "";
        const message = stderr || stdout || error.message;
        throw new Error(`Doppler CLI command failed: ${message}`);
      }
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal information. It states the tool sets a secret value, implying a write/mutation operation, but doesn't cover critical aspects like authentication requirements, rate limits, idempotency (e.g., whether it creates or updates), error handling, or side effects. This leaves significant gaps for a tool that modifies data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise—a single sentence that directly states the tool's purpose without any fluff. It's front-loaded and wastes no words, making it easy for an agent to parse quickly. Every part of the sentence earns its place by conveying the core functionality.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a write operation (setting secrets) with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits (e.g., permissions, idempotency), output format, error cases, and usage context. While the schema covers parameters well, the overall context for safe and effective tool invocation is insufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, so the schema already documents all parameters (name, value, project, config) thoroughly. The description adds no additional parameter semantics beyond what's in the schema, such as format examples or constraints. With high schema coverage, a baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't need to given the schema's completeness.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Set') and resource ('a secret value in Doppler'), making the purpose immediately understandable. It distinguishes from siblings like doppler_secrets_get (retrieve) and doppler_secrets_delete (remove), though it doesn't explicitly name these alternatives. The description is specific but could be slightly more precise about what 'set' entails (e.g., create or update).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to choose this over doppler_secrets_get for retrieval, doppler_secrets_delete for removal, or other secret management tools. There's no context about prerequisites, error conditions, or typical use cases, leaving the agent with minimal usage direction.

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/aledlie/doppler-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server