Connect Netlify to Claude Code

Manage Netlify sites, deploys, builds, forms and environment variables. Add Toolspoke to Claude Code once and it can use 19 Netlify actions. Your Netlify 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 Netlify and connect it

    Add Netlify to a project in your Toolspoke workspace.

    Personal 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.

    Personal access token
    Netlify → your avatar → User settings → Applications → Personal access tokens → New access token. The token acts as you, on every team you belong to.
  3. Choose what Claude Code may do

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

What you can ask Claude Code for

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

  • Read one site's settings, custom domain, build settings, linked repository and the deploy currently published
  • Return the user this token belongs to, with their name, email and the teams they can reach
  • List the team accounts this token can reach
  • List a site's deploys, newest first, with their state, branch, commit, context and error message if one failed

What Claude Code can do in Netlify

11 actions read, 3 write and 5 delete or permanently change something.

Reads

  • List sites

    List the sites this token can reach, with their id, name, URL, linked repository and the latest published deploy. Takes no required arguments, which is why an install tests itself with it.

  • Get site

    Read one site's settings, custom domain, build settings, linked repository and the deploy currently published.

  • Get current user

    Return the user this token belongs to, with their name, email and the teams they can reach.

  • List accounts

    List the team accounts this token can reach. An account id is what the environment variable actions take.

  • List site deploys

    List a site's deploys, newest first, with their state, branch, commit, context and error message if one failed.

  • Get deploy

    Read one deploy by id, including its state, URLs, commit, summary of changes and error message. The first call when a deploy failed.

  • List site builds

    List a site's builds, newest first, with their deploy id, state and timing.

  • Get build

    Read one build by id, with its state, deploy id and timing.

  • List forms

    List the forms Netlify detected on a site, with their field names and submission counts.

  • List form submissions

    List the submissions to one form, newest first. They are what visitors typed, so the response is never written to the audit log.

  • List env vars

    List environment variables on a team account, or on one site when site_id is given, with their scopes and values per deploy context. Values can be secrets, so the response is never written to the audit log.

Writes

  • Lock deploy

    Lock publishing on this deploy, so later builds of the production branch are built but not published until unlock_deploy. Reversible.

  • Unlock deploy

    Unlock publishing that lock_deploy locked, so the next production build publishes automatically again.

  • Set env var value

    Set the value of an existing environment variable for one deploy context. It takes effect on the next build. The value is masked in the audit log.

Deletes or permanently changes

  • Trigger build

    Start a new build of the site from its linked repository. Destructive because a build of the production branch publishes to the live site as soon as it succeeds, unless publishing is locked. Pass branch to build another branch, and clear_cache to build without the dependency cache.

  • Restore deploy

    Publish an earlier deploy of the site to production again. Destructive because it changes what visitors see at once; restore the previous deploy to undo it.

  • Cancel deploy

    Cancel a deploy that is still building or processing. Destructive because a cancelled deploy cannot be resumed; a new build has to start from the beginning.

  • Delete submission

    Delete one form submission permanently. There is no undo.

  • Delete env var

    Delete an environment variable and all its values. Destructive because the values are gone and the next build runs without them.

Netlify in Claude Code: questions

Does Claude Code see my Netlify 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 Netlify?

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

Will 19 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 Netlify 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 Netlify call does not run in a sandbox, so it bills nothing.

Try Netlify in Claude Code

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