Cowboy MCP 1.7.7: sign-in on subfolder sites and strict hosts, Drafts only access, and API keys that get past stripped headers

Claude, ChatGPT and the other apps can now sign in to sites they could not reach before: WordPress in a subfolder, multisite subsites, and hosts or Cloudflare rules that block /.well-known/. A new Drafts only access level lets an AI write without publishing. API keys get through on hosts that strip the Authorization header, and when a first sign-in fails, the Connections tab says so and shows how to retry. Updating is recommended, and nothing needs doing afterwards.

Sign-in where it used to fail

Browser sign-in starts with the app reading a few small documents at the root of your domain, under /.well-known/. Three kinds of site could not serve them:

Cowboy MCP 1.7.7 adds a second sign-in address under /wp-json/ and works out by itself which one your host allows. There is nothing to configure, and apps that are already connected are never moved.

Two apps need a different step on a subfolder site:

Server names in the setup commands now include the folder (example-com-blog), so two sites on one domain do not collide.

Drafts only access

The consent screen and the API-key form gain a fourth access level next to Full access, Read-only and Custom. A Drafts only connection can create and edit drafts, but it never publishes anything or changes the live site:

When a first sign-in fails

If an app could not finish signing in, the Connections tab now tells you, and gives the one step to retry in that app, for example "in Claude, open Customize → Connectors, choose your site and click Connect".

The Connection Doctor names the host problem and its fix too. That includes a blocked /.well-known/ (with Cloudflare steps when Cloudflare fronts the site) and a stripped Authorization header. It also offers a one-click switch to the other sign-in address. The Cloudflare guide is updated to match.

API keys on hosts that strip the Authorization header

Some hosts remove the Authorization header before WordPress sees it, and some staging sites sit behind an HTTP password that takes the header for itself. A connection that uses an API key can now send it in an X-Cowboy-MCP-Key header instead:

--header "X-Cowboy-MCP-Key: YOUR_API_KEY"

An Authorization header still wins when both are sent. Apps that sign in through the browser always need the Authorization header to arrive, so on those hosts the Doctor's fix still applies.

Separately, some Apache hosts hid a valid key from WordPress, and connections failed with "Missing Authorization header". Those connections now work.

Setup steps that match the apps today

Changed

Update

Update from your WordPress dashboard like any other plugin, or install it from WordPress.org. The full changelog is there too.