This week’s AI contributor meeting focused on the AI plugin release cycle, MCP client progress, connector-related issues, and contributor onboarding topics. Discussions also covered strategies for improving AI block recognition and processing Elementor feedback into actionable issues.
Announcements
- Testing feedback from @illuminea is available and should be reviewed. Contributors are encouraged to create issues in the relevant repositories based on findings. @justlevine is helping generate issues based on comment discussions in the document. Larger themes such as rate limits and fallback behavior may be addressed asynchronously.
- AI 0.7.0 was released last week. Feedback is encouraged, with emphasis on fixing bugs and improving existing features ahead of upcoming releases.
Abilities
- Commit needed: Abilities API: Catch exceptions thrown by ability callbacks
- Approved PRs related to the abilities work are ready to be merged following final checks.
AI plugin
- 0.8.0 is targeted for release next week.
- At least one additional major release is expected ahead of the eventual WordPress 7.0 release.
- Current focus remains on stabilizing existing features rather than introducing large new functionality.
PHP / WP AI Client
- Commit needed: A single config option to disable all LLM related features
- PR from @westonruter requires testing and review: #77353 — Connectors: preload REST API responses on the Connectors screen
- Issue from @westonruter requires a PR: #77352 — Connectors screen: Users are blocked on sites with a read-only file system (
DISALLOW_FILE_MODS) - Connector plugin developers should review recent API changes and updates: Connector API changes may require metadata adjustments when using
wp_get_connectors(). - @flixos90 and @jason_the_adams pinged on merging updates in the Google provider repository and shipping v1.0.4 to include recent fixes.
MCP
- MCP Client 0.5.0 was scheduled for release immediately following the meeting.
- Contributors discussed converting the MCP client from a Composer package into a WordPress plugin to avoid dependency conflicts.
- @ovidiu-galatan will initiate a public discussion in the core AI channel regarding reversing the original decision to ship as a Composer package.
- @justlevine can assist with technical aspects of submitting the MCP client as a plugin to WordPress.org.
AI Block Recognition Strategies
- Contributors discussed challenges converting HTML into WordPress blocks due to missing backend creation mechanisms. Proposed approach:
- Provide agents with a list of available blocks.
- Use REST API or WP-CLI tools to expose block metadata.
- Prefer source-code-driven context over traditional documentation references.
- @euthelup is preparing to open source a Claude-based block dictionary tool.
Contributor Support Topics
- New contributors were encouraged to focus on areas aligned with their experience: AI client, Agent skills, Abilities, MCP development, AI plugin
- @mikeyarce reported being stuck in a verification loop while submitting the Minimax provider plugin.
- Recommendation: request assistance in the Plugins team Slack channel.
- AI team members offered to help escalate if needed.
- Additional provider plugin work is ongoing, including development of connectors for services such as Kimi or Moonshot AI.
Next Steps
- Generate GitHub issues from Miriam’s feedback documentation.
- Merge approved Abilities and llm-off-switch PRs.
- Release MCP Client 0.5.0.
- Continue testing connector-related changes.
- Advance preparation for AI plugin 0.8.0 release.
Upcoming meetings
Folks are welcome to join on Wednesday’s at 1700 UTC via Google Meet with in-meeting notes captured in a Slack Canvas and then paired with Gemini meeting notes to help generate this meeting summary post. All team meetings are published to https://make.wordpress.org/meetings/#ai.
- The next bi-weekly AI Team Office Hours Slack discussion is scheduled for 16 April 2026.
- The next weekly AI Contributor weekly Google Meet video call is scheduled for 22 April 2026.
Props to @neel33 for pre-publish review.