Operations integration
FlyingPress MCP
FlyingPress keeps one flat config in its option and loads it into its own Config class at start-up. WP MCP Pro adds a settings pair plus a preload on the theme dispatcher: get-flyingpress-settings reports a summary and every allowlisted setting, with the license key, the FlyingCDN API key and the Cloudflare credentials reported masked; set-flyingpress-settings changes them through Config::update_config() as the plugin's own save does, so its .htaccess, drop-in and purge listeners run, snapshotted on the option so rollback-operation reloads the restored config and fires the same action. The CDN type, image optimizer, object cache and Cloudflare page caching stay read-only, since switching them reaches external services or writes drop-ins. preload-flyingpress-cache runs FlyingPress's own preload, queueing every public URL to warm the cache in the background; a preload is not snapshotted, since warming the cache destroys nothing. Writes are off until a site opts in, and every op runs at manage_options.
What your AI can do
Real FlyingPress operations, every write reversible.
- Read a summary and every allowlisted FlyingPress setting, credentials masked
- Change lazy load, minify, delay JS, CDN and preload settings, snapshotted
- Start FlyingPress's cache preload to warm every public URL
- Roll back any settings change exactly
Example prompts
Example FlyingPress prompts.
Show me the FlyingPress settings.
Turn on CSS and JavaScript minification in FlyingPress.
Start the FlyingPress preload now that the redesign is live.
Under the hood
The FlyingPress calls, under the hood.
theme-read({ operation: "get-flyingpress-settings" }), allowlisted; license and CDN keys masked
theme-write({ operation: "set-flyingpress-settings", args: { values: { minify_css: true } } }), Pro; opt-in; via Config::update_config, snapshotted
Part of WP MCP Pro
The FlyingPress integration is part of WP MCP Pro.
One Pro licence unlocks the FlyingPress tools and every other Pro integration on this site: Elementor deep editing, the other page builders, the forms adapter pack and more, 133 Pro tools in all. The free plugin still covers the rest of WordPress and the full snapshot and undo engine, so you can try the safety model before you buy.
Frequently asked
FlyingPress MCP: questions, answered.
Can the FlyingPress integration change the CDN or object cache?
No. The CDN type, image optimizer, object cache and Cloudflare page caching stay read-only, since switching them reaches external services or writes drop-ins. The license and CDN and Cloudflare credentials are only ever reported masked.
On FlyingPress, is a preload reversible?
A preload is not snapshotted, since warming the cache destroys nothing, and the reply says so. A settings write, by contrast, is snapshotted and one click from restored.
Related integrations
More integrations for the same agent.
MCP for WP Rocket
FreeOperations, 4 tools.
MCP for W3 Total Cache
FreeOperations, 2 tools.
MCP for LiteSpeed Cache
FreeOperations, 4 tools.
MCP for WP Fastest Cache
FreeOperations, 2 tools.
MCP for Perfmatters
ProOperations, 2 tools.
MCP for UpdraftPlus
FreeOperations, 2 tools.
Browse the full Integrations hub, or read more on the WordPress MCP plugin.