Infisical MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INFISICAL_HOST_URL | No | Custom host URL. This is useful if you're self-hosting Infisical or you're on dedicated infrastructure. | https://app.infisical.com |
| INFISICAL_UNIVERSAL_AUTH_CLIENT_ID | Yes | The Machine Identity universal auth client ID that will be used for authentication | |
| INFISICAL_UNIVERSAL_AUTH_CLIENT_SECRET | Yes | The Machine Identity universal auth client secret that will be used for authentication |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create-secretB | Create a new secret in Infisical |
| delete-secretB | Delete a secret in Infisical |
| update-secretB | Update a secret in Infisical |
| list-secretsB | List all secrets in a given Infisical project and environment |
| get-secretC | Get a secret in Infisical |
| create-projectA | Create a new project in Infisical |
| create-environmentC | Create a new environment in Infisical |
| create-folderB | Create a new folder in Infisical |
| invite-members-to-projectB | Invite members to a project in Infisical |
| list-projectsA | List all projects in Infisical that the machine identity has access to. If the user asks to list all projects, use the |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool targets a distinct resource and action: secret CRUD (create, get, list, update, delete) is clearly separated from project/environment/folder creation and member invitations. No two tools have overlapping or ambiguous purposes.
All tool names follow a consistent kebab-case verb-noun pattern (e.g., create-secret, list-secrets, update-secret). The singular vs. plural use is logical (list for multiple, others for single) and makes the naming predictable across the set.
10 tools is within the ideal 3-15 range for a focused server. Each tool serves a clear purpose in secrets management or project scaffolding, with no unnecessary redundancy or bloat.
Secrets are fully covered with CRUD, but the server lacks essential operations for the other entities it creates: there is no get/update/delete for projects, environments, or folders, and no list-environment/list-folder tools. This leaves obvious gaps where agents cannot manage or retrieve the resources they create.