HashiCorp
HashiCorp Secrets Engines MCP server
HashiCorp Secrets Engines MCP server
HashiCorp Secrets Engines MCP server
for Claude, ChatGPT, Cursor and your own agents
for Claude, ChatGPT, Cursor and your own agents
for Claude, ChatGPT, Cursor and your own agents
HashiCorp Secrets Engines MCP server
HashiCorp Secrets Engines MCP server
HashiCorp Secrets Engines MCP server
for Claude, ChatGPT, Cursor and your own agents
for Claude, ChatGPT, Cursor and your own agents
for Claude, ChatGPT, Cursor and your own agents
Expose HashiCorp Secrets Engines to Claude, ChatGPT, Cursor or your own agents as a governed MCP server, even if the vendor doesn’t ship one. Mindflow turns every API operation into an MCP tool and keeps the connector current when the API changes. The MCP Gateway sits between your AI clients and your data, with scoped access, human approval before sensitive writes and a record of every call.
Expose HashiCorp Secrets Engines to Claude, ChatGPT, Cursor or your own agents as a governed MCP server, even if the vendor doesn’t ship one. Mindflow turns every API operation into an MCP tool and keeps the connector current when the API changes. The MCP Gateway sits between your AI clients and your data, with scoped access, human approval before sensitive writes and a record of every call.
13
operation
s
available
Complete and up-to-date endpoint coverage by Mindflow.
Other services from this vendor:
13
operation
s
available
Complete and up-to-date endpoint coverage by Mindflow.
Other services from this vendor:
13
operation
s
available
Complete and up-to-date endpoint coverage by Mindflow.
Other services from this vendor:
Our customers scale automation with security built in.
Tools exposed by this MCP server
Every HashiCorp Secrets Engines operation, as an MCP tool
Every HashiCorp Secrets Engines operation, as an MCP tool
Each API operation becomes a tool your AI client can call. You decide which ones: allow reads, require approval before sensitive writes and block the rest. A few of the most used:
HashiCorp Secrets Engines
HashiCorp Secrets Engines
Configure backend settings for all keys
Configure backend settings for all keys
HashiCorp Secrets Engines
HashiCorp Secrets Engines
Kv v2 delete
Kv v2 delete
HashiCorp Secrets Engines
HashiCorp Secrets Engines
Kv v2 delete metadata and all versions
Kv v2 delete metadata and all versions
HashiCorp Secrets Engines
HashiCorp Secrets Engines
Kv v2 delete versions
Kv v2 delete versions
HashiCorp Secrets Engines
HashiCorp Secrets Engines
Kv v2 destroy versions
Kv v2 destroy versions
HashiCorp Secrets Engines
HashiCorp Secrets Engines
Kv v2 list
Kv v2 list
HashiCorp Secrets Engines
HashiCorp Secrets Engines
Kv v2 read
Kv v2 read
HashiCorp Secrets Engines
HashiCorp Secrets Engines
Kv v2 read metadata
Kv v2 read metadata
HashiCorp Secrets Engines
HashiCorp Secrets Engines
Kv v2 read subkeys
Kv v2 read subkeys
HashiCorp Secrets Engines
HashiCorp Secrets Engines
Kv v2 undelete versions
Kv v2 undelete versions
HashiCorp Secrets Engines
HashiCorp Secrets Engines
Kv v2 write
Kv v2 write
HashiCorp Secrets Engines
HashiCorp Secrets Engines
Kv v2 write metadata
Kv v2 write metadata
HashiCorp Secrets Engines
HashiCorp Secrets Engines
Read the backend level settings
Read the backend level settings
HashiCorp Secrets Engines
Configure backend settings for all keys
HashiCorp Secrets Engines
Kv v2 delete
HashiCorp Secrets Engines
Kv v2 delete metadata and all versions
HashiCorp Secrets Engines
Kv v2 delete versions
HashiCorp Secrets Engines
Kv v2 destroy versions
HashiCorp Secrets Engines
Kv v2 list
HashiCorp Secrets Engines
Kv v2 read
HashiCorp Secrets Engines
Kv v2 read metadata
HashiCorp Secrets Engines
Kv v2 read subkeys
HashiCorp Secrets Engines
Kv v2 undelete versions
HashiCorp Secrets Engines
Kv v2 write
HashiCorp Secrets Engines
Kv v2 write metadata
HashiCorp Secrets Engines
Read the backend level settings
HashiCorp Secrets Engines
HashiCorp Secrets Engines
Read the backend level settings
Read the backend level settings
HashiCorp Secrets Engines
HashiCorp Secrets Engines
Kv v2 write metadata
Kv v2 write metadata
HashiCorp Secrets Engines
HashiCorp Secrets Engines
Kv v2 write
Kv v2 write
HashiCorp Secrets Engines
HashiCorp Secrets Engines
Kv v2 undelete versions
Kv v2 undelete versions
HashiCorp Secrets Engines
HashiCorp Secrets Engines
Kv v2 read subkeys
Kv v2 read subkeys
HashiCorp Secrets Engines
HashiCorp Secrets Engines
Kv v2 read metadata
Kv v2 read metadata
HashiCorp Secrets Engines
HashiCorp Secrets Engines
Kv v2 read
Kv v2 read
HashiCorp Secrets Engines
HashiCorp Secrets Engines
Kv v2 list
Kv v2 list
HashiCorp Secrets Engines
HashiCorp Secrets Engines
Kv v2 destroy versions
Kv v2 destroy versions
HashiCorp Secrets Engines
HashiCorp Secrets Engines
Kv v2 delete versions
Kv v2 delete versions
HashiCorp Secrets Engines
HashiCorp Secrets Engines
Kv v2 delete metadata and all versions
Kv v2 delete metadata and all versions
HashiCorp Secrets Engines
HashiCorp Secrets Engines
Kv v2 delete
Kv v2 delete
HashiCorp Secrets Engines
HashiCorp Secrets Engines
Configure backend settings for all keys
Configure backend settings for all keys
HashiCorp Secrets Engines
Read the backend level settings
HashiCorp Secrets Engines
Kv v2 write metadata
HashiCorp Secrets Engines
Kv v2 write
HashiCorp Secrets Engines
Kv v2 undelete versions
HashiCorp Secrets Engines
Kv v2 read subkeys
HashiCorp Secrets Engines
Kv v2 read metadata
HashiCorp Secrets Engines
Kv v2 read
HashiCorp Secrets Engines
Kv v2 list
HashiCorp Secrets Engines
Kv v2 destroy versions
HashiCorp Secrets Engines
Kv v2 delete versions
HashiCorp Secrets Engines
Kv v2 delete metadata and all versions
HashiCorp Secrets Engines
Kv v2 delete
HashiCorp Secrets Engines
Configure backend settings for all keys
Connect HashiCorp Secrets Engines to your AI client in three steps.
01
Connect the service
Add HashiCorp Secrets Engines in Mindflow with its credentials. They stay in Mindflow and never reach the AI client.
02
Choose the tools
Pick the operations each AI client may call. Allow reads, require approval before sensitive writes and block the rest.
03
Connect your AI client
Point Claude, ChatGPT, Cursor or your own agent to your MCP Gateway endpoint, then check real calls in the audit log.
Use cases
Use cases
What your AI agents can do with HashiCorp Secrets Engines
What your AI agents can do with HashiCorp Secrets Engines
AI clients
Mindflow
HashiCorp Secrets Engines
→ Automate secret version control to prevent accidental deletion by using version undelete and destroy APIs, ensuring reliable secret lifecycle management → Streamline backend configuration updates by automatically reading and applying backend settings across all keys, reducing manual configuration errors → Enhance secret metadata management with automated reading and writing of metadata, improving auditability and compliance
→ Automate secret version control to prevent accidental deletion by using version undelete and destroy APIs, ensuring reliable secret lifecycle management → Streamline backend configuration updates by automatically reading and applying backend settings across all keys, reducing manual configuration errors → Enhance secret metadata management with automated reading and writing of metadata, improving auditability and compliance
More
More
HashiCorp
HashiCorp
MCP servers:
MCP servers:
Every call goes through one governed endpoint.
Every call goes through one governed endpoint.
Your AI clients get access. You keep control.
Your AI clients get access. You keep control.
Every call to HashiCorp Secrets Engines goes through the Mindflow MCP Gateway. The same policies apply to every AI client: role-based access by team and environment, scoped credentials that never reach the client, human approval before sensitive writes, and a log of every call you can export to your SIEM.
Every call to HashiCorp Secrets Engines goes through the Mindflow MCP Gateway. The same policies apply to every AI client: role-based access by team and environment, scoped credentials that never reach the client, human approval before sensitive writes, and a log of every call you can export to your SIEM.
HashiCorp Secrets Engines MCP server
Live
RBAC · SecOps
Scoped credentials
Audit log
Configure backend settings for all keys
Allowed
Kv v2 delete
Allowed
Kv v2 delete metadata and all versions
Needs approval
Kv v2 delete versions
Blocked
Every call logged · Export to SIEM
Questions about the HashiCorp Secrets Engines MCP server
Clear answers before you connect an AI client.
Questions about the HashiCorp Secrets Engines MCP server
Clear answers before you connect an AI client.
Explore more MCP servers in our catalog of 4,000+ services.
Put this MCP server to work.
Bring one AI client and the tools it needs. We’ll show you the setup in Mindflow, from scoped access to the audit log.
Put this MCP server to work.
Bring one AI client and the tools it needs. We’ll show you the setup in Mindflow, from scoped access to the audit log.
Less busywork. More possibility.
Let your agents handle the routine. Make room for what comes next.
Resources
Automation intelligence, delivered monthly.
Product releases, automation playbooks, and security research — straight to your inbox. No spam, unsubscribe anytime.
Less busywork. More possibility.
Let your agents handle the routine. Make room for what comes next.
Resources
Automation intelligence, delivered monthly.
Product releases, automation playbooks, and security research — straight to your inbox. No spam, unsubscribe anytime.
Less busywork. More possibility.
Let your agents handle the routine. Make room for what comes next.
Resources
Automation intelligence, delivered monthly.
Product releases, automation playbooks, and security research — straight to your inbox. No spam, unsubscribe anytime.