Connect

Add the MCP. Ask. Approve one link.

Open your website’s repository in Claude Code, Codex, Cursor or any tool that speaks MCP. Add the server, ask, and approve the link the agent sends you. When it reports back that the site is live, invite the client.

Three steps

1. Add the Tusk MCP server to your tool’s MCP config. It is on npm; there is nothing to install.

{
  "mcpServers": {
    "tusk": {
      "command": "npx",
      "args": [
        "-y",
        "@tuskcms/mcp"
      ]
    }
  }
}

2. Ask.

Connect this site to Tusk CMS.

3. Approve the link. The agent replies with one link. Open it where you are signed in to Tusk and press Approve & connect. That one tap adds the site to your studio and connects the agent to it. The screen names the site and the exact actions you are granting; the token is saved on your machine and never shown to you or the agent. If the site is already in Tusk, the same link simply connects the agent to it.

Agent without the connect_site tool (an older @tuskcms/mcp, or a client that only speaks to the hosted server)? Add the site in the dashboard, then run this in the repository with its slug and approve the link it prints, before you ask.

npx @tuskcms/mcp login --site <your-site-slug> --scopes scan,fields,content,publish,deploy,invite

What the agent does

StepWhat happens
It registers the siteThe link it sends you adds the site to your studio the moment you approve it. Nothing is created or changed on your website.
It marks your HTMLOne data-tusk attribute per editable thing, in your own files. Attributes only. No layout, styles, markup order or wording change.
It wires your buildTwo shipped scripts pull the published content and photos and write them into the built, marked HTML, so a deploy serves your own files and never calls Tusk at runtime.
It wires your hostIt sets up a deploy hook in your own host and records it in Tusk, so a Publish rebuilds the site: on Netlify or Cloudflare it can create the hook itself, on Vercel you create it and paste the link. Tusk never hosts the site, and with a deploy hook that link is all it holds of your host.
It proves it went liveIt publishes once and checks that the publish reached the site before it reports back.

Expect a few minutes for a small site, most of it your host’s first build. It will still stop for the things only you can do: signing in to your host, and setting TUSK_TOKEN in your host’s environment if it cannot reach your host’s CLI. It cannot create a Tusk account and cannot pay for anything.

Then invite the client

Open the site in Tusk: Manage › People › Give a client access. They get an email with a link, sign in with Google or Microsoft, or a password plus an authenticator app, and land in the editor on their site, seeing only the fields that were marked. No training call. If invite was among the actions you approved, you can ask the agent to do this for you once the site is live.

What the token can and cannot do

It can
  • Act on the one site named on the approval screen, and no other.
  • Do only the actions on the approval screen: scan, mark fields, edit content, publish, record the deploy hook, invite.
  • Expire by itself after 30 days (up to 90 with --ttl). Your site and your client are unaffected; only the agent needs a fresh Approve.
  • Be revoked earlier in the dashboard, under Studio settings > Connected tools & devices. You get an email the moment it is approved.
It cannot
  • Reach your other Tusk sites, or mint another token.
  • Touch your code or hosting on its own. Tusk never hosts the site, and with a deploy hook that link is all it holds of your host.
  • Show your agent the build token: the MCP writes it straight into a git-ignored .env and hands back only a masked preview. It lets a build read published content and nothing else, and lives in .env and your host’s environment variables only.

Without an MCP

If your tool cannot use MCP servers, paste this line instead. The agent reads the public guide and does the same steps by hand, driving your browser as well as your repository. Budget 30–40 minutes for a small site, and expect it to stop a few times for a click only you can make: your host’s sign-in, the build token, the domain.

Connect this site to Tusk CMS. Read https://tuskcms.com/llms-full.txt first and follow it exactly.

What the agent needs to understand the job is public and contains no token, key or account identifier: the guide, the same at GET /api/connect, the index, and a marked-up example page. The two build scripts (tusk-pull.mjs, tusk-apply.mjs) are for connected sites, so they download with your site’s build token once you have one. Prefer to do it by hand? The developer docs cover the same four steps for a human reader.