Skip to main content
Glama
aledlie

Doppler MCP Server

by aledlie

doppler_secrets_get

Retrieve secret values from Doppler's secure secrets management system by specifying the secret name, with optional project and config parameters for targeted access.

Instructions

Get a secret value from Doppler

Input Schema

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

Implementation Reference

  • Specific implementation logic for the doppler_secrets_get tool: builds the CLI command 'doppler secrets get <name> [--project <project>] [--config <config>] --json'
    case "doppler_secrets_get":
      parts.push("secrets", "get", getString("name")!);
      if (getString("project")) parts.push("--project", getString("project")!);
      if (getString("config")) parts.push("--config", getString("config")!);
      parts.push("--json");
      break;
  • Input schema and metadata definition for the doppler_secrets_get tool.
    {
      name: "doppler_secrets_get",
      description: "Get a secret value from Doppler",
      inputSchema: {
        type: "object",
        properties: {
          name: {
            type: "string",
            description: "The name of the secret to retrieve",
          },
          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"],
      },
    },
  • src/index.ts:27-31 (registration)
    Registers the listTools request handler, which provides the tool definitions including doppler_secrets_get.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: toolDefinitions,
      };
    });
  • src/index.ts:34-51 (registration)
    Registers the generic callTool request handler that dispatches doppler_secrets_get calls to the executeCommand function.
    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}`);
      }
    });
  • Core helper function that executes the built Doppler CLI command for doppler_secrets_get and parses the output.
    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 full burden for behavioral disclosure but offers minimal information. It states the tool retrieves a secret value but doesn't cover critical aspects like authentication requirements, rate limits, error handling, or what happens if the secret doesn't exist. For a secrets management tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 at just 6 words, front-loading the core purpose without any wasted language. Every word earns its place by directly communicating the tool's function, making it easy to parse quickly.

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 secrets management (sensitive operations) and the absence of both annotations and an output schema, the description is insufficiently complete. It doesn't address security implications, return format, error conditions, or how it differs from sibling tools. For a tool with 3 parameters and no structured behavioral hints, more context is needed.

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 schema description coverage is 100%, with all parameters clearly documented in the schema itself. The description adds no additional parameter semantics beyond what's already in the schema (e.g., it doesn't explain format requirements for 'name' or clarify the relationship between 'project' and 'config'). This meets the baseline for high schema coverage but doesn't provide extra value.

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 ('Get') and resource ('a secret value from Doppler'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like doppler_secrets_list (which lists secrets) or doppler_secrets_set (which sets secrets), missing the opportunity to clarify this is specifically for retrieving a single secret's value.

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_list for browsing secrets or doppler_secrets_set for modifying them, nor does it explain prerequisites like authentication or setup requirements beyond what's implied in the schema.

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