MCP: HashiCorp Vault MCP Server
by HashiCorp
HashiCorp's official MCP server for Vault: manage secret engine mounts, read and write KV secrets, and drive the PKI engine — issuers, roles and certificates — from an agent.
Doppler's official MCP server — let an agent list projects, read and write secrets, manage configs and review activity logs, scoped by the token you give it.
Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.
Doppler is a secrets manager: one place to hold API keys, database URLs and other credentials, and sync them into every environment that needs them. The official Doppler MCP server (@dopplerhq/mcp-server, Apache-2.0) puts that store behind an agent's tool calls, so a coding assistant can answer "which config is this service reading?" or add a new secret to a staging config without you leaving the editor.
What it exposes. Listing projects, configs and secrets; reading secret values and downloading a whole config; creating and updating secrets; managing environments and configs; and reading the activity log. Which of those an agent can actually reach depends on two things you control: the --read-only flag, which drops every write tool, and the scope of the token itself.
Authentication. Run npx @dopplerhq/mcp-server login once for an interactive browser login, or pass a DOPPLER_TOKEN service token in the client config for CI and shared machines. Doppler is explicit that the token is where real access control lives — --read-only hides the write tools but does not stop a determined agent from finding another route, so scope the token to exactly the projects and configs you intend to expose.
Worth knowing before you wire it into production. Doppler ships this as experimental, intended for development, testing and evaluation. Model output is non-deterministic, so treat anything the agent does against real secrets as something to review, not to trust blindly. --project and --config override the auto-detected pair when you want the agent pinned to one place.
by HashiCorp
HashiCorp's official MCP server for Vault: manage secret engine mounts, read and write KV secrets, and drive the PKI engine — issuers, roles and certificates — from an agent.
by Bitwarden
Bitwarden's official MCP server — unlock the vault, read and edit items, generate passwords and TOTP codes, and run organisation administration. Local use only.
by Cloudsmith
Cloudsmith's official MCP server, built into its CLI: manage artifact repositories, packages and policies through an agent, with write operations off by default.
by Fly.io
Fly.io's MCP server, built into flyctl — provision and inspect Fly apps from an agent, with subcommands that also deploy and proxy other MCP servers onto Fly machines.