Convert PDFs and other documents to structured formats via Docling, for AI applications.
Nothing to run from here
Total CMS is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
20
tools declared
remote
at its publisher
—
calls last 7d
What it does
Read-only Total CMS docs: Twig signatures, field types, schema options, the CLI and the REST API.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http total-cms-mcp-2 https://totalcms.co/mcp
# 2 — ask your agent for something these tools do
# describe_collection, describe_view, docs_get and 17 more
Total CMS costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
TOAll 2 servers
totalcms2 servers
2 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http total-cms-mcp-2 https://totalcms.co/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
20 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 b
| Parameter | Type | Required | Notes |
|---|---|---|---|
| collection | string | yes | Collection id (slug-form). Use list_collections to discover available collections. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | View id. Use list_views to discover available views. |
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".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | yes | Documentation page path from docs_search results |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | yes | — |
| name | string | no | Entry name (function name, field type, "GET /api/collections", command name…). Omit to list the 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search terms, e.g. "image resize twig" or "webhook automation" |
| limit | integer | no | Maximum results (default 8, max 20) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | A document 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| competitor | string | yes | Competitor name, e.g. "Kirby" or "Craft". |
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 (te
| Parameter | Type | Required | Notes |
|---|---|---|---|
| collection | string | yes | Collection id. Use list_collections to discover available collections. |
| id | string | yes | Object id (slug). Get candidate ids from query_collection or search_collection output. |
| format | string | no | Rendered format for content fields. Accepted now for forward-compat; full conversion ships with the Tiptap→markdown converter in a later release. |
| locale | string | no | BCP 47 locale tag. Accepted for forward-compat with the 3.6 i18n release — has no effect today. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| uri | string | yes | A tcms:// resource URI identifying one object. Format: tcms://{collection}/{id}. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | View id. Use list_views to discover available views. |
| format | string | no | Forward-compat with collection tools. View data is freeform so this has no effect today. |
| locale | string | no | BCP 47 locale tag — forward-compat for the 3.6 i18n release. No effect today. |
The most recent Total CMS release: version, title, date and the release summary. Returns: paginated releases objects with url per item.
No parameter schema on file.
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_collectio
No parameter schema on file.
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.
No parameter schema on file.
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
No parameter schema on file.
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 compariso
| Parameter | Type | Required | Notes |
|---|---|---|---|
| before | string | no | Only pages whose reviewed date is on or before this ISO date (optional). |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| collection | string | yes | Collection id (slug-form). Use list_collections to discover available collections. |
| include | string | no | Comma-separated field:value pairs items must ALL match. Wildcards "*foo*", "foo*", "*foo" supported. |
| exclude | string | no | Comma-separated field:value pairs that exclude items (OR). Drafts the caller may not see are removed before this filter runs, whatever it says. |
| sort | string | no | Sort rule "field:direction"; multiple rules comma-separated. Only fields marked sortable in the catalog will sort. |
| limit | integer | no | Maximum items to return. Capped at 50 (vs. REST's 100) to fit MCP response-size budgets. |
| offset | integer | no | Number of items to skip — combine with limit for pagination. |
| format | string | no | Rendered format for content fields. Accepted now for forward-compat; full conversion ships with the Tiptap→markdown converter in a later release. |
| locale | string | no | BCP 47 locale tag. Accepted for forward-compat with the 3.6 i18n release — has no effect today. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | View id from list_views. |
| include | string | no | REST-style filter, e.g. "category:tech,published:true". Field names depend on the view's output shape. |
| exclude | string | no | REST-style negative filter. |
| sort | string | no | Sort spec, e.g. "date:desc". |
| limit | integer | no | — |
| offset | integer | no | — |
| format | string | no | Forward-compat with query_collection; no effect today since view data is freeform. |
| locale | string | no | Forward-compat for 3.6 i18n. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search terms. |
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 too
| Parameter | Type | Required | Notes |
|---|---|---|---|
| collection | string | yes | Collection id to search within. Use list_collections to discover available collections. |
| query | string | yes | Search terms. AND-semantics by default; use or between terms for OR; wrap phrases in double quotes. |
| limit | integer | no | Maximum items to return (capped at 50 to fit MCP response-size budgets). |
| format | string | no | Output format for styledtext properties on the matched items. markdown is friendliest for AI consumption. |
| locale | string | no | BCP 47 locale tag. Accepted for forward-compat with the 3.6 i18n release — has no effect today. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search terms. AND-semantics by default; use or between terms for OR; wrap phrases in double quotes. |
| limit | integer | no | Maximum items returned in aggregate across all collections. Capped at 50 for MCP response-size budgets. |
| format | string | no | Output format for styledtext properties on the matched items. markdown is friendliest for AI consumption. |
| locale | string | no | BCP 47 locale tag. Accepted for forward-compat with the 3.6 i18n release — has no effect today. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Total CMS or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.0.1 · scanned 25 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digesta2f705b626dc9fcac66dc4dcf0803268708f2f6d6cfc00b7b1ca4c5b1b6337ea
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| describe_collection | no tags | |
| describe_view | no tags | |
| docs_get | untrusted-input | untrusted-input: keyword "fetch" |
| docs_lookup | no tags | |
| docs_search | no tags | |
| fetch | untrusted-input | untrusted-input: keyword "fetch" |
| find_comparison | no tags | |
| get_object | untrusted-input | untrusted-input: keyword "fetch" |
| get_resource | no tags | |
| get_view | untrusted-input | untrusted-input: keyword "fetch" |
| latest_release | no tags | |
| list_collections | no tags | |
| list_guides | no tags | |
| list_views | no tags | |
| needs_review | no tags | |
| query_collection | no tags | |
| query_view | no tags | |
| search | no tags | |
| search_collection | no tags | |
| search_collections | untrusted-input | untrusted-input: keyword "fetch" |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digesta2f705b626dc9fca
Scanned2026-10-25
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.1.
1.0.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Total CMS can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.