CMS

Client sites
Each card says whether the site is live, who can edit it, and what to do next.

Activity

Across all your sites

Plan

Your plan
MonthlyYearly

Refer & earn

Your referral link

Earn 20% of everything a referred studio pays for a year.

Share it anywhere developers are. Anyone who signs up within 90 days of clicking it is your referral, and every payment they make in their first 12 months earns you 20%. How the programme works.

0link clicks
0studios signed up
US$0earned, awaiting payout
US$0paid to you
Payout email (PayPal or bank contact)

Studio settings

Your brand in the editor, sign-in security, connected tools.

Connected tools & devices

AI tools paired through the Tusk MCP. Each can do only what you approved, and expires by itself. Revoke anything you don’t recognise.
Your brand in the editor

Name
Colour
Pick any colour
Logo (PNG, JPG or WebP)

Two-step sign-in

Loading…

Close this studio

Everything becomes read-only: no edits, publishes or invitations. Your websites keep running. The data is deleted 30 days after closing unless you export it.

Chrome extension

An Edit with Tusk button on every site you manage, from the page itself: open the editor, manage or publish without going through the dashboard. Download, unzip, then chrome://extensions › Developer mode › Load unpacked. Instructions.

Your sites›

The editor is what your client sees. Everything below is yours.

Open the editor

Setup

Five steps to live

Checking…

    1. Site address

    Where the site lives; the editor previews it and the scanner reads it
    Site name
    Business
    Live domain
    Preview URL

    2. What the client can edit

    Turn on Make editable, then click anything on your site
    All fields & scanningSet fields by list, scan pages, rename or lock
    Scan your site

    Paste the page addresses. Tusk reads each page, finds the headings, text, buttons, photos, downloads and repeated cards, and builds the fields.

    How to mark up a page by hand 
    <h1 data-tusk="home.headline">A small studio.</h1>
<p data-tusk="home.intro">Longer text becomes paragraphs.</p>
<img data-tusk="home.hero" src="…">               a photo
<a data-tusk="home.pricelist" href="/prices.pdf">   a download
<h2 data-tusk="about.heading" data-tusk-label="Team heading">

    page.field, or just field for the page the address implies. data-tusk-label names it for the client; data-tusk-kind (text, textarea, photos, file) overrides the guess. Marks always win over the automatic scan. Try it on the example page.

    Pages and fields

    3. Connect it to your site

    Add Tusk to your AI tool, log in once, paste one prompt. It does the rest.
    1

    Add Tusk to your AI tool

    Paste this into your tool’s MCP settings (Claude Code, Codex, Cursor…). Nothing to install.

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

    Log in once

    Run this in your site’s folder. It prints a link: open it, press Approve. That gives your tool access to this site only, and never to your code or hosting.

    npx @tuskcms/mcp login --site … --scopes scan,fields,content,publish,deploy,invite
    3

    Copy the prompt, paste it into your AI tool

    Hit Copy the prompt (top-right) and paste it. You don’t need to read it. Your tool marks what’s editable, wires your host, and publishes. When it’s done, your fields appear in step 2 above and step 4 says whether it’s live. Then invite your client under Project → People.

    For your developer (optional)

    Your AI tool does all of this through the MCP. By hand: after the marked pages are deployed, press Scan for editable fields above to verify the markup. Then in the build, pull the published content with two zero-dependency scripts:

    curl -O /sdk/tusk-pull.mjs && curl -O /sdk/tusk-apply.mjs
    node tusk-pull.mjs && node tusk-apply.mjs dist

    Set TUSK_TOKEN on your host to the build token under Advanced → Build token (in step 4, Going live).

    Download .tusk/schema.json

    4. Going live

    Set this up once. Then Publish sends edits to the real website.
    Last published
    Last deploy
    Build feed
    How edits reach your website
    Vercel: connect once for every site
    Site on Vercel? Create a token at vercel.com/account/tokens and paste it here once. Every site in your studio then goes live on Publish, with no deploy hook: Tusk finds each site's Vercel project from its address. Stored encrypted, never shown again.

    Deploy hook linkWhere to find it: Vercel → Project → Settings → Git → Deploy Hooks; Netlify → Project configuration → Build & deploy → Build hooks; Cloudflare Pages → Settings → Builds → Deploy hooks. Every other host: pick yours on tuskcms.com. Paste the link here. Every Publish uses it to rebuild your site with the new content. For this to actually show your edits, the site’s build must pull Tusk content. That’s what the prompt in step 3 sets up. No git on Vercel? Use vercel://TOKEN@TEAM_ID/PROJECT_ID — stored encrypted.
    Publishes every page now and tells you what happened.

    Advanced (webhooks, public feed)
    Publish webhook URLTusk POSTs a signed payload here on every publish; your receiver pulls the feed and deploys anywhere. Setting a URL mints a signing secret, shown once.
    Advanced build token, publish to GitHub

    Build token

    The site build sends it as a Bearer header to read the feed above
    The old one stops working the moment you do.

    Publish to GitHub

    Every publish commits .tusk/published.json and changed photos to the site's own repository, so its normal deploy runs.

    Leaving, or handing over

    Export works whatever your plan's standing: content, fields, history and every file, with a note on leaving. Release hands the whole site to another studio. Remove site takes it off your studio (after an export): the build token is rotated, the deploy hook cleared and client logins removed; the client's published site keeps serving its last snapshot.

    Give a client access

    They get an email with a link. They open it, continue with Google or Microsoft (or choose a password plus an authenticator app), and they are in.

    Their name
    Their email

    Build token

    Your site's build fetches published content from this address, sending the token as a Bearer header. Copy it now: for safety the token is shown only once, but you can make a new one here whenever you need it.

    Endpoint

    Token

    Build it Tusk-ready

    The site is in your studio and your client's build tracker has started at Kickoff. Paste this line into Claude Code, Codex or Cursor in the new site's folder: it builds the site with every editable element marked as it goes, so connecting it later is a formality.

    
  
    
    



  
    
  
    
  
    
    


  
    
    
    
    
    
    
    
    
    
    
    
  
    
    


  
    
    
    Folder settings
    
    
    Name
    
    
    Colour
      
    
        
    
        
    
          
          
          
          
          
          
        
    
      
    
    
    
    
    
    
    
  
    
    


  
    
    
    Add an invoice
    
    
    
      
    Number
    
      
    Amount (A$, inc. GST)
    
    
    
    
    Description
    
    
    
      
    Status
    
      
    PDF (optional)
    
    
    
    
    
    
    
  
    
    


  
    
    
    Send a file to your client
    
    
    It appears under Files in their login.
    
    
    File (PDF or image)
    
    
    
      
    Name
    
      
    Type
    
    
    
    
    A line about it