Feature 031 β Add Google Gemini CLI as a supported MCP client
The server-edit Clients tab (admin.php?page=acrossai_mcp_manager&action=edit&server={id}&tab=clients) now surfaces a Gemini card (π pill) alongside the existing 7. Uses the same npx @automattic/mcp-wordpress-remote@latest bridge + WP Application Password Basic auth as Claude Desktop / Cursor / other stdio-based clients; config paste target is ~/.gemini/settings.json under the standard mcpServers key.
GeminiClient is a near-verbatim mirror of ClaudeDesktopClient (slug gemini, name Gemini CLI, byte-for-byte identical get_config_snippet shape) β no new auth mechanism, no new abstraction, no new render path.
What shipped
- New:
includes/MCPClients/GeminiClient.php(~55 lines) - Registered:
MCPClientsBlock::$default_classes+CLIENT_META['gemini'](π emoji, config file path, top-level key, instructions) - Tests: 2 new golden fixtures (byte-for-byte copies of claude-desktop fixtures), Gemini row added to
ConcreteClientsTestdata provider,AbstractMCPClientTestcanary bumped 7 β 8 - Docs:
docs/planings-tasks/031-add-gemini-mcp-client.mdplanning artifact + README.txt changelog
Test suite delta
mcpclients PHPUnit suite: 74 tests / 124 assertions (was 67/111 pre-F031 β the Gemini row added 7 tests Γ ~1 assertion each).
Assets β WordPress.org banner refresh
Refreshed the two .wordpress-org/ banner PNGs with updated artwork (banner-1544x500.png + banner-772x250.png). Visual update only β no code change.
Internal
ACROSSAI_MCP_MANAGER_VERSIONconstant bumped to0.1.5matching the plugin header- Plugin
Version:header +Stable tag:in README.txt bumped to0.1.5
PRs merged in this release
- #41 β
feat(mcp-clients): F031 β Add Google Gemini CLI as an MCP client(feature + tests + planning doc) - #42 β
chore(release): 0.1.5 β F031 Add Google Gemini CLI + banner refresh(version bump +.wordpress-org/banner refresh)
Full Changelog: v0.1.4…v0.1.5