Skip the install. Get this working in under 2 minutes.
Start a free trial on cloud.anythingmcp.com, add the Infisical in one click, then point your AI client (Claude, ChatGPT, Copilot or Cursor) at the generated MCP endpoint. No Docker, no git clone, zero engineering experience required.
Summary
Infisical secrets management on Cloud US, Cloud EU or self-hosted, signed in as a machine identity: projects, environments, folders and secret imports, secret names and metadata, single secret values on request, tags, project members, identities and the audit log. Creates and updates secrets, folders, environments and tags; deleting a secret is switched off at install.
Try asking
Example prompts for Infisical
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Infisical, paste your credentials, mint an MCP API key and you're done. No Docker, no
git clone, no local server.
Infisical + Meta Muse
Infisical secrets management on Cloud US, Cloud EU or self-hosted, signed in as a machine identity: projects, environments, folders and secret imports, secret names and metadata, single secret values on request, tags, project members, identities and the audit log. Creates and updates secrets, folders, environments and tags; deleting a secret is switched off at install.
Prerequisites
See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:
INFISICAL_URL, INFISICAL_CLIENT_ID, INFISICAL_CLIENT_SECRET
Step 1 — Get credentials
Setting up takes about 5 minutes and needs an Infisical organization admin. The connector signs in as a machine identity with Universal Auth.
- In Infisical open Organization, Access Control, Machine Identities (older versions: Organization Settings, Identities), click Create Identity, name it for example AnythingMCP and give it the organization role Member or a custom role. Reading the audit log needs a role with audit log access.
- On the identity, add the auth method Universal Auth. Keep the access token TTL (30 days by default) or shorten it; the connector signs 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 your AnythingMCP server.
- Copy the Client ID (a UUID) into
INFISICAL_CLIENT_IDand the Client Secret, which is shown once, intoINFISICAL_CLIENT_SECRET. - Add the identity to every project it should reach: in the project open Access Control, Machine Identities, Add Identity, with the role Viewer to read only, or Developer or a custom role to write. Limit the role to the environments and paths it needs.
- Set
INFISICAL_URLtohttps://app.infisical.com(Cloud US),https://eu.infisical.com(Cloud EU) or the address of your own instance, without/apiand without a trailing slash. - Install the connector and run
infisical_list_projects: it confirms the login and lists the projects the identity belongs to.
The connector logs in at /api/v1/auth/universal-auth/login, sends the access token as Authorization: Bearer and renews it by itself.
Secret values reach the AI: Infisical returns a value in plain text to anyone allowed to read it, and every value this connector reads or writes passes through the conversation and the AI provider. That is why infisical_list_secrets and infisical_get_secret return names and metadata only: they ask Infisical not to send values. The one tool that returns a value is infisical_read_secret_value, one secret per call, and the AI uses it only when you ask for that value. The values you pass to infisical_create_secret and infisical_update_secret travel through the conversation too. If no value should ever appear in the chat, a workspace admin switches infisical_read_secret_value off, or the identity gets a role without permission to read values. Infisical records every value read in its audit log.
What it reads: the organization of the identity (infisical_get_identity_details); projects with their environments (name, slug, id); the folders of an environment, as a list or with recursive as the whole tree; secret imports, the other environments or paths a folder inherits secrets from; secret names with version, comment, tags, metadata and timestamps, narrowed by tag_slugs or metadata_filter, and one secret's metadata or an older version with infisical_get_secret; tags; project members with their roles, project identities and organization identities; and the organization audit log (infisical_list_audit_logs), filtered by project, environment, secret, actor, event type such as get-secret, update-secret or delete-secret, and dates, to find out who read or changed a secret. infisical_read_secret_value resolves references like ${DB_HOST} unless expand_secret_references is false.
What it writes: infisical_create_secret, infisical_update_secret (new value, new name with new_secret_name, comment or tags; tag_ids replaces the whole tag list), infisical_create_folder, infisical_create_environment and infisical_create_tag. Infisical keeps the previous version of a secret, so a value change can be rolled back in the dashboard. Apps that read the secret get the new value on their next fetch, so the AI confirms the environment with you before it writes to production. When an environment has a change approval policy, a create or update opens an approval request in Infisical instead of changing the secret at once.
Switched off at install: infisical_delete_secret. It cannot be undone from this connector and breaks every app and pipeline that reads the secret, so a workspace admin turns it on when the team needs it.
Data formats: ids are UUIDs; environments are addressed by slug (dev, staging, prod), projects by id. Paths start with /, and / alone is the root. version counts the changes of a secret; secretValueHidden: true means the value was not sent. Times are ISO 8601 in UTC.
Paging: infisical_list_audit_logs (20 entries by default), infisical_list_project_identities and infisical_list_org_identities (100 by default) page with offset and limit; the AI asks again with a higher offset while a page comes back full. The other lists return everything in one answer.
Limits: per minute and client IP, Infisical Cloud allows, 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. How long the audit log is kept depends on the plan. Self-hosted Infisical needs version 0.150 or later for the v4 secrets API the connector uses.
Common errors: 401, or 403 with TokenError, means the login failed: a wrong Client ID or Client Secret, a client secret that is revoked, expired or used up, the wrong region in INFISICAL_URL, or an IP outside the trusted IPs. 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.
The connector does not delete secrets with the tools switched on at install, reads at most one secret value per call, does not change members, roles or machine identities, and does not manage certificates or KMS keys.
Step 2 — Install the adapter
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Step 3 — Add the connector in Muse
Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (
https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide showsYOUR_SERVER_ID.
Muse adds remote MCP servers as custom connectors and signs in to them with OAuth.
- In Muse, open Settings → Connectors and choose Add custom connector.
- Paste the MCP server URL
https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. - Muse opens the AnythingMCP sign-in page: sign in and approve access.
- In a chat, ask Muse for something that needs the
Infisicaltools.
You can also set it up from a chat, on the web, in the iOS and Android apps or in WhatsApp. Send Muse this message:
Create a Custom Connector for a new remote MCP server, then connect to it:
Name: AnythingMCP
Transport: remote streamable HTTP
URL: https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID
Auth: OAuth
Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Muse connects from Meta's cloud, so localhost does not work.
Available tools
| Tool | What it does |
|---|---|
infisical_get_identity_details | Who the connector is signed in as: the organization (id, name, slug) of the machine identity |
infisical_list_projects | Projects the machine identity is a member of: id, name, slug, type (secret-manager, cert-manager, kms, ...), organization id and the… |
infisical_get_project | One project by id: name, slug, type, environments (name, slug, id), audit log retention and delete protection |
infisical_get_project_by_slug | One project by its slug (the short name in the project URL and settings), to find its id |
infisical_get_environment | One environment of a project by its slug: id, name, slug and position |
infisical_list_folders | Folders below a path in one environment of a project: id, name, description, relative path and when a secret in it last changed |
infisical_get_folder | One folder by id: name, description, full path, environment and project |
infisical_list_secret_imports | Secret imports of a folder: other environments or paths whose secrets this folder inherits (importPath, importEnv, position, replication… |
infisical_list_secrets | Names and metadata of the secrets in one folder of an environment, WITHOUT their values: the connector asks Infisical not to send values… |
infisical_get_secret | Metadata of one secret WITHOUT its value: version, comment, tags, metadata, reminder, who changed it last and when |
infisical_read_secret_value | READS THE SECRET VALUE in plain text: returns secret.secretValue of one secret (current or a given version), with its metadata |
infisical_list_tags | Secret tags of a project: id, slug and color |
infisical_list_project_members | Users who are members of a project, with their roles: membership id, user id, email, first and last name |
infisical_list_project_identities | Machine identities with access to a project, with their roles and auth methods |
infisical_list_org_identities | Machine identities of the organization with their organization role, auth methods and last login |
infisical_get_identity | One machine identity by id: name, organization role, auth methods, locked-out auth methods, metadata and last login |
infisical_list_audit_logs | Audit log of the organization, newest first: event type and class, actor (user, identity, service), IP address, user agent, project and time |
infisical_create_secret | Create a secret in one folder of an environment |
infisical_update_secret | Change an existing secret: a new value, a new name, comment or tags |
infisical_delete_secret | Delete a secret from one folder of an environment |
infisical_create_folder | Create a folder in one environment of a project, below an existing path |
infisical_create_environment | Add an environment (e.g. qa or preview) to a project, with its name, slug and position |
infisical_create_tag | Create a secret tag (slug and color) in a project, to group and filter secrets |
Example prompts
- "Which secrets are in the prod environment of our backend project? Names only, no values."
- "Who changed the secret STRIPE_SECRET_KEY in production during the last 7 days?"
- "Show me the value of DATABASE_URL in the staging environment of the api project."
- "Create a folder /payments in dev and add a secret PAYMENTS_WEBHOOK_URL with the value https://example.com/hooks/payments."
- "Which machine identities and users have access to the web project, and with which roles?"
FAQ
Where is Muse available? Meta currently offers Muse in the US and Canada, on the web, in the iOS and Android apps and in WhatsApp.
Does Meta review this connector? No. Meta doesn't review custom connectors. Muse sees only the tools you switched on for this MCP server in AnythingMCP, and you can disconnect it anytime under Settings → Connectors.
Next steps
- Connector landing page
- Connect to Claude
- Connect to ChatGPT
- Connect to Cursor
- Connect to Gemini
- Connect to Microsoft Copilot
Was this guide helpful?