"FCC" matching MCP servers:

Enables browser control through your existing signed-in Chrome profile, letting MCP clients like Claude Code manage tabs, navigate, inspect pages, and perform real user interactions via tool calls. Works with any model backend without needing Playwright or a fresh browser profile.

Enables an external AI agent to delegate tasks to a local Claude Code installation and receive structured reports, with code modifications governed by a plan-approval-execution workflow and direct file and git operations available outside that loop.

Enables Claude Code to dispatch opencode CLI tasks as background processes with immediate task handle return, status polling, and result retrieval, avoiding tmux and log parsing issues.

WCC is an MCP server that compiles websites into typed capabilities for agents. It enables low-risk search, filter, and navigation actions with verified execution and reduced token usage on repeated tasks.

Lets AI agents check remaining MiniMax Token Plan quota and automatically pause themselves before hitting rate limits.

An MCP server that bridges Claude Desktop and Claude Code by letting Desktop read and interact with Claude Code Remote Control sessions, enabling cross-agent coordination.

Enables Codex to manage a local Claude Code companion through MCP, implementing a dual-agent workflow where Codex handles reasoning and review while Claude Code performs engineering tasks.

Enables Codex to delegate already-scoped coding tasks to Claude Code and manage the resulting execution and fresh read-only review sessions, returning deterministic PASS/FAIL results through a local MCP interface.

MCP server to control Chrome browsers locally or remotely via the Claude extension, enabling navigation, form filling, screenshots, and JavaScript execution from any MCP client.

Enables Claude Code and OpenAI Codex to exchange messages directly within their sessions, including optional cross-review of plans, without copying between terminals.

Routes Claude Code tasks to different AI roles with separate APIs, keys, and models while preserving existing MCP, skills, and project settings.