Check Secrets, Projects, and Access Through Infisical and Your Muse
Through an AnythingMCP custom connector, your muse can check your Infisical projects for you: which secrets exist by name, who can reach them, and who read or changed one, while values stay hidden unless you ask for one by name.
What it does
Infisical is where teams store secrets such as database passwords and service keys. Connected this way, the muse gets 23 tools and signs in as a machine identity you create for it. It lists projects, their environments, such as dev, staging, and prod, and the folders inside each one. It lists secret names with version, tags, and change history, without their values. One separate tool reads a single secret value, only when you ask. It reads tags, project members with their roles, machine identities, and the audit log. With your approval it creates and updates secrets, folders, environments, and tags. Deleting a secret is off at install.
How to use it
- In Infisical, open Organization, then Access Control, then Machine Identities, and create an identity for the connector with a Member role.
- Add the Universal Auth method, create a client secret with no usage limit, and copy the Client ID and Client Secret, shown once, into the connector.
- Add the identity to each project it should reach, as Viewer to read only, or with a write role only where you want changes. Use your US, EU, or own instance address.
- In Muse, open Settings, then Connectors, and add a custom connector with the address AnythingMCP gives you. Sign in and approve.
- Ask in plain words: list the secret names in prod and tell me who changed any of them this week.
What you need
- A Muse account that can add custom connectors
- An AnythingMCP workspace, on Cloud or self-hosted
- An Infisical organization where you are an admin
What to watch for
- A value the muse reads or writes passes through the chat in plain text. That is why the list tools return names only. If no value should ever appear in chat, switch the value tool off, or give the identity a role with no right to read values.
- A write to production takes effect on the next fetch by your apps. The muse confirms the environment with you before it writes. With a change approval policy, a write opens an approval request instead.
- This is a custom connector, and Meta does not review custom connectors. You can disconnect it in Settings at any time. The muse prepares, you decide.