Skip to main content
Glama
aledlie

Doppler MCP Server

by aledlie

doppler_me

Retrieve authenticated user details from Doppler's secrets management platform for identity verification and access control.

Instructions

Get information about the current authenticated Doppler user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Schema definition including name, description, and empty input schema for the doppler_me tool.
      {
        name: "doppler_me",
        description: "Get information about the current authenticated Doppler user",
        inputSchema: {
          type: "object",
          properties: {},
        },
      },
    ];
  • Specific handler logic for doppler_me within buildDopplerCommand: constructs and prepares the 'doppler me --json' CLI command for execution.
    case "doppler_me":
      parts.push("me");
      parts.push("--json");
      break;
  • Core handler function that executes the Doppler CLI command built for doppler_me (and other tools) using 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:27-31 (registration)
    Registers all tools, including doppler_me, by returning toolDefinitions in response to ListToolsRequest.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: toolDefinitions,
      };
    });
  • src/index.ts:34-51 (registration)
    Registers the generic CallToolRequest handler that dispatches tool execution to executeCommand based on the tool name 'doppler_me'.
    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}`);
      }
    });

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden for behavioral disclosure. It doesn't state whether this tool verifies authentication validity, what happens with an invalid/expired token, whether it makes network calls, or what level of detail about the user is returned. For a tool that is effectively an auth-check/identity endpoint, this is thin disclosure.

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?

Single sentence, zero waste. Every word earns its place. For a zero-parameter tool, this is the appropriate length—there is nothing more to say about parameters or invocation.

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?

With 0 parameters, no output schema, and no annotations, the tool is simple enough that the short description is largely adequate. However, because there's no output schema or annotations, some disclosure about what identity fields are returned (email, name, org roles, etc.) and auth failure behavior would strengthen completeness for a tool serving as an auth-context operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has 0 parameters, and schema description coverage is 100% (the schema has no properties). With no parameters to document, the baseline of 4 applies—there is nothing the description needs to add, and the empty schema is correct. No param semantics gap exists.

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?

Clear specific verb (Get) + resource (information about current authenticated Doppler user). Distinguishes itself from siblings which all target specific resources like secrets, projects, configs, and environments. A 'me' pattern is recognizable from similar authed-user endpoints in other APIs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The purpose implies it should be used to identify the current user or verify auth state, but there is no explicit when-to-use guidance. With 10 sibling tools dedicated to specific resources, there's no stated exclusion like 'use this to obtain user identity before calling other tools' or instructions about auth prerequisites for other functions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.