Skip to main content
Glama
aledlie

Doppler MCP Server

by aledlie

doppler_secrets_list

Retrieve and display all secrets stored in a Doppler configuration to manage sensitive data access across your projects and environments.

Instructions

List all secrets in a Doppler config

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectNoThe Doppler project name (optional if set via doppler setup)
configNoThe Doppler config name (optional if set via doppler setup)

Implementation Reference

  • Specific handler logic for doppler_secrets_list tool: builds the CLI command 'doppler secrets list [--project X] [--config Y] --json'
    case "doppler_secrets_list":
      parts.push("secrets", "list");
      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_list tool
    {
      name: "doppler_secrets_list",
      description: "List all secrets in a Doppler config",
      inputSchema: {
        type: "object",
        properties: {
          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)",
          },
        },
      },
    },
  • src/index.ts:27-31 (registration)
    Registers the listTools handler, exposing the doppler_secrets_list tool definition
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: toolDefinitions,
      };
    });
  • MCP callTool request handler that dispatches to executeCommand based on tool name, handling the execution for doppler_secrets_list
    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 Doppler CLI command for all tools, including doppler_secrets_list, by running execSync on the built command and parsing 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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action but doesn't cover critical aspects like whether this is a read-only operation, if it requires authentication, what the output format looks like (e.g., list of secrets with metadata), or any rate limits. This leaves significant gaps for an agent to understand the tool's 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 a single, efficient sentence that directly states the tool's purpose without any wasted words. It's front-loaded and appropriately sized for a simple list operation, 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 lack of annotations and output schema, the description is incomplete for a tool that lists secrets. It doesn't explain what the output contains (e.g., secret names, values, metadata), how results are structured, or any behavioral constraints. For a tool with no structured support, this leaves too much unspecified for reliable agent use.

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, clearly documenting both optional parameters ('project' and 'config') as optional if set via 'doppler setup'. The description doesn't add any additional meaning beyond what the schema provides, such as explaining default behaviors or dependencies, so it meets the baseline for high schema coverage.

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 verb ('List') and resource ('all secrets in a Doppler config'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'doppler_secrets_get' (which presumably retrieves a single secret) or 'doppler_configs_list' (which lists configs rather than secrets).

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention sibling tools like 'doppler_secrets_get' for retrieving individual secrets or 'doppler_configs_list' for listing configs, nor does it specify prerequisites or context for usage beyond the basic action.

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