Cowboy MCP 1.6.3: local development, first-class

Cowboy MCP 1.6.3 is about the site on your laptop. A local WordPress install — Local, Studio, MAMP, DevKinsta, or anything on localhost — now works just as well with your AI agent as a live one: Claude Code, Cursor, Codex, and Gemini CLI connect with an API key exactly as they do in production, Claude Desktop connects through a small local bridge, and the plugin's own tooling knows which is which. The release is also tested against WordPress 7.1.

What this means for you

Until now the Connection tab and Connection Doctor assumed a public HTTPS site, so on a local install you got a fail for "hostname not publicly reachable" and a Claude Desktop setup that could not work without a tunnel. This release makes local development a first-class story: the plugin recognises a local site, tells you per client what works locally and what genuinely needs a public URL, and hands you the right config for each — with no tunnel exposing your dev site while you work.

What's new

Try it

claude mcp add --transport http my-local-site http://mysite.local/wp-json/cowboy-mcp/v1/endpoint --header "Authorization: Bearer YOUR_API_KEY"

Then: "List every page that is still a draft and tell me which ones have no featured image."

Read the full 1.6.3 changelog on WordPress.org.