Skip to main content
Glama
iola1999

Codex Control Chrome MCP

by iola1999

Codex Control Chrome MCP

Expose the Codex Chrome extension flow to other Agent tools through MCP.

Current implementation is an early Node.js prototype with:

  • official @modelcontextprotocol/sdk stdio server

  • Chrome Native Messaging host mode

  • MCP stdio server mode

  • install/uninstall commands with manifest backup

  • JSON-RPC bridge socket under /tmp/codex-browser-use

  • basic Chrome tab/CDP MCP tools

Install the Chrome native host:

npx -y codex-control-chrome-mcp@latest install-native-host

The user must also have the Codex Chrome Extension installed and enabled in the Chrome profile they want to automate.

Uninstall and restore the previous Codex native host manifest:

npx -y codex-control-chrome-mcp@latest uninstall-native-host

Intended Agent config:

{
  "type": "stdio",
  "command": "npx",
  "args": ["-y", "codex-control-chrome-mcp@latest", "--stdio"]
}

If your Agent supports skills, install or reference the bundled skill folder:

skills/codex-control-chrome-mcp

The skill documents the recommended MCP tool order for status checks, tab claiming, CDP commands, screenshots, events, and tab finalization.

Read:

Install Server
F
license - not found
B
quality
A
maintenance

Maintenance

Maintainers
Response time
0dRelease cycle
3Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/iola1999/codex-control-chrome-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server