Skip to main content
Glama
signalford

Doppler MCP Server

by signalford
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Doppler MCP Server

No user-submitted related servers found.

    Related Servers

    • Doppler MCP Server

      aledlie
      F
      license
      A
      quality
      D
      maintenance
      Enables secure secrets management through the Doppler CLI via natural language interactions. Supports managing secrets, projects, configs, and environments across different Doppler workspaces.
      11
      -
    • Doppler MCP Server by DopplerHQ

      Doppler MCP Serverofficial

      DopplerHQ
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to interact with the Doppler API for secrets management, including listing, retrieving, and updating secrets across projects and configs. Supports both read-only and full access modes with token-based authentication.
      1,475 npm
      7
      Apache 2.0

    • protonpass-mcp

      aureTheDev
      F
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server for Proton Pass. It wraps the official pass-cli binary and exposes 14 tools so any MCP-compatible AI assistant (Claude Desktop, Claude Code, etc.) can manage your vaults, credentials, and secrets.
      14
      -

    • Phantom Secrets MCP Server

      ashlrai
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding tools to securely manage secrets via MCP tools for vault operations, diagnostics, and cloud sync, ensuring real keys never enter the LLM context.
      16
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 11 tools

    Disambiguation4/5

    Tools are largely distinct by resource type (secrets, projects, configs, environments) and action (get, list, set, delete, create). The only minor overlap is doppler_run which touches secrets, but its purpose of injecting into a command is clearly distinct from directly getting secret values.

    Naming Consistency5/5

    All tools follow a consistent doppler_<resource>_<action> pattern (e.g., doppler_secrets_get, doppler_projects_list, doppler_configs_create). This is uniform and predictable across all 11 tools.

    Tool Count4/5

    11 tools is within the ideal 3-15 range and covers the core Doppler surface reasonably. A few related actions appear grouped (e.g., get/list/set/delete for secrets) which is appropriate. Not excessive or too thin for a secrets management server.

    Completeness3/5

    Secrets have full CRUD coverage (get, list, set, delete) which is good. However, there are notable gaps: no ability to update/delete configs or projects, no way to list roles/members, and doppler_run is useful but projects/configs lifecycle is incomplete (create exists but no delete or update).

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources