Infisical

Infisical

This connector uses the Infisical API (Infisical Cloud US https://app.infisical.com, Cloud EU https://eu.infisical.com, or a self-hosted or dedicated instance) as a machine identity: projects and environments, folders and secret imports, secret names and metadata, single secret values on request, tags, project members and identities, organization identities and the audit log. It can create and update secrets, folders, environments and tags.

Secret values reach the AI. Infisical returns a secret's value in plain text to anyone allowed to read it. Every value this connector reads or writes passes through the conversation and the AI provider. The connector therefore lists names and metadata only (infisical_list_secrets and infisical_get_secret ask Infisical not to send values) and reads a value only with infisical_read_secret_value, one secret at a time. Use that tool only when the user asks for that value, never repeat a value unless asked, and do not copy values into other tools. An admin who wants no values in the conversation at all switches infisical_read_secret_value off, or gives the identity a role without the permission to read values.

Setup (about 5 minutes, Infisical organization admin)

1. In Infisical open Organization, Access Control, Machine Identities (older versions: Organization Settings, Identities), click Create Identity, name it e.g. AnythingMCP, organization role Member (or a custom role; reading the audit log needs a role with audit log access).
2. On the identity, add the auth method Universal Auth. Keep the access token TTL (default 30 days) or shorten it; the connector logs in again by itself. Under Client Secrets create a secret with usage limit 0 (unlimited), because every new login uses it once. If you set Trusted IPs, include the outbound address of this AnythingMCP server.
3. Copy the Client ID into INFISICAL_CLIENT_ID and the Client Secret (shown once) into INFISICAL_CLIENT_SECRET.
4. Add the identity to each project it should reach: open the project, Access Control, Machine Identities, Add Identity, role Viewer to read only, Developer or a custom role to write. Restrict the role to the environments and paths it needs.
5. Set INFISICAL_URL to https://app.infisical.com (US), https://eu.infisical.com (EU) or your instance address, without /api and without a trailing slash. Install; infisical_list_projects checks the login.

The connector logs in at /api/v1/auth/universal-auth/login and sends the access token as Authorization: Bearer.

Workflow

• Orientation: infisical_get_identity_details (organization of this identity), infisical_list_projects, then infisical_get_project or infisical_get_project_by_slug for the environments (name, slug, id) and infisical_get_environment for one environment.
• Structure: infisical_list_folders (path / for the root, recursive for the tree), infisical_get_folder, infisical_list_secret_imports for folders that inherit secrets from another environment or path.
• Secrets without values: infisical_list_secrets for a folder (recursive for all subfolders, tag_slugs or metadata_filter to narrow), infisical_get_secret for one secret's metadata or an older version.
• One value, on request: infisical_read_secret_value. References like ${DB_HOST} are resolved unless expand_secret_references is false.
• Changes: infisical_create_secret, infisical_update_secret (new value, rename with new_secret_name, comment, tags), infisical_create_folder, infisical_create_environment, infisical_list_tags and infisical_create_tag. Confirm the environment with the user before writing to production.
• Access review: infisical_list_project_members (users and roles), infisical_list_project_identities, infisical_list_org_identities (organization id from infisical_get_identity_details), infisical_get_identity.
• Audit: infisical_list_audit_logs with project_id, secret_key, event_type (e.g. get-secret, update-secret, delete-secret), actor and dates, for questions like who read or changed a secret.

Switched off at install: infisical_delete_secret; it cannot be undone from this connector and breaks every app that reads the secret, so an admin switches it on when the team needs it.

Reading the answers: ids are UUIDs; environments are addressed by slug (dev, staging, prod), projects by id. Paths start with /. version counts the changes of a secret. secretValueHidden: true means the value was not sent. Times are ISO 8601 in UTC. When an environment has a change approval policy, a create or update returns an approval request instead of the secret: tell the user it waits for approval in Infisical.

Paging: infisical_list_audit_logs, infisical_list_project_identities and infisical_list_org_identities page with offset and limit; ask again with a higher offset while a page comes back full. The other lists return everything at once.

Limits: Infisical Cloud allows per minute and client IP, depending on the plan, 200 to 600 reads, 90 to 300 writes and 120 to 500 secret operations (600 requests in total). A 429 says how many seconds to wait. Audit log retention depends on the plan.

Errors: 401 or 403 with TokenError means the login failed (wrong Client ID or Secret, used-up or expired client secret, IP not trusted). 403 PermissionDenied means the identity's role does not allow this project, environment, path or action. 404 means a wrong id, slug, path or secret name (names are case-sensitive). Self-hosted Infisical needs version 0.150 or later for the v4 secrets API that this connector uses.