How to integrate Browser tool MCP with Codex

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Browser tool MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or app, whichever you prefer.

Composio removes the Authentication handling completely from you. We handle the entire integration lifecycle, and all you need to do is just copy the URL below, authenticate inside Codex, and start using it.

Why use Composio?

Apart from a managed and hosted MCP server, you will get:

• CodeAct: A dedicated workbench that allows GPT to write its code to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
• Large tool responses: Handle them to minimise context rot.
• Dynamic just-in-time access to 20,000 tools across 870+ other Apps for cross-app workflows. It loads the tools you need, so GPTs aren't overwhelmed by tools you don't need.

How to install Browser tool MCP in Codex

Codex CLI

Run the command in your terminal.

This will auto-redirect you to the Rube authentication page.

Once you're authenticated, you will be able to access the tools.

Verify the installation by running:

codex mcp list

If you otherwise prefer to use config.toml, add the following URL to it. You can get the bearer token from rube.app → Use Rube → MCP URL → Generate token

[projects."/home/user/composio"]
trust_level = "untrusted"

[mcp_servers.rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"

Codex in VS Code

If you have installed Codex in VS Code.

Then: ⚙️ → MCP Settings → + Add servers → Streamable HTTP:

Add the Rube MCP URL: https://rube.app/mcp and the bearer token.

To verify, click on the Open config.toml

Make sure it's there:

[mcp_servers.composio_rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"

Codex App

Codex App follows the same approach as VS Code.

1. Click ⚙️ on the bottom left → MCP Servers → + Add servers → Streamable HTTP:

2. Restart and verify if it's there in .codex/config.toml

[mcp_servers.composio_rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"

3. Save, restart the extension, and start working.

The Browser tool MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to browser automation tools. It provides structured and secure access to browser actions, so your agent can fetch web content, perform clicks, automate keyboard shortcuts, move the mouse, and interact with on-page elements just like a real user.

• Fetch and analyze webpage content: Let your agent retrieve the full HTML or clean text of any web page for data extraction, analysis, or decision-making.
• Automated mouse and keyboard interactions: Instruct your agent to perform precise clicks, double clicks, drags, and keyboard shortcuts to navigate, select, or manipulate content on the page.
• Clipboard and text extraction: Have the agent copy highlighted text, read clipboard contents, or transfer data between the browser and other tools for seamless workflows.
• Drag-and-drop automation: Enable your agent to handle complex drag-and-drop actions, such as moving files or rearranging lists, to mimic advanced user interactions.
• Fine-grained UI element control: Direct your agent to move the mouse, press and hold, or release buttons at exact coordinates to interact with dynamic or custom web interfaces.

Conclusion

You've successfully integrated Browser tool with Codex using Composio's Rube MCP server. Now you can interact with Browser tool directly from your terminal, VS Code, or the Codex App using natural language commands.

Key benefits of this setup:

• Seamless integration across CLI, VS Code, and standalone app
• Natural language commands for Browser tool operations
• Managed authentication through Composio's Rube
• Access to 20,000+ tools across 870+ apps for cross-app workflows
• CodeAct workbench for complex tool chaining

Next steps:

• Try asking Codex to perform various Browser tool operations
• Explore cross-app workflows by connecting more toolkits
• Build automation scripts that leverage Codex's AI capabilities