What 1.7.6 changes: an OAuth token now works on the MCP route only
Before 1.7.6, an OAuth token for the MCP endpoint also signed its holder in on other parts of a WordPress site. What it reached, what changed, and what else shipped.
Read moreBefore 1.7.6, an OAuth token for the MCP endpoint also signed its holder in on other parts of a WordPress site. What it reached, what changed, and what else shipped.
Read moreWordPress hands back the same value for "there is nothing here" and "the question could not be asked". Nine review rounds on version 1.7.5 kept finding the same bug wearing a different costume, including one where a failed consent lookup read as consent granted.
Read moreThe sign-in screen now identifies a connector by its verified redirect host rather than the name it sends, and the Activity Log records every MCP request that reaches WordPress.
Read moreA default of ours stopped ChatGPT connecting. Also fixed: a mangled redirect address, a session ID handed back for a session that was never written, and a tool list that could exhaust memory.
Read moreA completed sign-in with no ability calls after it means the request never reached WordPress. How to read that signal in the Activity Log, confirm it at the CDN, and fix it.
Read moreVersion 1.7.0 closes an OAuth revocation race, stops a payment gateway credential leak, and fixes four ACF writes that were destroying content.
Read moreA user-reported OAuth bug and six related fixes bring error responses, discovery, and tool status codes in line with what MCP and OAuth clients expect.
Read moreVersion 1.4.0 adds a one-screen Quick Connect wizard that gets an agent connected fast, without loosening the off by default governance underneath.
Read moreIn 1.3.0 we turned OAuth off by default and fixed real security gaps in our own plugin, patched in the open. Here is what changed.
Read moreTwo honest ways to connect an AI agent to your WordPress site, what each one is good at, and how to pick the one that fits your setup.
Read more