Model Context Protocol server for Tusk CMS: connect Claude Code or Codex to a Tusk studio and manage sites headlessly — create, scan, save fields, publish, check deploys — over a scoped personal access token.
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
TUSK_PATAPI keyoptionalOptional. A Tusk access token (tusk_pat_…). Leave unset and run `npx @tuskcms/mcp login --site <slug> --scopes scan,fields,content,publish,deploy,invite` once instead; the token is then saved on this…
Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge has no scan on record for this entry, so it holds no observation of its tool surface. That is an absence of evidence, not evidence that it exposes no tools.
Model Context Protocol server for Tusk CMS: connect Claude Code or Codex to a Tusk studio and manage sites headlessly — create, scan, save fields, publish, check deploys — over a scoped personal access token.
This package has not been scanned yet, so no dependency tree has been resolved.