Skip to main content
Glama
aledlie

Doppler MCP Server

by aledlie

doppler_projects_create

Create a new project in Doppler for organizing and managing secrets across your applications and environments.

Instructions

Create a new Doppler project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the project to create
descriptionNoOptional description for the project

Implementation Reference

  • Handler logic specific to 'doppler_projects_create': builds the CLI command 'doppler projects create <name> [--description <desc>] --json' and executes it via execSync.
    case "doppler_projects_create":
      parts.push("projects", "create", getString("name")!);
      if (getString("description")) parts.push("--description", getString("description")!);
      parts.push("--json");
      break;
  • Tool definition including name, description, and input schema for creating a Doppler project (required: name; optional: description).
    {
      name: "doppler_projects_create",
      description: "Create a new Doppler project",
      inputSchema: {
        type: "object",
        properties: {
          name: {
            type: "string",
            description: "The name of the project to create",
          },
          description: {
            type: "string",
            description: "Optional description for the project",
          },
        },
        required: ["name"],
      },
    },
  • src/index.ts:27-31 (registration)
    Registers the 'doppler_projects_create' tool (among others) by including it in toolDefinitions returned for ListToolsRequest.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: toolDefinitions,
      };
    });
  • Core handler function that executes the built Doppler CLI command for any tool, including 'doppler_projects_create', via child_process.execSync and parses output as JSON.
    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}`);
      }
    }
  • src/index.ts:34-51 (registration)
    MCP server request handler for CallToolRequest that dispatches to executeCommand based on tool name, used to invoke 'doppler_projects_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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Create' implies a mutation operation, the description doesn't specify permissions required, whether the operation is idempotent, rate limits, or what happens on failure (e.g., duplicate project names). For a creation 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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and wastes no space, making it easy for an agent to parse quickly. Every word earns its place by conveying essential information.

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 creation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address behavioral aspects like error handling, authentication requirements, or return values. While the schema covers parameters well, the overall context for safe and effective use is lacking, especially for a mutation operation.

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 description adds no parameter semantics beyond what the input schema provides. With 100% schema description coverage, the schema already documents both parameters ('name' and 'description') clearly. The baseline score of 3 reflects adequate coverage by the schema, but the description doesn't enhance understanding with examples, constraints, or contextual usage.

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 ('Create') and resource ('new Doppler project'), making the purpose immediately understandable. It distinguishes from sibling tools like 'doppler_projects_list' by specifying creation rather than listing. However, it doesn't explicitly differentiate from other creation tools like 'doppler_configs_create', which would require mentioning project-specific context.

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., authentication needs), when not to use it, or how it relates to sibling tools like 'doppler_projects_list' for checking existing projects before creation. The agent must infer usage from the tool name alone.

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