What we deliberately leave out

Half of a design is what it refuses. These are the things CTXR does not have and will not quietly grow — so nobody looks for them, and nobody builds a workaround that undoes the reason.

No plugins

Third-party code inside your site, updated on someone else’s schedule, breaking on yours. What a plugin would add lives in the theme, in your own files.

No accounts, no logins

No user table, no password, no session. People and agents act with keys that carry explicit rights and can be revoked without a trace. See Security without logins.

No API beyond the MCP

The MCP’s short list of verbs is the entire management surface (see Keys and the MCP): spoken as MCP, described in OpenAPI, but one set of verbs, not a bespoke API to learn and version.

No build step, no compile

See Render, don’t build.

No search engine

A word search over the index (?q=, the MCP’s search) and a map for AI assistants; that is the extent of it. Lists are curated by editors, and depth is exposed to machines that already know how to search. A site that needs full-text ranking hands its index to a service built for that.

No cart, no checkout, no customer accounts

A CTXR site can be a shop’s face — product pages, collections, the catalogue as structured data — but a cart, a checkout, payments and order history are platform logic and stay with the platform that owns them. The site renders the window and hands the transaction over: a link, a hosted checkout, an embedded widget. Visual and data, yes; transactional, no. See Coming from another platform.

No shared root between sites

See One site, one install.

No plan enforced against the owner

Limits keep a site fast and are applied where changes come in — never by a service that polices, never by removing what exists. See What a plan governs.

No silent fallbacks

A template does not invent missing data; a missing translation means the page is absent in that language; a check that cannot run means nothing goes live. A quiet fallback would hide the gap from the person who should fix it.

The rule for adding things

Each absence was once a request. The test is the first foundation: would an agent need this to read or operate the site? If it can be done with the files, a key and the protocol, it is a client or a theme — not an engine feature.