Labsco
MCP SERVER · OFFICIAL PROJECT

Infisical

by Infisical ↗

Create, read, change and remove Infisical secrets by project, environment and path, and stand up the project, environment and folder they live in.

Identity, Access, Secrets & Encryption✓ Verified
Summary
Standing up secrets for a new environment is one sequence of calls instead of a session in the dashboard.

The tool set is shaped around the coordinates Infisical uses: nothing resolves without projectId, environmentSlug and secretPath, and list-projects exists largely to find the first of those. What the identity can see is what you get, so scoping happens outside this server. The write side is complete for secrets and thin elsewhere — environments and folders can be created but not renamed or removed, and there is no tool to take back an invitation.

What it is

The official Infisical server: ten tools over secrets, projects, environments, folders and project membership, acting as a machine identity.

What you get
  • Secrets created, read, updated and deleted at a secretPath inside a given projectId and environmentSlug
  • Reads that resolve rather than echo: expandSecretReferences and includeImports turn a referenced or imported value into its actual content
  • Projects created with a slug, type, description, projectTemplate and kmsKeyId, and listed by what the machine identity can reach
  • Environments and folders created inside a project, so a new stage or path exists before anything is written to it
  • Project invitations by emails or usernames, with the roleSlugs each invitee should get
Requirements

INFISICAL_HOST_URL, plus the universal-auth pair INFISICAL_UNIVERSAL_AUTH_CLIENT_ID and INFISICAL_UNIVERSAL_AUTH_CLIENT_SECRET for a machine identity. Every secret call also needs a projectId, an environmentSlug and a secretPath. Apache-2.0 licensed.

Setup effort

One command plus a key — npx -y @infisical/mcp, then supply credentials