Skip to main content
Glama
aledlie

Doppler MCP Server

by aledlie

doppler_configs_list

Retrieve all configuration sets from a Doppler project to manage secrets across environments.

Instructions

List all configs in a Doppler project

Input Schema

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

Implementation Reference

  • Specific switch case implementing the logic for the 'doppler_configs_list' tool by building the corresponding Doppler CLI command.
    case "doppler_configs_list":
      parts.push("configs", "list");
      if (getString("project")) parts.push("--project", getString("project")!);
      parts.push("--json");
      break;
  • Input schema defining the parameters (project) for the 'doppler_configs_list' tool.
    inputSchema: {
      type: "object",
      properties: {
        project: {
          type: "string",
          description: "The Doppler project name (optional if set via doppler setup)",
        },
      },
    },
  • src/tools.ts:117-129 (registration)
    Tool registration object defining name, description, and input schema for 'doppler_configs_list' in the toolDefinitions array.
    {
      name: "doppler_configs_list",
      description: "List all configs in a Doppler project",
      inputSchema: {
        type: "object",
        properties: {
          project: {
            type: "string",
            description: "The Doppler project name (optional if set via doppler setup)",
          },
        },
      },
    },
  • Core handler function that executes the Doppler CLI command built for any tool, including 'doppler_configs_list', and handles output parsing and errors.
    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 this is a list operation, implying it's read-only and non-destructive, but doesn't explicitly confirm safety, describe pagination, rate limits, authentication needs, or return format. For a tool with zero annotation coverage, this leaves significant gaps in behavioral understanding.

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 with zero wasted words. It's appropriately sized for a simple list tool and front-loads the core purpose immediately.

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

Completeness3/5

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

Given the tool's low complexity (single optional parameter, list operation) and high schema coverage, the description is minimally adequate. However, with no annotations and no output schema, it should ideally provide more context about what 'configs' are and the return format to be fully complete for 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?

Schema description coverage is 100%, so the input schema already fully documents the single parameter. The description adds no additional meaning beyond what the schema provides (e.g., it doesn't explain what 'configs' are or provide context on the project parameter). Baseline 3 is appropriate when the schema does all the work.

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 ('List all configs') and resource ('in a Doppler project'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from its sibling 'doppler_configs_create', which would be needed for a perfect score.

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 like 'doppler_configs_create' or 'doppler_secrets_list'. It mentions the project parameter is optional if set via doppler setup, but this is already covered in the input schema description, so it doesn't add usage guidance beyond what's structured.

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