Update README.md for WordPress 6.9/7.0 changes

[itsgajendraSingh]

Fixes #164. Extends #150. Related: #101.

Updates the README to reflect changes since the Abilities API merged into WordPress 6.9 core (Dec 2025) and the WordPress/abilities-api repo was archived (Feb 2026).

Changes

1. Abilities API still listed as a separate required dependency — repo was archived Feb 2026
2. composer require command includes wordpress/abilities-api (archived package)
3. No WordPress minimum version listed — only PHP >= 7.4
4. .wp-env.json example includes WordPress/abilities-api in plugins array
5. Basic Usage says all abilities are "automatically available" — missing meta.mcp.public requirement
6. Code example missing meta.mcp.public flag — ability won't appear on default server without it
7. Abilities API docs link points to archived GitHub repo instead of core dev notes
8. STDIO transport labeled "Testing Only" — it's the primary local dev transport for Claude/Cursor/VS Code
9. No explanation of what the @automattic/mcp-wordpress-remote proxy does

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Unlinked Accounts

The following contributors have not linked their GitHub and WordPress.org accounts: @ovidiu-galatan.

Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Unlinked contributors: ovidiu-galatan.

Co-authored-by: itsgajendraSingh <gajendrasingh@git.wordpress.org>
Co-authored-by: galatanovidiu <ovidiu-galatan@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[Copilot]

Pull request overview

This PR updates the README.md documentation to reflect changes in WordPress 6.9/7.0 compatibility, specifically addressing the merging of the Abilities API into WordPress core, the archiving of the WordPress/abilities-api repository in February 2026, and the inclusion of the MCP Adapter in WordPress 7.0 core.

Changes:

• Added WordPress version requirement (>= 6.8, with 6.9+ recommended and 7.0+ bundled) and updated Abilities API documentation to reference core dev notes instead of the archived plugin repository
• Updated composer require command to remove the archived wordpress/abilities-api package with conditional installation notes for WordPress 6.8
• Removed WordPress/abilities-api from .wp-env.json example with a note for WordPress 6.8 compatibility
• Clarified that the meta.mcp.public flag is required for abilities to appear on the default MCP server, with updated code examples
• Updated STDIO transport documentation from "Testing Only" to "Local Development" and added explanation of the @automattic/mcp-wordpress-remote proxy
• Added WordPress.com MCP support information and v0.3.0 migration guide reference

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.25%. Comparing base (33659df) to head (368e1cf).
⚠️ Report is 6 commits behind head on trunk.

Additional details and impacted files

@@             Coverage Diff              @@
##              trunk     #165      +/-   ##
============================================
+ Coverage     88.04%   88.25%   +0.21%     
- Complexity     1236     1243       +7     
============================================
  Files            54       54              
  Lines          4022     4035      +13     
============================================
+ Hits           3541     3561      +20     
+ Misses          481      474       -7     

Flag	Coverage Δ
unit	88.25% <ø> (+0.21%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 3 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[galatanovidiu]

Thanks for the PR and for catching several real gaps in the README. There are a few things that need fixing before this can be merged.

Core inclusion claim (blocking)

The MCP Adapter is not part of WordPress core. It's a standalone package/plugin. References to it being "bundled in core" or "shipped in WordPress 7.0" need to be removed. This appears in:

• Dependencies: 7.0+ includes the MCP Adapter in core
• Installation note: On WordPress 7.0+, the MCP Adapter itself is bundled in core
• PR description: the MCP Adapter shipped in WordPress 7.0 core (April 2026)
• The "client-side JavaScript counterpart" paragraph and link are tied to the same claim

The Abilities API is in core since 6.9, but the MCP Adapter itself is a separate standalone package/plugin. These are two different things.

Protocol versions (non-blocking)

The PR mentions support for 2025-06-18 and 2025-11-25, but McpVersionNegotiator also supports 2024-11-05. Either list all three or use something like "supports multiple MCP protocol versions" without implying the list is exhaustive.

What's good here

The meta.mcp.public documentation, STDIO relabeling to "Local Development", WordPress.com MCP note, v0.3.0 migration link, abilities-api removal from default install, and the proxy explanation are all accurate and useful. I'd like to keep those.

[galatanovidiu]

Hey @itsgajendraSingh, quick ping. I'd like to land this in v0.5.0, which I'm tagging today.

The only blocker is the "bundled in WP 7.0 core" wording. The Abilities API is in core since 6.9, but the MCP Adapter itself is still a standalone package, so those lines need to come out.

If it's easier, I can push the fix to your branch directly. Let me know, otherwise I'll go ahead later today so it makes the release.

[itsgajendraSingh]

Hey @galatanovidiu, thanks for the ping and for the patient review!
Apologies for the "bundled in WP 7.0 core" wording — that was my mistake. I'll push the fix to my branch shortly so it can make v0.5.0.

[itsgajendraSingh]

@galatanovidiu I've pushed the fixes. Removed all "bundled in WP 7.0 core" references and updated the protocol versions line to "supports multiple MCP protocol versions" per your suggestion. Ready for another look.

[galatanovidiu]

Thanks for the quick turnaround — all feedback addressed. I also edited the PR description to match what this PR actually implements (removed the claim that the MCP Adapter ships in WordPress 7.0 core — the Abilities API is in core since 6.9, but the MCP Adapter itself remains a standalone package). Ready to merge.

[galatanovidiu]

Pushed a small follow-up commit (368e1cf) directly to this branch rather than asking for another revision round:

• Dropped the WordPress.com users callout. On reflection, singling out one commercial host in a vendor-neutral README hosted under the WordPress org isn't the right fit — even though the information itself is accurate. My earlier review praised that line and I've reversed on it, so it felt wrong to ask you to revise again for something I'd already approved.
• Restored the trailing newline at EOF that got lost in the final revision.

Thanks again for the thorough work on this — merging shortly.