Infisical MCP Server – Secrets Management for AI Agents
Infisical's official MCP server lets AI agents interact with Infisical APIs through function calling. It is useful when agents need governed access to secrets management workflows such as listing, reading, creating, updating, or deleting secrets and managing related Infisical project resources.
Overview
Infisical MCP Server is the official Model Context Protocol server published by Infisical for connecting AI assistants and agents to Infisical APIs. Infisical is a security platform for managing application secrets, certificates, SSH keys, privileged access, and identities across human, machine, and agent workflows. The MCP server provides a structured tool layer so an AI client can work with Infisical data through explicit, authenticated tool calls instead of relying on static model knowledge or pasted credentials.
What the MCP server enables
The server exposes tools for common Infisical operations. Documented tools include creating, deleting, updating, listing, and retrieving secrets; creating projects, environments, and folders; inviting members to a project; and listing projects. These capabilities allow an AI agent to help with secrets-management tasks such as checking whether a project contains a needed secret, creating a folder structure for a new environment, or updating configuration values under the permissions of the authenticated identity.
When to use it
Use this MCP server when an agent needs controlled access to Infisical rather than a broad, manually shared token or copied secret values. Practical workflows include assisting platform teams with project setup, helping developers inspect secret names or values where permitted, maintaining environment-specific configuration, or automating routine onboarding steps for new services. Because the server can expose write operations such as create, update, and delete, it should be connected only to trusted MCP clients and identities with the minimum permissions required.
Connection and authentication
The official server is a local stdio MCP server started with npx -y @infisical/mcp. Authentication is configured with environment variables. By default, it uses Machine Identity Universal Auth with INFISICAL_UNIVERSAL_AUTH_CLIENT_ID and INFISICAL_UNIVERSAL_AUTH_CLIENT_SECRET. It can also use INFISICAL_AUTH_METHOD=access-token with INFISICAL_TOKEN, which may be a personal access token or machine identity access token. INFISICAL_HOST_URL can point to a custom host for self-hosted or dedicated Infisical deployments and otherwise defaults to https://app.infisical.com.
Key considerations
The MCP server acts with the permissions granted to the configured Infisical identity or token. Use RBAC, scoped machine identities, and short-lived or tightly controlled credentials where possible. Avoid connecting it to untrusted clients, and review tool calls carefully because the server includes mutating tools for secrets and project resources. For documentation-only assistance, Infisical also provides a separate public docs MCP endpoint at https://infisical.com/docs/mcp that does not require authentication, but that endpoint is distinct from the API-integrated secrets-management MCP server described here.
Supported Transports
stdio
Command: npx
Args:
-y@infisical/mcp
Frequently Asked Questions
- When should an AI agent use the Infisical MCP server?
- Use it when an agent needs authenticated access to Infisical secrets-management workflows, such as listing projects, retrieving permitted secrets, creating folders or environments, or helping maintain configuration across application environments.
- What does this MCP server add to an AI agent's capabilities?
- It gives the agent live, tool-based access to Infisical APIs through MCP, allowing the agent to perform documented Infisical operations instead of answering only from general knowledge or static documentation.
- What can the AI agent access or manage through this server?
- The documented tools include create-secret, delete-secret, update-secret, list-secrets, get-secret, create-project, create-environment, create-folder, invite-members-to-project, and list-projects. Actual access depends on the configured Infisical identity or token permissions.
- How is authentication configured for this MCP server?
- Authentication is configured with environment variables. Universal Auth uses INFISICAL_UNIVERSAL_AUTH_CLIENT_ID and INFISICAL_UNIVERSAL_AUTH_CLIENT_SECRET, while access-token mode uses INFISICAL_AUTH_METHOD=access-token and INFISICAL_TOKEN. INFISICAL_HOST_URL can be set for custom, self-hosted, or dedicated Infisical instances.
- Which transport should be used for this MCP server?
- Use the documented stdio transport by running npx -y @infisical/mcp from an MCP-compatible client. The official API-integrated Infisical MCP server documentation does not list Streamable HTTP or SSE transports for this package.