Controlling Super Speedy Imports with MCP

Connect Super Speedy Imports to Codex or Claude Code and you can ask it to create and configure imports, migrate existing WP All Import jobs, preview the result safely, start an agreed run, and monitor it to completion.

Requires Super Speedy Imports 2.87.3 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 for Super Speedy Imports.

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 or reuses a dedicated Super Speedy Agent user, grants the selected plugin capabilities, and generates a revocable WordPress Application Password plus a version-pinned command for the shared Node.js 18+ bridge. ssi_run_imports and plugin installation are separate execute opt-ins. One connection exposes every permitted ability registered by the active Super Speedy plugins. If you later install or activate Imports, restart the assistant and use the same connection.

Useful requests

• “Migrate my imports from WP All Import to Super Speedy Imports.”
• “Create a product import from this CSV, auto-map it and show me anything ambiguous.”
• “Preview import 12 and give me the draft product links to check.”
• “Run import 12 after I approve it, monitor it, and explain any skipped rows or image failures.”
• “Why is the current import still running, and which stage is taking the time?”
• “Fetch the configured supplier feed, but do not start the import.”

Migrating from WP All Import

The migration workflow is designed to be conversational rather than a blind conversion:

1. The assistant lists the saved WP All Import jobs and identifies which local sources are available.
2. It inspects and analyses a selected job without returning credentials, raw configuration or PHP expressions.
3. It prepares an SSI import and compares the two configurations semantically.
4. It shows blockers and stable difference IDs. You choose how genuine differences should be resolved.
5. It applies only allow-listed decisions against the current analysis, refusing stale decisions if the source has changed.
6. It creates an isolated draft preview and gives you wp-admin and front-end links.
7. Only after you approve the result can it start the live import.

Preparing or migrating a job never starts a live import. The operation is idempotent by source job ID, so repeating discovery does not create uncontrolled duplicates.

Creating a new import

For CSV data, the assistant can upload or securely fetch the source, create an import and run the normal automatic mapper. It should report unmapped or ambiguous columns rather than invent a destination. Before editing mappings it should read the live configuration vocabulary and the current full configuration because mapping updates replace the supplied tree rather than merging arbitrary fragments.

For XML, the source remains canonical. The assistant can upload and validate the XML, analyse its repeating record path, convert it to a deterministic CSV working copy and link the two so the CSV can be regenerated when the XML changes.

The source abilities handle CSV and XML. A JSON or JSON Lines source is created through + New Import in wp-admin, or over restricted SSH by converting it with wp ssi convert-source feed.json and creating the import from the result with wp ssi create.

Previewing and running safely

Preview uses the existing Preview first item pipeline. It creates isolated draft content and returns review links; it does not update live content. Discarding a preview removes only drafts, attachments and unused terms recorded as owned by that preview.

Starting a run requires explicit confirmation and returns immediately. It launches the ordinary wp ssi <id> WP-CLI runner in the background, so there is no separate MCP import engine. The assistant must poll run status until the import is no longer running, then read history and import issues to verify the final result.

MCP ability groups

Discover the registered super-speedy-imports/... abilities from the connected site. Availability depends on the installed build.

Safety and permissions

Reading and authoring require ssi_manage_imports. Starting, aborting or deleting requires ssi_run_imports plus confirm: true on every call. Administrators receive both capabilities automatically. The dedicated Import Manager role carries only these import capabilities and WordPress read access, which is preferable for a long-lived agent account.

Additional server-enforced safeguards include:

• Agent-written configurations can never store PHP source or {function:...} mappings, and stored PHP is never returned.
• Remote downloads use WordPress’s protected download path and validate file names and content.
• Stored recurring-source credentials are used internally but never returned.
• Live runs refuse to start when another run is active or the source exceeds the default 2,000,000-row MCP ceiling (superspeedyimports_mcp_row_ceiling filter).
• An import migrated from WP All Import that still carries something that could not be translated is not run, by start-run, wp ssi or a schedule, until you complete it in the import’s configuration. The refusal names what is missing and points to Migration Tools > Review differences.
• abort-run stops further work at the next checkpoint; it does not roll back rows already written.
• Deleting an import removes its definition, history and staging tables, but not imported content or its CSV file.

When MCP does not cover the task

Use browser control when a human needs to judge previewed products, edit visual mappings, or handle a wp-admin feature not yet represented by an ability. Restricted SSH gives an assistant access to WP-CLI, server logs and database diagnostics, and can run the exact wp ssi command on a host that cannot launch background processes through PHP. SSH is powerful, so use a restricted account, protect the private key and avoid giving an assistant unrestricted root access.

Troubleshooting the connection

• If the super-speedy-imports/... abilities are missing, activate or update Super Speedy Imports and restart Codex or Claude Code.
• If the connection command cannot be generated, use HTTPS and check that WordPress Application Passwords are enabled.
• If start-run refuses because this host cannot create a background process, run the returned WP-CLI command through restricted SSH and continue monitoring through MCP.
• If a migration decision is rejected as stale, compare the source and SSI import again and use the new analysis hash.
• If a run appears complete, do not rely on the start response: check run status, history and import issues.

Further reading

Related products

Super Speedy ImportsEasy to use. Built for speed.

Written for Super Speedy Imports 3.40.0.