Skip to content
Ordomat
Contents

Ordomat / Documentation

Documentation

Install, connect, and know exactly what the assistant can do on your site. Ten minutes to read it all, two to be up and running.

What Ordomat is

Ordomat is a WordPress plugin that exposes your site to an assistant as named, documented tools. The assistant guesses nothing: it calls a tool, with precise parameters, and gets an answer.

The plugin contains no artificial intelligence. It calls no service. It waits to be spoken to, and checks every request before answering it.

The default client is Claude Code, on your own computer. Any client that speaks the Model Context Protocol will do.

Install the plugin

Two minutes, no command line.

  1. Download the packageVersion 1.0.0, from this page. Free, under the GPL, no account to create.
  2. Upload itIn your admin: Plugins, Add New Plugin, Upload Plugin, then Install Now.
  3. ActivateA new Ordomat menu appears in the left column.
  4. Open the connectorOrdomat, Settings. It arrives closed: pick the usage mode that suits you.

You need WordPress 6.9 or newer and PHP 7.4 at least. The diagnostics screen tells you if something is missing.

Connect your assistant

The Connection screen builds the command for you. There is nothing to compose by hand.

  1. Create a tokenOrdomat, Connection, New token. Choose its profile and how long it lasts.
  2. Copy the commandIt appears once, token included. The token is never shown again.
  3. Paste it into a terminalOnce. Claude Code remembers the connection.
claude mcp add ordomat \
  --transport http https://your-site.com/wp-json/ordomat/v1/mcp \
  --header "Authorization: Bearer your-token"

For another client, the same screen offers a configuration file to drop in. And if your client reads the WordPress core Abilities API, the tools are declared there too.

The 87 tools

Sorted into eleven families. Each tool states its scope, its profile and its parameters, and each one can be switched off on its own from the Tools screen.

A tool moves to Pro as soon as it writes executable code, touches the whole database, schedules a deferred action, or reads operational data.

Read and inventory

8 tools

Posts, pages, media, taxonomies, accounts, settings, site health, dead links. Everything that answers “what is on this site”.

Write and publish

13 tools

Create, edit, schedule, unpublish. Drafts, excerpts, featured images, categories and tags.

Fix in bulk

3 tools

Search and replace, preview required. The editorial audit that proposes, shows, then applies if you say so.

Run the site

16 tools

Menus, accounts, roles, settings, permalinks, comments, custom fields. The daily plumbing.

Shop

9 tools

WooCommerce: products, variations, orders, sales, discount codes, settings. Reading first, writing with Pro.

Design

13 toolsOrdomat Pro

Block theme, palette, typography, templates, patterns. Elementor and Beaver Builder globals.

Code

6 toolsOrdomat Pro

The child theme and your own plugin: PHP, CSS, JavaScript files. Everything goes through a sandbox that checks every path.

Automate

9 toolsOrdomat Pro

Scheduled tasks, signed webhooks, reactions to a site event. What must happen when you are not there.

Maintain

4 toolsOrdomat Pro

Plugins, themes, updates, clean-up. The things we put off until they break.

Diagnose

4 toolsOrdomat Pro

Error log, performance, plugin conflicts. What answers “why did the site go down”.

Export and import

2 toolsOrdomat Pro

Content both ways, and a database export. To migrate, to archive, or to sleep well.

What you can ask for

You state the outcome you want, in your own words. Turning that into tool calls is the assistant's job.

Write and fix

“Draft five posts on this topic, with their categories.”

Audit

“Which posts have images with no alt text?”

Replace in bulk

“Replace the old name everywhere, but show me first.”

Build a page

“A home page: banner, three arguments, call to action.”

Run the shop

“Twenty percent off this category until Sunday.”

Investigate

“The site went down around two. What changed?”

The three barriers

Every call passes them in order. The strictest one wins, always. The assistant can never do more than the account it borrows.

  1. The site usage modeSet in the settings, it applies to everyone. In read-only mode, no writing tool exists at all, not even for an administrator.
  2. The token profileEach token carries its own. A read token stays a read token, whatever account created it.
  3. The WordPress account's capabilitiesThe token borrows an account. What that account cannot do in the admin, the assistant cannot do either.

A refused tool says which of the three barriers stopped it. You never have to guess.

Tokens

Your password never leaves WordPress. The assistant presents a token, and nothing else.

  • It shows once, when created.
  • It is stored hashed: reading your database will not recover it.
  • It carries a profile, a lifetime and an account.
  • It is revoked in one click, and stops working at once.
  • An emergency stop closes the connector and revokes every token at the same time.

Dry run before writing

Every tool that changes something can first describe what it would do, touching nothing. The parameter is injected by the framework, never copied tool by tool: none of them can forget it.

{
  "tool": "content_replace",
  "arguments": {
    "search": "old name",
    "replace": "new name",
    "dry_run": true
  }
}

The answer lists what would change, item by item. Nothing is written until you say yes. Bulk replace even refuses to run if no preview was asked for.

The log

Every call is recorded, refusals included: the account, the tool, the originating address, the duration, what changed. Secrets are masked as they are written, never stored in the clear.

The Log screen filters by tool, by account and by outcome. The dashboard draws from it the count for the last seven days and the success rate.

Compatibility

Ordomat reads content where it actually lives, not where an assumed format would put it. That is what lets audits and link checks tell the truth on a site built with a page builder.

Block editor

Full reading and writing, templates and patterns included.

Elementor

Reading everywhere. Layout building through its own model, with Ordomat Pro.

Beaver Builder

Reading everywhere. Layout building with Ordomat Pro.

Divi and the rest

Reads the real text. When writing is not safe, Ordomat says so and names the builder.

WooCommerce

Products, variations, orders and sales, read only. Writing and promotions with Ordomat Pro.

ACF and custom fields

Reading and writing fields, by their key.

WordPress 6.9 or newer, PHP 7.4 at least. No theme is imposed, no page builder is required.

Licence and updates

The free plugin is downloaded from this site, and every version stays available there. The What's new page says what changed.

Ordomat Pro updates from our own server, and only while your licence is active. The Licence screen shows its state, the product bought, the renewal date and the sites using it. A place frees up and moves elsewhere at any time.

A licence that runs out switches nothing off. The tools stay in place and keep working: only updates and support stop.

What Ordomat does not do

Ordomat lives inside WordPress. It does not replace SSH access, and we would rather write it here than let you find out.

  • System cron, the server's scheduled tasks rather than WordPress ones.
  • Server configuration, the PHP version, system extensions.
  • DNS, certificates, domain redirection.
  • Your host's backups, and restoring them.
  • Bulk email, which belongs to your email tool.

What's new

1.0.3 30 September 2026

  • The connection screen gives one path per client, Claude Code, a single project, Claude Desktop and Cursor, or by hand, each with its own three steps.

1.0.2 30 September 2026

  • Comment moderation is paginated and searchable: hundreds of pending comments no longer take four round trips.
  • A featured image can be set from the library, which no tool allowed before.
  • Discussion settings are writable: link threshold, disallowed words, words that hold a comment.
  • A category description can be written, where many themes display it.
  • A redirect loop is named instead of leaving the site for dead, and a link refused by a remote server is no longer counted as broken.
  • The connection test tries both headers, reads every schema as a client would, calls a tool for real, and asks the internet for every folder the plugin writes into.
  • An email warns a token's owner the first time it answers from a new address.
  • The log filters by kind of action, and the dashboard announces the widest mode.

1.0.1 30 September 2026

  • Fixed: tools with no parameter sent an empty JSON array instead of an empty object. A strict client then rejected the whole list, and no tool was usable at all.
  • Security: the backup folder is now proven closed before a backup is written into it. On nginx its guard files are never read, and a full copy of the site became downloadable.
  • Fixed: the token is also read from the raw request headers. Hosts that strip the Authorization header before PHP no longer need an .htaccess rule.
  • Fixed: a replace preview is kept in the database rather than a transient, which an object cache could lose. Unknown and expired no longer say the same thing.
  • Fixed: link checking stops after a time limit and returns what it found, instead of never answering when a remote server goes silent.

1.0.0 25 September 2026

  • First public release.
  • 87 tools in eleven families, each one switchable on its own.
  • MCP entry point in JSON-RPC over the REST API, mirrored in the core Abilities API.
  • Hashed tokens, with a profile and a lifetime, plus an emergency stop.
  • Dry run required before any bulk write.
  • A log of every call, refusals included.
  • French and English.