Infisical Model Context Protocol
The Infisical Model Context Protocol server allows you to integrate with Infisical APIs through function calling. This protocol supports various tools to interact with Infisical.
Setup
Environment variables
In order to use the MCP server, you must first set the environment variables required for authentication.
INFISICAL_AUTH_METHOD: The authentication method to use. Supported values areuniversal-authandaccess-token. Defaults touniversal-auth.INFISICAL_UNIVERSAL_AUTH_CLIENT_ID: The Machine Identity universal auth client ID. Required whenINFISICAL_AUTH_METHODisuniversal-auth.INFISICAL_UNIVERSAL_AUTH_CLIENT_SECRET: The Machine Identity universal auth client secret. Required whenINFISICAL_AUTH_METHODisuniversal-auth.INFISICAL_TOKEN: An access token for authentication. This can be both a personal access token or a machine identity access token. Required whenINFISICAL_AUTH_METHODisaccess-token.INFISICAL_HOST_URL: Optionally set a custom host URL. This is useful if you're self-hosting Infisical or you're on dedicated infrastructure. Defaults tohttps://app.infisical.com.
To run the Infisical MCP server using npx, use the following command:
npx -y @infisical/mcp
Usage with Claude Desktop
Add the following to your claude_desktop_config.json. See here for more details.
Universal Auth (default)
{
"mcpServers": {
"infisical": {
"command": "npx",
"args": ["-y", "@infisical/mcp"],
"env": {
"INFISICAL_HOST_URL": "https://<custom-host-url>.com",
"INFISICAL_UNIVERSAL_AUTH_CLIENT_ID": "<machine-identity-universal-auth-client-id>",
"INFISICAL_UNIVERSAL_AUTH_CLIENT_SECRET": "<machine-identity-universal-auth-client-secret>"
}
}
}
}
Access Token
{
"mcpServers": {
"infisical": {
"command": "npx",
"args": ["-y", "@infisical/mcp"],
"env": {
"INFISICAL_HOST_URL": "https://<custom-host-url>.com",
"INFISICAL_AUTH_METHOD": "access-token",
"INFISICAL_TOKEN": "<your-access-token>"
}
}
}
}
Available tools
| Tool | Description |
|---|---|
create-secret |
Create a new secret |
delete-secret |
Delete a secret |
update-secret |
Update a secret |
list-secrets |
Lists all secrets |
get-secret |
Get a single secret |
create-project |
Create a new project |
create-environment |
Create a new environment |
create-folder |
Create a new folder |
invite-members-to-project |
Invite one or more members to a project |
list-projects |
List all projects |
Debugging the Server
To debug your server, you can use the MCP Inspector.
First build the server
npm run build
Run the following command in your terminal:
# Start MCP Inspector and server
npx @modelcontextprotocol/inspector node dist/index.js
Instructions
- Set the environment variables as described in the Environment Variables step.
- Run the command to start the MCP Inspector.
- Open the MCP Inspector UI in your browser and click Connect to start the MCP server.
- You can see all the available tools and test them individually.
Recommend MCP Servers 💡
mcp_weather_server
An MCP server providing weather information via Open-Meteo API.
Token-Minter-MCP
An MCP server providing tools for AI agents to mint ERC-20 tokens across multiple blockchains.
telephony-mcp-server
A very simple no-fuss minimalist MCP Server with telephony tools like voice call and sms. This MCP Server can be integrated with LLM applications. Vonage API is used for calls, SMS, Speech-to-Text and Speech Recognition.
bundler_mcp
A Model Context Protocol (MCP) server enabling AI agents to query information about gems in a Ruby project's Gemfile, including source code and metadata.
domain-check-mcp
An MCP server for checking domain availability using IONOS endpoints
imagesorcery-mcp
An MCP server providing tools for image processing operations