Read + write ACSS palette / type / space / radius / breakpoint vars.
Agents understand Automatic.css and can safely operate on it at scale — something no generic AI can do.
Read and write Automatic.css data through typed, schema-validated calls.
Apply changes across hundreds of records in one operation.
Create, update and configure Automatic.css — not just read it.
Feed Automatic.css values into templates, query loops and other tools.
Scoped tokens and draft-mode keep large edits under control.
No exports, no SQL, no brittle scripts — just protocol.
Ask in plain language and the Automatic.css integration turns it into a couple of typed calls — no exports, no SQL, no plugin spelunking.
Populate or update a field across an entire dataset at once.
Have an agent draft and fill structured Automatic.css data from a brief.
Find empty or inconsistent records and fix them in place.
Chain Automatic.css actions into multi-step agent workflows.
The NibWP Automatic.css AI automation integration exposes Automatic.css to any MCP-compatible AI agent — Claude, Cursor, Claude Code or your own — as typed, schema-validated tools. Instead of clicking through Automatic.css or writing custom code, you describe what you want in plain language and the agent reads and writes real Automatic.css data over the Model Context Protocol (MCP).
It runs on the NibWP Pro plan and activates the moment Automatic.css is detected, exposing every tool with scoped tokens, draft-mode and an audit log so automation stays safe. Pair it with the ACSS Pro Skill and WooCommerce integrations to automate design-system end to end, or browse all NibWP integrations and the open Novamira alternative.
| Tool | Type | What it does |
|---|---|---|
| nibwp/automaticcss-list | read | List Automatic.css records via typed MCP calls. |
| nibwp/automaticcss-get | read | Read Automatic.css records via typed MCP calls. |
| nibwp/automaticcss-create | write | Create Automatic.css records via typed MCP calls. |
| nibwp/automaticcss-update | write | Update Automatic.css records via typed MCP calls. |
Did in seconds what used to take our team a full day with Automatic.css.
The agent reads our Automatic.css model and operates on it correctly every time.
No more CSV round-trips — Automatic.css edits happen through the agent.
Yes — once Automatic.css is installed, NibWP detects it and its abilities go live instantly.
Yes — it exposes both read and write tools, with destructive actions clearly flagged.
Scoped tokens, rate limits and draft-mode keep large operations controlled and reversible.
No — the Automatic.css integration works on Pro. Pro Skills are for design-to-build builder output.
Activate the integration and it's live on your MCP endpoint instantly.