Auto Infinite Scroll

Controlling Auto Infinite Scroll with MCP

Published · Last updated

Connect Auto Infinite Scroll to Codex or Claude Code and you can ask it to diagnose an archive that will not load the next page, inspect the selectors on the live page, and apply the corrected configuration for you.

Requires Auto Infinite Scroll 1.72 or newer and WordPress 6.9 or newer.

Connect once for all Super Speedy plugins

MCP setup is shared across the Super Speedy range. You do not need a separate bridge or connection for Auto Infinite Scroll.

  1. Install any Super Speedy plugin, open Super Speedy, and enter your licence.
  2. Open Super Speedy > MCP setup.
  3. Generate the connection commands and copy the command for Codex or Claude Code.
  4. Paste it into your terminal, then restart the AI assistant.

The setup page creates a revocable WordPress Application Password for the current administrator. One connection exposes the documented tools from every active Super Speedy plugin. Installing or activating another plugin adds its tools to that same connection.

Useful requests

  • "The shop archive stops after page one. Find out why and fix it."
  • "Add infinite scroll to my blog without changing the shop behaviour."
  • "Check whether my container, item and next-page selectors match the current archive."
  • "Show me the proposed Auto Infinite Scroll changes before applying them."

What the assistant should do

A safe diagnosis starts by reading the current configuration. It then inspects a same-site archive using the stored selectors, reports the match counts and suggests better candidates where a selector matches nothing. It should show you the proposed change before updating the configuration, then inspect the archive again to verify the result.

Custom selectors are appended to the built-in selectors by default. This lets the assistant add support for another archive without removing the WooCommerce defaults.

MCP abilities

AbilityPurpose
get-configRead every setting, its default, meaning, confirmation status and the effective merged selectors.
inspect-archiveInspect a post-type archive or same-site URL, count selector matches and suggest selector candidates.
update-configUpdate recognised settings using the same validation rules as the settings screen.

These abilities use the auto-infinite-scroll namespace. The shared controller discovers them automatically, so the site owner should not have to configure the namespace or endpoint.

Safety

The abilities require ais_manage, which administrators receive automatically. inspect-archive accepts same-site URLs only. Changing Replace CSS requires explicit confirmation because it discards the built-in selectors; ordinary custom-selector changes keep the defaults.

When MCP does not cover the task

Ask the assistant to use browser control when the problem is visual, depends on a cookie banner, or needs interaction with a page builder. Restricted SSH can help with server logs or WP-CLI, but is not needed for normal Auto Infinite Scroll setup.

Troubleshooting the connection

  • If the tools are missing, confirm the plugin is active and current, then restart Codex or Claude Code.
  • If connection generation is unavailable, use HTTPS and check that WordPress Application Passwords are enabled.
  • If an inspection reports zero matches, give the assistant the exact archive URL and ask it to inspect that page before changing anything.

Further reading

Understand the shared connection, permissions and alternatives.
Set up the plugin manually and learn how its selectors work.

Comments

▲
▼
1/1