Connect Infisical to Claude Code

Read, add, and rotate the secrets in a project's environments. Add Toolspoke to Claude Code once and it can use 10 Infisical actions. Your Infisical credential stays in Toolspoke, and you choose which actions Claude Code may call.

Set it up in Claude Code

Three steps, the first one once for every toolkit you will ever add.

  1. Add Toolspoke to Claude Code

    Run it in your project, then /mcp to sign in

    claude mcp add --transport http toolspoke https://toolspoke.com/mcp

    The sign-in opens in your browser, and Toolspoke asks you to approve it.

  2. Install Infisical and connect it

    Add Infisical to a project in your Toolspoke workspace.

    Access token. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

    Access token
    A machine identity access token, or a service token. Grant it only the projects and environments this connection should reach, the token's own permissions are the real limit on every action here.
  3. Choose what Claude Code may do

    All 10 actions start on. Switch off any of the 4 actions that change something in Infisical, and Claude Code gets a refusal if it tries.

What you can ask Claude Code for

A few of the Infisical actions that only read, so they are safe to try first.

  • List the projects this token can reach, each with its environments
  • Fetch one project by id, with its environments and settings
  • List the secret keys in one environment and path
  • Read one secret's value by name

What Claude Code can do in Infisical

6 actions read, 3 write and one deletes or permanently changes something.

Reads

  • List projects

    List the projects this token can reach, each with its environments. Call this first, every secret action needs a project id and an environment slug, and the environment slugs come back here.

  • Get project

    Fetch one project by id, with its environments and settings. Use list_projects when the id is not known yet.

  • List secrets

    List the secret keys in one environment and path. Values are withheld: this asks Infisical not to send them, and every result of this call is written to the workspace audit log. Read one value on purpose with get_secret instead, which is not logged. Set recursive to include every folder below the path.

  • Get secret

    Read one secret's value by name. Use it only when the value is genuinely needed, this is the one action here that returns plaintext. The response is deliberately never written to the audit log, so the value exists only in this conversation. Set expand_references to resolve ${OTHER_SECRET} placeholders in the value.

  • List folders

    List the folders under one path in an environment. Folders are how a project groups secrets by service or component, and their names are the secret_path values every secret action takes.

  • List audit logs

    Read the organisation's audit log, who read, changed, or deleted which secret, and when. Use it to answer "who touched this key" and to check that a rotation actually reached everything that reads it. Filters narrow it by project, environment, secret path or key, actor, and date range.

Writes

  • Create secret

    Add a new secret to one environment and path. Fails if the key already exists there, call update_secret for that. Anything deployed from this environment picks the value up on its next read.

  • Update secret

    Change an existing secret's value, comment, or name. This is how a credential is rotated. The previous version is kept, so get_secret can still read it back by version, nothing is lost here.

  • Create folder

    Create a folder in one environment, so a group of secrets can live under its own path. Creates nothing else, the secrets inside it are added with create_secret.

Deletes or permanently changes

  • Delete secret

    Delete a secret from one environment and path, with every version of its value. Whatever reads that key next gets nothing, which usually means an outage rather than an error anyone sees. There is no undo, rotate with update_secret unless the key genuinely has to stop existing.

Infisical in Claude Code: questions

Does Claude Code see my Infisical credential?

No. The credential is stored encrypted in Toolspoke, and the gateway adds it to each call. Claude Code only ever talks to Toolspoke, and the dashboard shows the last four characters of the credential and nothing more.

Can I stop Claude Code from changing things in Infisical?

Yes. Each of the 10 actions can be switched off for a project. Turn off the 4 that change something and Claude Code can only read.

Will 10 actions crowd Claude Code's context?

No. Toolspoke shows Claude Code five bridge tools, plus a guide where a toolkit has one, and Claude Code searches for the Infisical action it needs when it needs it. Adding more toolkits does not add more tools to its list.

Can I add it once for every project?

Yes. Add --scope user to the command and Claude Code keeps Toolspoke in every project on this machine. Without it, the server is added to the project you ran the command in.

What does it cost?

Tool calls are free on every plan, and a Infisical call does not run in a sandbox, so it bills nothing.

Try Infisical in Claude Code

Free to start, and tool calls cost nothing on any plan.