What is the Total CMS remote MCP server?
The Total CMS remote MCP server is a hosted Model Context Protocol endpoint at https://totalcms.co/mcp, so AI assistants can connect to it without installing or running anything locally.
Total CMS MCP ServerVerifiedFeatured
@Joe Workman
Basic information
Transport
Streamable HTTP
Authentication
None
Category
Developer Tools
Author
Joe Workman
Submitted by
Joe Workman
About Total CMS MCP Server
Read-only Total CMS docs and site content over MCP: exact Twig signatures, field types, schema options, the CLI, release notes and comparisons. No key required.
Connection details
https://totalcms.co/mcpSetup
claude mcp add totalcms-docs --transport http https://totalcms.co/mcpTotal CMS MCP Server tools
20Describe one collection in detail. Returns the collection metadata plus a properties array — each entry is a property with its type, description, and indexed/filterable/sortable flags. Call list_collections first to find a collection id, then describe_collection to see what is queryable inside it. `indexed: true` means the property appears in query_collection / search_collection results (and may be filterable/sortable). `indexed: false` means the property exists on objects but is not returned by query/search — retrieve it through get_object instead.
Describe one data view in detail. Returns metadata (id, name, description, last_built, access, total_items) plus output_shape — the list of keys present on the first cached item, sampled so agents can compose effective query_view / get_view calls. Admin callers also receive the view's Twig definition for dev visibility. Use list_views to discover view ids first.
Fetch a full Total CMS documentation page as markdown by its path (as returned by docs_search), e.g. "twig/data" or "site-builder/overview".
Look up a specific Total CMS reference entry: Twig functions/filters, field types, REST API endpoints, schema configuration keys, CLI commands, extension API, or builder API. Omit `name` to list all entries of a kind.
Search the Total CMS documentation. Returns matching pages with their path, title, group, and section headings. Use docs_get with a returned path to read the full page.
Fetch the full document for a search result id. Returns {id, title, text, url, metadata}; `text` is the readable body for citation. Pass an id returned by the `search` tool.
Find the head-to-head comparison page for a competitor by name (case-insensitive partial match). Returns the full page content including the feature table. Parameters: - competitor (string, required): Competitor name, e.g. "Kirby" or "Craft". Returns: paginated comparisons objects with url per item.
Fetch a single object by its id from a collection. Returns the full object as a flat map of fields, decorated with a `url` field where the collection has a public URL pattern configured. This tool does not search or filter — use query_collection for paginated lists or search_collection for free-text search. Available collections and filterable properties: - articles — id (id, sortable), title (text), author (select), summary (textarea), date (date, sortable), draft (toggle), updated (datetime, sortable) - comparisons — competitor (text), competitorUrl (url), heading (text), lede (textarea), reviewed (date, sortable), draft (toggle), sort (number, sortable), id (id, sortable) - extension — id (id, sortable), name (text), extensionId (text), soldAs (text), summary (textarea), category (select), price (number, sortable), currency (select), minEdition (select), minVersion (text), bundled (toggle), beta (toggle), docsUrl (url), productUrl (url), draft (toggle), owner (select), featured (toggle), approved (datetime, sortable), submitted (datetime, sortable), weight (range, sortable) - releases — id (id, sortable), version (text), title (text), date (date, sortable), draft (toggle), urgent (toggle), fullnotesurl (url), announce (toggle) - roundups — heading (text), lede (textarea), reviewed (date, sortable), draft (toggle), headToHead (toggle), sort (number, sortable), id (id, sortable) - showcase — name (text), url (url), industry (select), id (id, sortable), owner (select), draft (toggle), featured (toggle), approved (datetime, sortable), submitted (datetime, sortable), weight (range, sortable)
Resolve a tcms:// resource URI to its underlying object. Format: tcms://{collection}/{id} — e.g. tcms://blog/hello-world. Equivalent to calling get_object with the parsed collection and id; returns the same shape. Use this when a URI has been surfaced to you (in other tool output, in user input, etc.); use get_object directly when you have a separate collection + id pair. Extension-registered URIs (other schemes) are reachable via the resources/read transport surface.
Fetch a data view's full cached result by id. Output is freeform — each item's field set depends on the view's Twig definition. Call describe_view first to learn the expected shape. Capped at 50 items; larger views return the first 50 plus a hint to call query_view for pagination. For per-item paginated access use query_view directly.
The most recent Total CMS release: version, title, date and the release summary. Returns: paginated releases objects with url per item.
Discover the collections visible to you. Lean overview — one entry per collection. Returns id, name (display label), schema (the schema id this collection uses), description, url_pattern, access level, and total_objects (so you can decide whether to paginate or enumerate). For the per-property detail of one collection (which properties exist, which are filterable/sortable), call describe_collection. Then query_collection / search_collection / get_object for the data.
The site's Guides: evergreen buying-guide pages served at /guides/{id}, stored in the roundups collection. Returns every guide in display order with its id, heading, lede, reviewed date and draft flag. A guide's full content (contenders, choose, howToChoose, faqs, sources) is on the object itself: get_object with collection "roundups". Returns: paginated roundups objects with url per item.
Discover the pre-computed data views visible to you. Lean overview — one entry per view. Data views are Twig-defined queries that aggregate across collections; their result is cached and accessible by id. Returns id, name, description, last_built, and access. Use the id with query_view (paginated query), get_view (fetch the whole cached result), or describe_view (output shape + metadata). For raw collection content use list_collections instead.
Comparison pages ordered by how long ago their competitor facts were last verified, oldest first. Pass `before` (ISO date) to return only pages last verified before that date. Each page shows its verification date publicly, so keeping these fresh matters. Parameters: - before (string, optional): Only pages whose reviewed date is on or before this ISO date (optional). Returns: paginated comparisons objects with url per item.
Query a collection for paginated content. Returns the matching items plus pagination metadata (total, limit, offset, has_more); each item is decorated with a public `url` field where one is configured. Use REST-style `include` / `exclude` filter strings (comma-separated field:value pairs; AND-semantics for include, OR-semantics for exclude) and `sort` (e.g. `date:desc`). Only properties listed in the catalog below are queryable — other schema properties exist on objects but are not filterable here; use get_object if you need the full record or describe_collection to see every property. This tool does not free-text search content — use search_collection for that. It does not fetch a single object by id — use get_object. Available collections and filterable properties: - articles — id (id, sortable), title (text), author (select), summary (textarea), date (date, sortable), draft (toggle), updated (datetime, sortable) - comparisons — competitor (text), competitorUrl (url), heading (text), lede (textarea), reviewed (date, sortable), draft (toggle), sort (number, sortable), id (id, sortable) - extension — id (id, sortable), name (text), extensionId (text), soldAs (text), summary (textarea), category (select), price (number, sortable), currency (select), minEdition (select), minVersion (text), bundled (toggle), beta (toggle), docsUrl (url), productUrl (url), draft (toggle), owner (select), featured (toggle), approved (datetime, sortable), submitted (datetime, sortable), weight (range, sortable) - releases — id (id, sortable), version (text), title (text), date (date, sortable), draft (toggle), urgent (toggle), fullnotesurl (url), announce (toggle) - roundups — heading (text), lede (textarea), reviewed (date, sortable), draft (toggle), headToHead (toggle), sort (number, sortable), id (id, sortable) - showcase — name (text), url (url), industry (select), id (id, sortable), owner (select), draft (toggle), featured (toggle), approved (datetime, sortable), submitted (datetime, sortable), weight (range, sortable)
Paginated query against a data view's cached result. REST-syntax include/exclude/sort, same vocabulary as query_collection. View data is freeform — call describe_view first to learn the field set before composing filters. `limit` is capped at 50; use offset to paginate larger views.
Search site content across all collections you can see. Returns matching results as {id, title, url}; pass a result id to `fetch` to read the full document. Drafts are hidden from anonymous callers.
Free-text search within a single collection. Returns matching items decorated with a public `url`; total reflects what was found. Supports AND (default), OR, and "quoted phrases". Searches across the properties listed in the catalog below — other schema properties exist on objects but are not searchable here; use get_object for the full record or describe_collection to see every property. This tool does not filter by field value — use query_collection with `include`/`exclude` for that. Drafts are auto-hidden from anonymous callers. Available collections and filterable properties: - articles — id (id, sortable), title (text), author (select), summary (textarea), date (date, sortable), draft (toggle), updated (datetime, sortable) - comparisons — competitor (text), competitorUrl (url), heading (text), lede (textarea), reviewed (date, sortable), draft (toggle), sort (number, sortable), id (id, sortable) - extension — id (id, sortable), name (text), extensionId (text), soldAs (text), summary (textarea), category (select), price (number, sortable), currency (select), minEdition (select), minVersion (text), bundled (toggle), beta (toggle), docsUrl (url), productUrl (url), draft (toggle), owner (select), featured (toggle), approved (datetime, sortable), submitted (datetime, sortable), weight (range, sortable) - releases — id (id, sortable), version (text), title (text), date (date, sortable), draft (toggle), urgent (toggle), fullnotesurl (url), announce (toggle) - roundups — heading (text), lede (textarea), reviewed (date, sortable), draft (toggle), headToHead (toggle), sort (number, sortable), id (id, sortable) - showcase — name (text), url (url), industry (select), id (id, sortable), owner (select), draft (toggle), featured (toggle), approved (datetime, sortable), submitted (datetime, sortable), weight (range, sortable)
Full-text search across every collection you can see, in one call. Returns matching items each decorated with `collection` (which collection the hit came from) and `url`. Pair `collection` + `id` to fetch the full record via get_object. Call list_collections for the available collections and describe_collection on any one for its full property list; properties not flagged filterable there exist on objects but are not searched here (use get_object for the full record). For a single-collection search use search_collection instead — same query syntax, scoped tighter. Drafts are auto-hidden from anonymous callers.
Overview
Total CMS Docs
The public MCP server for Total CMS, the flat-file PHP CMS with a built-in MCP server. Point your AI client at it and the agent looks up Total CMS answers from the source instead of guessing: exact Twig function signatures, field types, schema options, CLI commands and REST API endpoints, matched to the current release.
No account, no API key. It is read-only.
Connect
Claude Code
claude mcp add --transport http totalcms-docs https://totalcms.co/mcp
Claude Desktop, ChatGPT and other clients: add https://totalcms.co/mcp as a remote (Streamable HTTP) server. For a
client that only speaks stdio, use npx mcp-remote https://totalcms.co/mcp.
Tools
Documentation
docs_search: search the Total CMS documentationdocs_get: fetch a full docs page as Markdowndocs_lookup: exact reference entries for Twig functions and filters, field types, schema options, REST endpoints and CLI commands
Site content (totalcms.co's own collections)
search,search_collections,search_collection: full-text searchlist_collections,describe_collection,query_collection,get_object,get_resource: browse and read contentlist_views,describe_view,query_view,get_view: pre-computed data viewslatest_release: the newest release and its notesfind_comparison: the head-to-head page for a competitor (Kirby, Statamic, Grav, WordPress and others)list_guides: the buying guidesfetch: full documents for ChatGPT and deep-research clients
Prompts
Guided workflows that use the tools above: tcms_research, tcms_twig_recipe, tcms_explain_field, tcms_model_collection,
tcms_build_page, tcms_write_content, tcms_audit_seo and tcms_troubleshoot_mcp.
Your own site has one too
Every Total CMS install serves the same MCP server at https://your-site/mcp, with your own schemas, content and
version-matched docs. Reading works on Standard and Pro. Writing (content, schemas, collections) needs Pro and an OAuth 2.1
token or an API key. Read the MCP docs
Also available as a Claude Desktop extension, in the ChatGPT and Claude plugin
directories, and in the official MCP registry as co.totalcms/docs.
Frequently asked questions
How do I connect to the Total CMS MCP server?
Add the endpoint https://totalcms.co/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.
Does the Total CMS MCP server require authentication?
No. Total CMS's MCP server does not require authentication — you can connect directly with the endpoint URL.
Which transport does the Total CMS MCP server use?
Total CMS exposes a Streamable HTTP endpoint, the transport used by remote MCP servers and supported by all major MCP clients.
More remote MCP servers
9apes
The 9apes MCP server lets an AI assistant read the GitHub Actions data 9apes already collects for your organization: runs, jobs, steps, and their durations. Ask it why a build got slower, which jobs take the longest, or
AdWhispr - Research, Clone, & Launch Ads from Claude/ChatGPT
Remote MCP server that turns Claude, ChatGPT, or Cursor into a full ad workflow: research any brand's live Facebook and TikTok ads, clone the proven winners for your own brand, and launch real campaigns on Google, TikTok
A
AI Pricing Hub
Read-only, source-backed AI model pricing, history, comparisons and cost calculations.
A
ASO Atlas
App Store keyword research, rank tracking, competitor analysis and authorized performance data.
AdLoop Cloud
Hosted AdLoop: Google Ads, Reddit Ads, GA4 and Tag Manager in claude.ai, ChatGPT and more, with a preview before every change.
Comments