Cowboy MCP 1.7.5: upload files straight from ChatGPT, undo that checks its own work, and super-admin-only multisite

Files you attach in a ChatGPT conversation can now go straight into your Media Library, and any upload can be resized and converted on the way in. Every undo now reports whether the restored item matches what was saved before the change. This release also fixes four undo and preview bugs, puts multisite networks in the hands of super admins only, locks down WP-CLI and stored credentials further, and brings every connection screen in line with the AI apps as they look today.

Files from a ChatGPT chat go into the Media Library

Attach an image to a ChatGPT message and ask for it on your site: "Upload the photo I attached as WebP, 1600px wide, and set it as this post's featured image." ChatGPT hands the file to Cowboy MCP, which downloads it from OpenAI's short-lived link and adds it to the Media Library.

• Resize and convert any upload. wp_upload_media takes convert_to (WebP, AVIF, JPEG or PNG), max_width, max_height and quality for every source: a chat attachment, a URL or inline data. Conversion uses WordPress's own image editor, so the formats available are the ones your server supports.
• Safe by default. Downloads are capped at 50 MB, follow at most three redirects and are checked against private and internal addresses at every hop, even in Power mode. SVG, HTML, XML, JavaScript, CSS and PHP files are refused from a chat. The audit log keeps the download's host and path but drops the signed query string.
• Clearer errors. A path from ChatGPT's own sandbox, a missing link or an expired one now gets a plain explanation instead of a failed download. The result reports the file's MIME type, width and height.

Undo that checks its own work

After an undo, Cowboy MCP now snapshots the item again and compares it with the before-state it saved when the change was made. The result says verified: true or, on a mismatch, lists the fields that differ. The check is a report, not a gate: the undo itself runs exactly as before. The undo guide has the details of how per-change undo works.

Fixes

• Undoing a permanent comment delete brings the comment back. It reported success without restoring the comment.
• No false conflicts after pingbacks. Undoing an edit to a published post no longer reports a conflict once WordPress has sent the post's pingbacks.
• Dry runs tell the truth. Dry runs and safe-mode previews now check a call's arguments first, so they no longer promise success for a call the tool would refuse, such as an upload with unknown arguments.
• WordPress 7.2 image edits survive an undo. Undoing a media delete keeps the link between an edited image and its original.
• "Repair now" in every language. The notice is translated in all 12 bundled languages.

Multisite: super admins only

On a multisite network, Cowboy MCP is now managed by super admins only: its settings, API keys and the approval of new connections. Two fixes come with it. A checkpoint on the network's main site now holds only that site's tables; it used to include every site's tables and the network tables, and restoring an older checkpoint now restores only the current site. wp_delete_user removes a user from the current site only, as described, instead of deleting the account from the whole network.

Action needed on a network: API keys created before 1.7.5 or with WP-CLI, and connections approved by a site administrator, stop working until a super admin creates or approves them again. Single-site installs are not affected.

Tighter WP-CLI and credential handling

• Without Power mode, wp_cli db query runs read-only queries only, and wp_cli search-replace must name its tables and cannot change options, users or network tables.
• Passwords, licence keys and API tokens that other plugins store inside their settings (SMTP passwords, CDN tokens, payment keys) are hidden whenever an agent reads them.
• Option, ACF and WooCommerce customer writes are checked more strictly.

The security page is updated to match.

Every connection step, re-checked

All 17 panels on the Connections tab were checked against the AI apps on 26 October, and the ones that had moved now say what you will see:

• Gemini app: custom servers now live under Customize → Connectors → + Custom; the old Connected Apps page redirects there.
• Perplexity: Plugins → Add custom → Add MCP connector (Remote, if asked) on accounts that have the new Plugins page; Customize → Connectors elsewhere.
• ChatGPT: click Add (or +) under Plugins, then start a new chat and type @ with the plugin's name.
• Claude: on Team and Enterprise, the organization owner's path is Add → Custom → Web.
• n8n: the credential type is MCP OAuth2, with Dynamic Client Registration on.
• VS Code: check the connection with Chat: Open Customizations → Tools; errors are under MCP: List Servers → Show Output.
• Muse: Meta offers Muse in the United States and Canada, and the approval choices are Allow once, Allow for this site and Always allow.
• Grok: connectors are available on every Grok plan, the free plan included.
• Opencode: the command now adds --global, because Opencode 2.x otherwise writes the server into the current project; on Opencode 1.x, leave the flag out. A second line, opencode mcp auth, opens the sign-in.

Update

Update from your WordPress dashboard like any other plugin, or install it from WordPress.org. The full changelog is there too, and every app's setup is compared on the connect hub.