Controlling filters with an AI assistant

You can ask Codex or Claude to inspect, plan, create and maintain your Super Speedy Filters setup without learning the individual tool names. The recommended route is MCP because the filter actions are structured, permission-controlled and return exact results the assistant can verify.

Chrome is simpler for occasional work and can operate every screen in the WordPress dashboard. Restricted SSH is another option for developers because Super Speedy Filters includes WP-CLI commands. The general guide, Setting up a store with an AI assistant, compares all three routes.

Connect once, then ask for the result

1. Install any Super Speedy plugin.
2. Enter your licence on the Super Speedy Plugins settings page.
3. Open the MCP setup page and copy the command shown there.
4. Paste the command into your terminal.
5. Ask Codex or Claude to inspect your current Super Speedy Filters setup.

You do not need to create a manual sequence of MCP calls. Starting with one Super Speedy plugin is enough because the shared tools can install Super Speedy Filters through the site’s licence, with your confirmation, when the job requires it.

What you can ask it to do

Try requests such as:

• Inspect my current filters and tell me what needs attention. Do not change anything.
• Plan a sensible filter set for my WooCommerce catalogue and show me the plan.
• Configure my filters from the catalogue, then verify where each filter appears.
• Preview the colour filter with red and blue selected and show me the resulting URL.
• Make this one filter use image tiles, but leave my other filters alone.
• Move my old per-filter swatch colours onto the product attribute terms. Dry run first.
• Rebuild the Super Speedy Filters lookup tables after my import and check the status.

The assistant translates those requests into the appropriate read, plan, preview and writing actions. Technical ability names are documented below, but they are not commands the site owner needs to type.

How automatic filter setup stays predictable

For a whole-store setup, the assistant does not invent a filter configuration. Auto Configure’s deterministic classifier decides which taxonomies need filters, their display types, placement, layout and category conditions. MCP, the settings-page button and wp ssf autoconfig all invoke the same decision engine.

The assistant can make a targeted edit to an existing filter, but that route is bounded. It accepts only known settings and valid values, reports invalid choices, and records the result as a human edit so a later Auto Configure run leaves it alone. Custom CSS is also contained beneath Super Speedy Filters’ own selectors instead of being allowed to affect unrelated parts of the site.

A typical conversation

You can simply ask: Set up sensible filters for my catalogue, but show me the plan first.

Behind that request the assistant will normally:

1. inspect the plugin edition, add-ons and lookup-table status;
2. list the catalogue taxonomies and available placement targets;
3. generate the dry-run plan and explain the important decisions;
4. wait for approval before creating or replacing filters;
5. run Auto Configure;
6. list and preview the finished filters to verify the result;
7. make any requested targeted adjustments without rebuilding hand-edited filters.

You should not have to tell it to run those seven actions individually. They are documented so you know what a good assistant should do and can challenge it if it skips planning or verification.

What the managed filter tools cover

Super Speedy Filters currently exposes 18 filter abilities.

Classic widget filters and ssf/filter blocks inside block-theme templates use the same managed surface, so the assistant can see and edit both storage types.

The shared ssp/ tools carried by every Super Speedy plugin can list the plugin range, check the licence, install another Super Speedy plugin and show the installation log. Plugin installation uses the licensed update server, requires explicit confirmation and does not accept an arbitrary download URL.

The safety rails

• A dedicated Filter Manager role. Give the assistant filter access without giving it a full administrator account. The role uses separate read/author and write capabilities.
• A dry run before writing. plan-filters returns the complete proposal and evidence without creating filters.
• A ceiling on bulk creation. Auto Configure will not create more than 40 filters in one MCP run unless that ceiling is explicitly overridden.
• Explicit confirmation. Undoing an Auto Configure run and installing a plugin require a deliberate confirmation step.
• Surgical undo. Undo removes what the last automatic run created while preserving filters and layout work added by hand.
• Hand edits survive. Filters changed manually or through a targeted assistant edit are not overwritten by a later automatic run.
• Scoped CSS. Custom selectors are rewritten beneath the plugin’s filter containers; attempts to style the body, header or checkout are rejected.
• Review after writing. The assistant can list and preview the filters it created, and the same configuration remains visible in WordPress.

Using Chrome instead

Chrome is the quickest route if you do not want to configure MCP. Sign in to WordPress yourself, give Codex or Claude browser access, and ask it to use the Super Speedy Filters screens. It can run Auto Configure, review the previews, edit a filter and check the result using the same interface you would.

Browser control also covers settings or third-party plugin screens that no MCP ability exposes. The trade-off is that it depends on the current dashboard layout and works through visual forms, so it is slower and less structured for a large or repeated job.

Using SSH and WP-CLI instead

Developers with restricted SSH access can use the command line. Super Speedy Filters provides wp ssf autoconfig --dry-run to print the proposed configuration and its reasons without writing, then wp ssf autoconfig to apply it. Through SSH the assistant can also install or update plugins, inspect logs and use other server tools allowed by the account.

SSH is broader than MCP. Use a dedicated non-root user, key authentication, staging and a current backup. Start with an inspection-only request and require approval before plugin installation, updates, code changes or database work.

Troubleshooting

• No filter tools appear: Confirm WordPress 6.9 or newer, update Super Speedy Filters, copy the current command from the MCP setup page and reconnect the assistant.
• The assistant is denied: Use an administrator for a short staging test, or give the dedicated user the Filter Manager role.
• Category conditions are missing: Rebuild the lookup tables. Without that data, Auto Configure keeps filters store-wide rather than guessing from missing counts.
• A planned filter is unexpected: Ask the assistant to show the evidence for that taxonomy and compare the same plan in the Auto Configure review screen before approving it.
• A targeted setting is rejected: Ask for the valid values returned by describe-filter-config; unknown settings and invalid enum values are deliberately refused.
• MCP does not expose the screen you need: Use Chrome for that dashboard task or restricted SSH for a genuine command-line or server task.

Further reading

Related products

Super Speedy FiltersFast product filters and pretty, indexable permalinks on every archive