Use Infisical MCP to work with secrets, projects, environments and folders through Infisical’s documented machine-identity or access-token authentication.
Infisical’s MCP server exposes operations on secrets and the projects that contain them. Its tool set includes looking up, creating and updating secrets, plus project, environment and folder operations. It connects an assistant to Infisical’s API rather than simply supplying a key to another integration.
Specify the project, environment and secret path before requesting a value or an update. Begin with the smallest lookup that answers the question. When changing configuration, keep the exact target and operation visible so development and production values are not confused.
Run the npm package @infisical/mcp. Universal authentication uses a machine-identity client ID and secret; access-token mode uses INFISICAL_TOKEN. A custom host URL selects self-hosted or dedicated infrastructure. Choose the authentication mode explicitly and verify the identity’s project permissions in Infisical.
Maintainer’s setup and tool reference. Browse secrets management MCP servers for related workflows.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| list-secrets | List secrets in the selected scope. |
| get-secret | Retrieve a secret. |
| update-secret | Update an existing secret. |
| list-projects | List accessible projects. |
{
"mcpServers": {
"infisical": {
"command": "npx",
"args": [
"-y",
"@infisical/mcp"
],
"env": {
"INFISICAL_AUTH_METHOD": "access-token",
"INFISICAL_TOKEN": "YOUR_INFISICAL_TOKEN"
}
}
}
}Use the maintainer’s authentication and account setup instructions.
An Infisical identity authorised for the intended project and environment.
| Variable | Description | Required |
|---|---|---|
| INFISICAL_AUTH_METHOD | Select universal-auth or access-token. | Optional |
| INFISICAL_TOKEN | Required for access-token mode. | Check documentation |
| INFISICAL_UNIVERSAL_AUTH_CLIENT_ID | Required for universal-auth mode. | Check documentation |
| INFISICAL_UNIVERSAL_AUTH_CLIENT_SECRET | Required for universal-auth mode. | Check documentation |
MCP server for 1Password service accounts
A Model Context Protocol (MCP) server that provides AI assistants with secure access to Bitwarden password manager functionality through two complementary interfaces:
MCP server for interacting with 1Password via the CLI to read and manage credentials.
Claude never receives a password. It cannot change anything without you clicking Save.
Doppler API: projects, configs, secrets.
MCP server for Wundervault zero-knowledge secret management. Exposes vault secrets to AI agents via the Model Context Protocol — secrets are