Get the FREE Ultimate OpenClaw Setup Guide →

infisical

Infisical's official MCP server.

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio infisical-infisical-mcp-server npx -y @infisical/mcp \
  --env INFISICAL_HOST_URL="https://<custom-host-url>.com (optional, defaults to https://app.infisical.com)" \
  --env INFISICAL_UNIVERSAL_AUTH_CLIENT_ID="<machine-identity-universal-auth-client-id>" \
  --env INFISICAL_UNIVERSAL_AUTH_CLIENT_SECRET="<machine-identity-universal-auth-client-secret>"

How to use

This MCP server exposes a suite of Infisical API interactions via the Model Context Protocol. It enables function calling against Infisical to manage secrets, environments, folders, projects, and member access. Tools include create-secret, delete-secret, update-secret, list-secrets, get-secret, create-project, create-environment, create-folder, and invite-members-to-project. To use it, configure the server in your MCP client (e.g., Claude Desktop) with the npx invocation and your Infisical credentials. Once connected, you can inspect available tools in the MCP Inspector or test each tool directly through the MCP UI or your host app, enabling automated secret management workflows through function calls.

How to install

Prerequisites:

  • Node.js and npm installed on your machine
  • Access to the internet to fetch the MCP package

Installation steps:

  1. Ensure Node.js and npm are installed. Verify with:
node -v
npm -v
  1. You can run the MCP server directly with npx (no global install required):
npx -y @infisical/mcp
  1. If you need to customize host or credentials, set environment variables before starting:
export INFISICAL_HOST_URL=https://<custom-host-url>.com
export INFISICAL_UNIVERSAL_AUTH_CLIENT_ID=<your-client-id>
export INFISICAL_UNIVERSAL_AUTH_CLIENT_SECRET=<your-client-secret>
  1. To integrate with Claude Desktop, configure the mcpServers entry as shown in the README, using the same npx invocation and environment variables. You can also test locally by running the server and using the MCP Inspector for tool exploration.

Additional notes

Tips and common considerations:

  • INFISICAL_HOST_URL is optional if you use the default Infisical host; set it only when self-hosting or using a custom deployment.
  • Ensure your INFISICAL_UNIVERSAL_AUTH_CLIENT_ID and INFISICAL_UNIVERSAL_AUTH_CLIENT_SECRET are kept secure and not exposed in logs.
  • The available tools cover core secret management (create, update, delete, list, get) and project structure (create-project, create-environment, create-folder) plus inviting members to projects.
  • If you encounter authentication errors, verify the client credentials and that INFISICAL_HOST_URL (if set) matches your deployment.
  • When using Claude Desktop or similar clients, add the environment variables in the client configuration to ensure seamless authentication.

Related MCP Servers

Sponsor this space

Reach thousands of developers