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}`);
      }
    });
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 mentions authentication ('authenticated Doppler user'), which hints at security context, but fails to describe key traits like whether this is a read-only operation, potential rate limits, error conditions, or the format of returned information. This leaves significant gaps for an agent to understand how to handle the tool effectively.

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, clear sentence that directly states the tool's purpose without any fluff or redundancy. It is front-loaded with the essential information, making it highly efficient and easy to parse for an AI agent.

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 simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks details on behavioral aspects like response format, error handling, or authentication requirements. For a tool that likely returns user data, more context on what information is provided would enhance completeness, though the absence of an output schema partially excuses this gap.

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?

The tool has 0 parameters, and the schema description coverage is 100%, so there are no parameters to document. The description appropriately doesn't add unnecessary param details, earning a high baseline score. However, it doesn't explicitly state the lack of parameters, which could slightly improve clarity, preventing a perfect 5.

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 tool's purpose with a specific verb ('Get') and resource ('information about the current authenticated Doppler user'), making it easy to understand what it does. However, it doesn't explicitly differentiate itself from potential sibling tools like 'doppler_projects_list' or 'doppler_secrets_list' that might also return user-related information, preventing 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 Guidelines3/5

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

The description implies usage by specifying 'current authenticated Doppler user,' suggesting it should be used when user identity or details are needed. However, it provides no explicit guidance on when to use this tool versus alternatives (e.g., for authentication checks vs. other user-related operations) or any prerequisites, leaving some ambiguity.

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