Skip to main content
Glama
aledlie

Doppler MCP Server

by aledlie

doppler_configs_create

Create a new configuration in a Doppler project for managing environment-specific secrets and settings.

Instructions

Create a new config in a Doppler project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the config to create
projectYesThe Doppler project name
environmentYesThe environment for the config (e.g., dev, staging, prod)

Implementation Reference

  • The switch case in buildDopplerCommand function that handles the "doppler_configs_create" tool by constructing the Doppler CLI command: doppler configs create <name> --project <project> --environment <environment> --json
    case "doppler_configs_create":
      parts.push("configs", "create", getString("name")!);
      parts.push("--project", getString("project")!);
      parts.push("--environment", getString("environment")!);
      parts.push("--json");
      break;
  • Input schema for the doppler_configs_create tool, specifying required parameters: name, project, and environment.
    inputSchema: {
      type: "object",
      properties: {
        name: {
          type: "string",
          description: "The name of the config to create",
        },
        project: {
          type: "string",
          description: "The Doppler project name",
        },
        environment: {
          type: "string",
          description: "The environment for the config (e.g., dev, staging, prod)",
        },
      },
      required: ["name", "project", "environment"],
    },
  • src/tools.ts:130-151 (registration)
    The tool definition object for "doppler_configs_create" included in the exported toolDefinitions array, used for MCP tool registration.
    {
      name: "doppler_configs_create",
      description: "Create a new config in a Doppler project",
      inputSchema: {
        type: "object",
        properties: {
          name: {
            type: "string",
            description: "The name of the config to create",
          },
          project: {
            type: "string",
            description: "The Doppler project name",
          },
          environment: {
            type: "string",
            description: "The environment for the config (e.g., dev, staging, prod)",
          },
        },
        required: ["name", "project", "environment"],
      },
    },
  • src/index.ts:27-31 (registration)
    MCP server request handler for listing tools, which returns the toolDefinitions array including doppler_configs_create.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: toolDefinitions,
      };
    });
  • MCP server request handler for calling tools, which invokes executeCommand with the tool name and arguments, handling the execution for all tools including doppler_configs_create.
    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}`);
      }
    });
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. It states this is a creation operation but doesn't mention any behavioral traits such as permissions required, whether it's idempotent, error conditions (e.g., duplicate names), or what happens upon success (e.g., returns a config object). This leaves significant gaps for a mutation tool.

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 fluff or redundant information. It's appropriately sized and front-loaded, 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 this is a mutation tool (create operation) with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects like authentication needs, error handling, or return values, which are critical for an AI agent to use it correctly. The high schema coverage helps with parameters, but overall context is lacking.

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 schema already documents all three parameters (name, project, environment) with clear descriptions. The description adds no additional parameter semantics beyond implying the tool creates a config, which aligns with the schema but doesn't provide extra context like format examples or constraints.

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 ('Create') and resource ('new config in a Doppler project'), making the purpose immediately understandable. It distinguishes from siblings like 'doppler_configs_list' (list vs create) but doesn't explicitly differentiate from 'doppler_projects_create' (creates projects vs configs) or 'doppler_secrets_set' (sets secrets vs creates configs).

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 prerequisites (e.g., needing an existing project), exclusions, or comparisons to sibling tools like 'doppler_secrets_set' for adding secrets to a config or 'doppler_configs_list' for viewing existing configs.

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