Publish HTML, Markdown, KV, JSON, and files to brewpage.app from AI assistants. No signup.
Nothing to run from here
Caelo 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.
94/100
trust score
402
downloads a day
local
runs on your machine
7k
downloads in 30d
What it does
Edit a self-hosted Caelo CMS site from your agent. Changes land in a draft; a human publishes.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'CAELO_ADMIN_URL=${CAELO_ADMIN_URL}' --env 'CAELO_MCP_TOKEN=${CAELO_MCP_TOKEN}' --transport stdio caelo-cms-mcp '--' npx -y --package=@caelo-cms/mcp-server caelo-admin-mcp
# 2 — ask your agent for something these tools do
# caelo_upload_images, caelo_chat, caelo_await_approval and 2 more
It needs CAELO_ADMIN_URL, CAELO_MCP_TOKEN: this reads them from your environment, so export them first.
Caelo 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
CCAll 1 server
caelo-cms1 server
1 category
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. This one runs on your machine: your client starts Caelo CMS as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads CAELO_ADMIN_URL (Your Caelo admin's https:// address, e.g. https://admin.example.com), CAELO_MCP_TOKEN (MCP token minted at /settings/mcp on your install) from your environment each time it starts the server, so the value stays out of its config: export them in your shell profile (macOS, Linux), or run setx CAELO_ADMIN_URL …, setx CAELO_MCP_TOKEN … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'CAELO_ADMIN_URL=${CAELO_ADMIN_URL}' --env 'CAELO_MCP_TOKEN=${CAELO_MCP_TOKEN}' --transport stdio caelo-cms-mcp '--' npx -y --package=@caelo-cms/mcp-server caelo-admin-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: CAELO_ADMIN_URL — Your Caelo admin's https:// address, e.g. https://admin.example.com; CAELO_MCP_TOKEN — MCP token minted at /settings/mcp on your install. You set them in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
5 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.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Upload 1–4 PNG, JPEG, WebP or GIF images (5 MiB each) to the Caelo media library. Prefer filePath for files on the machine running this MCP server; otherwise supply raw base64 (no data URL). Files become shared CMS media assets. Set reference: true for images that only guide image generation or…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| images | array | yes | — |
Talk to your Caelo CMS install's AI agent. Same agent that powers the live-edit chat overlay — it can read pages, propose edits, queue Owner-approval proposals, summarise plugin data. Continues an existing chat session (when chatSessionId is supplied) or starts a fresh one. Returns the agent's…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| attachments | array | no | Attachments returned by caelo_upload_images. |
| message | string | yes | What you want to say to the Caelo agent. |
| chatSessionId | string | no | Optional. Chat session UUID to continue. Omit to start a fresh page-unbound chat. |
| pageId | string | no | Optional. Bind a NEW chat to one page so the agent's page-context block is populated. Same shape as /edit?page=<id>. |
Wait for the operator's Approve/Reject on the approval cards your caelo_chat turn paused on, then continue that turn and return its reply (the change applied, or the agent's reaction to a rejection). Use it when a caelo_chat reply says it is still waiting for approval. You cannot approve anything…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chatSessionId | string | yes | The chatSessionId from the caelo_chat reply that is waiting. |
Open the Caelo work session your subsequent tool calls run in. Every write lands in the site's shared draft — invisible to the live site until it is staged and the operator clicks Publish live in the Caelo admin. Call this ONCE before any other caelo tool. By default it RESUMES the operator's own…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | no | Session title shown in the Caelo admin chat list. |
| pageId | string | no | Optional page UUID to bind the session to. |
| chatSessionId | string | no | Resume this specific session instead of the most recent one. |
| newSession | boolean | no | Open a fresh session instead of resuming the most recent open one. |
Fetch the Caelo install's composed site context: how pages/modules/content instances fit together, the tool playbook, staging rules, site memory (brand voice, glossary) and the active skills index. Load this once before working; load individual skills on demand via the load_skill tool.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MPL-2.0
- Runs on your machine — nothing of it reaches our gateway
- 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 Caelo 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: —
ATrust score 94 / 100
Release 0.11.5 · scanned 30 Oct 2026
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 score94
Findings1 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationsource
Surface digest99762626cfd141eb25c9e921a81707bb70269472e951dee4d9dc4fde68d046f2
Score vectorthreat 100 → client 94
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
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. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
can execute shell commands or code
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 digest99762626cfd141eb
Scanned2026-10-30
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
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.11.5. Pin a release below and the command asks for exactly that one.
0.11.5
30 Oct 2026
latestNo release note was published with this version.
0.11.3
29 Oct 2026
No release note was published with this version.
0.11.2
28 Oct 2026
No release note was published with this version.
0.11.1
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
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 Caelo 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.