by infisical
Securely manage and access secrets with a bridge to Infisical. Supports secret server solutions like AWS Secrets Manager
Connects to Infisical's secrets management platform to create, read, update, and delete secrets securely through API calls.
Infisical (Secrets Management) is an official MCP server published by infisical that provides AI assistants with tools and capabilities via the Model Context Protocol. Securely manage and access secrets with a bridge to Infisical. Supports secret server solutions like AWS Secrets Manager It is categorized under auth security, productivity.
You can install Infisical (Secrets Management) in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
Apache-2.0
Infisical (Secrets Management) is released under the Apache-2.0 license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
According to our notes, Infisical (Secrets Management) benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
We wired Infisical (Secrets Management) into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Useful MCP listing: Infisical (Secrets Management) is the kind of server we cite when onboarding engineers to host + tool permissions.
Infisical (Secrets Management) has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Infisical (Secrets Management) is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
We evaluated Infisical (Secrets Management) against two servers with overlapping tools; this profile had the clearer scope statement.
Infisical (Secrets Management) reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
I recommend Infisical (Secrets Management) for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
We evaluated Infisical (Secrets Management) against two servers with overlapping tools; this profile had the clearer scope statement.
Strong directory entry: Infisical (Secrets Management) surfaces stars and publisher context so we could sanity-check maintenance before adopting.
showing 1-10 of 68
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.
In order to use the MCP server, you must first set the environment variables required for authentication.
INFISICAL_UNIVERSAL_AUTH_CLIENT_ID: The Machine Identity universal auth client ID that will be used for authenticationINFISICAL_UNIVERSAL_AUTH_CLIENT_SECRET: The Machine Identity universal auth client secret that will be used for authentication.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 to https://app.infisical.comTo run the Infisical MCP server using npx, use the following command:
npx -y @infisical/mcp
Add the following to your claude_desktop_config.json. See here for more details.
{
"mcpServers": {
"infisical": {
"command": "npx",
"args": ["-y", "@infisical/mcp"],
"env": {
"INFISICAL_HOST_URL": "https://<custom-host-url>.com", // Optional
"INFISICAL_UNIVERSAL_AUTH_CLIENT_ID": "<machine-identity-universal-auth-client-id>",
"INFISICAL_UNIVERSAL_AUTH_CLIENT_SECRET": "<machine-identity-universal-auth-client-secret"
}
}
}
}
| 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 |
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
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.