Tuskcms

com.tuskcmsPublished by tuskcms.comOfficial publisherv0.4.0Updated Oct 28, 2026

Client editing for sites you built: register, scan, publish, go live, invite the client.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Tusk CMS MCP lets an assistant register, scan, publish and deploy client sites you built, and invite the client to edit them.

What you can do
  • Register and scan a site so its fields and content become editable
  • Publish content changes and deploy the site live
  • Invite the client to edit their own site
  • Authenticate against a Tusk site with a personal access token or a one-time login command
When to use it
Useful for developers or agencies who build sites on Tusk CMS and want an assistant to handle the handover workflow: scanning a site, publishing edits, going live and inviting the client.
Requirements
A Tusk site and account. Either a Tusk access token in TUSK_PAT or a one-time login command run with the site slug and scopes, which saves the token locally. Optional TUSK_URL to point at a different Tusk server; default is the hosted service. OAuth is declared as required.
Before you install
The login command requests broad scopes covering scanning, fields, content, publishing, deploying and inviting, so the saved token can change and publish live site content and add people to the site. Treat the stored token as a secret and revoke it if the machine is shared.

Installation

In SourceWeft

  1. Open Tuskcms in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.tuskcms%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "tuskcms": {
      "type": "http",
      "url": "https://tuskcms.com/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v0.4.0LatestOct 1, 2026
  2. v0.3.1Sep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.