Total CMS
REMOTE · TOTALCMS.CO
Total CMS docs, guides and CMS comparisons: Twig, field types, schemas, CLI, REST API and releases.
Available components
Last scanned (22 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 4057 tokens (~156/item across 26 items; 20 tools + 6 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 93% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
- Server version: 3.6.4 → 3.6.6 functional
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
- Tool “get_object” rewrote its description, which is the text the model reads security
- Tool “query_collection” rewrote its description, which is the text the model reads security
- Tool “search_collection” rewrote its description, which is the text the model reads security
- 28 Oct 26 0
- Tool “get_object” rewrote its description, which is the text the model reads security
- Tool “list_guides” rewrote its description, which is the text the model reads security
- Tool “query_collection” rewrote its description, which is the text the model reads security
- Tool “search_collection” rewrote its description, which is the text the model reads security
- Resource “roundups” was removed ▼ functional
- New resource “guides” functional
- Server version: 3.6.3 → 3.6.4 functional
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 0
- Tool “get_object” rewrote its description, which is the text the model reads security
- Tool “query_collection” rewrote its description, which is the text the model reads security
- Tool “search_collection” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- 24 Oct 26 72
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://totalcms.co/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=totalcms.co | CN=WE1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 7e5c39d7cadf469713351e1d8a6555d4 |
| SANs: totalcms.co, *.totalcms.co | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of totalcms.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| totalcms.co. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://totalcms.co/mcp | Verified | 200 | |
| http (plaintext) | http://totalcms.co/mcp | HTTPS enforced | 301 | https://totalcms.co/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
describe_collection ~139
Describe 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.
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Collection id (slug-form). Use list_collections to discover available collections. |
| Name | Type | Req | Description |
|---|---|---|---|
| access | string | yes | Persona that can query this collection. |
| description | string|null | – | Collection-level mcp.description, falling back to the schema description. |
| id | string | yes | – |
| ownership | string|null | – | Set when the collection limits the caller to their own objects, or has fields only the site sets: what the caller sees and may change. |
| properties | array | yes | One entry per exposed property (mcp.expose:false fields are stripped). Per-property mcp.description is surfaced here when set. |
| total_objects | integer | yes | – |
| url_pattern | string | – | URL template for objects, e.g. "/blog/{id}". Empty string when no pattern is configured. |
No examples provided.
describe_view ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | View id. Use list_views to discover available views. |
| Name | Type | Req | Description |
|---|---|---|---|
| access | string | yes | – |
| definition | string | – | Twig source for the view. Admin persona only — absent for public callers. |
| description | string | – | – |
| id | string | yes | – |
| last_built | string | – | – |
| name | string | yes | – |
| output_shape | array | yes | Keys present on the first cached item. Empty when the view has never been built or produced no items. |
| total_items | integer | yes | – |
No examples provided.
docs_get ~55
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".
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Documentation page path from docs_search results |
Structured output declared, but exposes no named fields.
No examples provided.
docs_lookup ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | – |
| name | string | – | Entry name (function name, field type, "GET /api/collections", command name…). Omit to list the kind. |
Structured output declared, but exposes no named fields.
No examples provided.
docs_search ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum results (default 8, max 20) |
| query | string | yes | Search terms, e.g. "image resize twig" or "webhook automation" |
| Name | Type | Req | Description |
|---|---|---|---|
| hint | string | – | Present when a search actually ran — guidance for the next call. |
| message | string | – | Present only when the query was too short (no token of 2+ characters). No `total`/`hint` alongside it. |
| results | array | yes | – |
| total | integer | – | Present when a search actually ran — total matches before the limit was applied. |
No examples provided.
fetch ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A document id returned by the `search` tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| metadata | object | – | – |
| text | string | yes | – |
| title | string | yes | – |
| url | string | yes | – |
No examples provided.
find_comparison ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| competitor | string | yes | Competitor name, e.g. "Kirby" or "Craft". |
| Name | Type | Req | Description |
|---|---|---|---|
| has_more | boolean | yes | True when total > offset + count(items); call again with offset += limit to paginate. |
| items | array | yes | Matching comparisons objects, each decorated with a `url` field where the collection has a public URL pattern configured. Field set varies by collection — call describe_collection for the schema. |
| limit | integer | yes | Cap applied to this response — server may have lowered the requested limit. |
| offset | integer | yes | – |
| total | integer | yes | Total matching items (post-persona-filter). |
No examples provided.
get_object ~500
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) - guides — heading (text), lede (textarea), reviewed (date, sortable), draft (toggle), sort (number, sortable), id (id, sortable), kind (select), product (select) - releases — id (id, sortable), version (text), title (text), date (date, sortable), draft (toggle), urgent (toggle), fullnotesurl (url), announce (toggle) - 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)
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Collection id. Use list_collections to discover available collections. |
| format | string | – | Rendered format for content fields. Accepted now for forward-compat; full conversion ships with the Tiptap→markdown converter in a later release. |
| id | string | yes | Object id (slug). Get candidate ids from query_collection or search_collection output. |
| locale | string | – | BCP 47 locale tag. Accepted for forward-compat with the 3.6 i18n release — has no effect today. |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Object id (slug). |
| url | string | – | Public URL for this object when the collection has a URL pattern configured. |
No examples provided.
get_resource ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| uri | string | yes | A tcms:// resource URI identifying one object. Format: tcms://{collection}/{id}. |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Object id (slug). |
| url | string | – | Public URL for this object when the collection has a URL pattern configured. |
No examples provided.
get_view ~154
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.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Forward-compat with collection tools. View data is freeform so this has no effect today. |
| id | string | yes | View id. Use list_views to discover available views. |
| locale | string | – | BCP 47 locale tag — forward-compat for the 3.6 i18n release. No effect today. |
| Name | Type | Req | Description |
|---|---|---|---|
| hint | string | – | Present only when truncated — points the agent at query_view. |
| items | array | yes | Items produced by the view, capped at 50. Field set varies by view — call describe_view for the expected shape. |
| total | integer | yes | Total cached items in the view (pre-cap). |
| truncated | boolean | yes | True when total > 50; pair with query_view for full pagination. |
No examples provided.
latest_release ~36
The most recent Total CMS release: version, title, date and the release summary. Returns: paginated releases objects with url per item.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| has_more | boolean | yes | True when total > offset + count(items); call again with offset += limit to paginate. |
| items | array | yes | Matching releases objects, each decorated with a `url` field where the collection has a public URL pattern configured. Field set varies by collection — call describe_collection for the schema. |
| limit | integer | yes | Cap applied to this response — server may have lowered the requested limit. |
| offset | integer | yes | – |
| total | integer | yes | Total matching items (post-persona-filter). |
No examples provided.
list_collections ~101
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| collections | array | yes | Persona-filtered list, sorted alphabetically by id. |
| total | integer | yes | Number of collections in the response (post-persona-filter). |
No examples provided.
list_guides ~91
The site's Guides: evergreen buying-guide pages served at /guides/{id}. 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 "guides". Returns: paginated guides objects with url per item.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| has_more | boolean | yes | True when total > offset + count(items); call again with offset += limit to paginate. |
| items | array | yes | Matching guides objects, each decorated with a `url` field where the collection has a public URL pattern configured. Field set varies by collection — call describe_collection for the schema. |
| limit | integer | yes | Cap applied to this response — server may have lowered the requested limit. |
| offset | integer | yes | – |
| total | integer | yes | Total matching items (post-persona-filter). |
No examples provided.
list_views ~100
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| total | integer | yes | – |
| views | array | yes | Persona-filtered list, sorted alphabetically by id. |
No examples provided.
needs_review ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| before | string | – | Only pages whose reviewed date is on or before this ISO date (optional). |
| Name | Type | Req | Description |
|---|---|---|---|
| has_more | boolean | yes | True when total > offset + count(items); call again with offset += limit to paginate. |
| items | array | yes | Matching comparisons objects, each decorated with a `url` field where the collection has a public URL pattern configured. Field set varies by collection — call describe_collection for the schema. |
| limit | integer | yes | Cap applied to this response — server may have lowered the requested limit. |
| offset | integer | yes | – |
| total | integer | yes | Total matching items (post-persona-filter). |
No examples provided.
query_collection ~719
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) - guides — heading (text), lede (textarea), reviewed (date, sortable), draft (toggle), sort (number, sortable), id (id, sortable), kind (select), product (select) - releases — id (id, sortable), version (text), title (text), date (date, sortable), draft (toggle), urgent (toggle), fullnotesurl (url), announce (toggle) - showcase — name (text), url (url), industry (select), id (id, sortable), owner (select), draft (toggle), featured (toggle), approved (datetime, sortable), submitte…
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Collection id (slug-form). Use list_collections to discover available collections. |
| exclude | string | – | Comma-separated field:value pairs that exclude items (OR). Drafts the caller may not see are removed before this filter runs, whatever it says. |
| format | string | – | Rendered format for content fields. Accepted now for forward-compat; full conversion ships with the Tiptap→markdown converter in a later release. |
| include | string | – | Comma-separated field:value pairs items must ALL match. Wildcards "*foo*", "foo*", "*foo" supported. |
| limit | integer | – | Maximum items to return. Capped at 50 (vs. REST's 100) to fit MCP response-size budgets. |
| locale | string | – | BCP 47 locale tag. Accepted for forward-compat with the 3.6 i18n release — has no effect today. |
| offset | integer | – | Number of items to skip — combine with limit for pagination. |
| sort | string | – | Sort rule "field:direction"; multiple rules comma-separated. Only fields marked sortable in the catalog will sort. |
| Name | Type | Req | Description |
|---|---|---|---|
| has_more | boolean | yes | True when total > offset + count(items); call again with offset += limit to paginate. |
| items | array | yes | Matching objects in sort order. Field set varies by collection — call describe_collection for the schema. |
| limit | integer | yes | Cap applied to this response — server may have lowered the requested limit. |
| offset | integer | yes | – |
| total | integer | yes | Total matching items (post-persona-filter). |
No examples provided.
query_view ~195
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.
| Name | Type | Req | Description |
|---|---|---|---|
| exclude | string | – | REST-style negative filter. |
| format | string | – | Forward-compat with query_collection; no effect today since view data is freeform. |
| id | string | yes | View id from list_views. |
| include | string | – | REST-style filter, e.g. "category:tech,published:true". Field names depend on the view's output shape. |
| limit | integer | – | – |
| locale | string | – | Forward-compat for 3.6 i18n. |
| offset | integer | – | – |
| sort | string | – | Sort spec, e.g. "date:desc". |
| Name | Type | Req | Description |
|---|---|---|---|
| has_more | boolean | yes | – |
| items | array | yes | Items in the requested page. Field set varies by view; call describe_view for the shape. |
| limit | integer | yes | Effective cap applied to this response. |
| offset | integer | yes | – |
| total | integer | yes | – |
No examples provided.
search ~59
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search terms. |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No examples provided.
search_collection ~567
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) - guides — heading (text), lede (textarea), reviewed (date, sortable), draft (toggle), sort (number, sortable), id (id, sortable), kind (select), product (select) - releases — id (id, sortable), version (text), title (text), date (date, sortable), draft (toggle), urgent (toggle), fullnotesurl (url), announce (toggle) - 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)
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Collection id to search within. Use list_collections to discover available collections. |
| format | string | – | Output format for styledtext properties on the matched items. markdown is friendliest for AI consumption. |
| limit | integer | – | Maximum items to return (capped at 50 to fit MCP response-size budgets). |
| locale | string | – | BCP 47 locale tag. Accepted for forward-compat with the 3.6 i18n release — has no effect today. |
| query | string | yes | Search terms. AND-semantics by default; use `or` between terms for OR; wrap phrases in double quotes. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | Matched objects, each a flat field map decorated with a `url`. Field set varies by collection. |
| limit | integer | yes | Applied result cap. |
| query | string | yes | The query that was run. |
| total | integer | yes | Number of items returned. |
No examples provided.
search_collections ~247
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.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Output format for styledtext properties on the matched items. markdown is friendliest for AI consumption. |
| limit | integer | – | Maximum items returned in aggregate across all collections. Capped at 50 for MCP response-size budgets. |
| locale | string | – | BCP 47 locale tag. Accepted for forward-compat with the 3.6 i18n release — has no effect today. |
| query | string | yes | Search terms. AND-semantics by default; use `or` between terms for OR; wrap phrases in double quotes. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | Matched objects across collections, each a flat field map decorated with `collection` (the source collection id) and `url`. Field set varies by collection. |
| limit | integer | yes | Applied aggregate result cap. |
| query | string | yes | The query that was run. |
| total | integer | yes | Number of items returned in aggregate. |
No examples provided.
How do I install the Total CMS MCP server?
Total CMS is a hosted endpoint at https://totalcms.co/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · totalcms.co
claude mcp add --transport http co-totalcms-docs 'https://totalcms.co/mcp'
What is the Total CMS MCP server?
Total CMS is an MCP server listed in the public MCP registry as co.totalcms/docs. Total CMS docs, guides and CMS comparisons: Twig, field types, schemas, CLI, REST API and releases. This page covers its hosted endpoint (https://totalcms.co/mcp).
Is the Total CMS MCP server safe to use?
Total CMS scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Total CMS MCP server expose?
Total CMS exposes 20 tools: describe_collection, describe_view, docs_get, docs_lookup, docs_search, and 15 more. Their descriptions and schemas cost roughly 3,654 tokens of context every time the server is loaded.
Does the Total CMS MCP server require authentication?
No. We connected to Total CMS without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Total CMS MCP server still maintained?
Total CMS is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.