How to integrate Browser tool MCP with Grok Build

Connect Grok Build to Browser tool MCP. Copy highlighted text from this webpage, drag and drop a file to upload section, and more from your terminal, with authentication handled for you.

Get started for freeGet a demo
Browser tool logoBrowser tool
No Auth

Browser tool is a virtual browser integration that lets AI agents interact with the web programmatically. It enables automated browsing, scraping, and action-taking from any AI workflow.

5 Tools

How to integrate Browser tool MCP with Grok Build

Grok Build is xAI's terminal coding agent. It runs on Grok 4.5, plans its work before it acts, and can run multiple sub-agents in parallel. It also reads Claude Code's MCP configuration, so any server you already have in a .mcp.json is picked up with no changes.

In this guide, I will show you how to connect your Browser tool account to Grok Build through Composio, so it can copy highlighted text from this webpage, drag and drop a file to upload section, fetch and summarize main page content, and more without leaving the terminal. Composio holds the OAuth tokens for you, and Grok Build only calls the tools you approve.

Also integrate Browser tool with

ChatGPT WorkAntigravityOpenAI Agents SDKClaude Agent SDKClaude CodeClaude CoworkCodexOpenCodeCursorVS CodeOpenClawHermesCLIGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAI

Why use Composio over a standalone MCP server?

  • Read and write access. Composio's Browser tool integration lets Grok Build take real actions like creating drafts, sending updates, and labeling records, not just reading data.
  • 1,000+ SaaS toolkits out of the box. One endpoint gives you a full catalog of pre-built connectors, from Gmail and Slack to Notion, Linear, and Salesforce.
  • One MCP server for every app. Wire up a single Composio server instead of maintaining a separate MCP entry for each app.
  • Smart, context-aware tool loading. Grok Build caps how many tools it holds in a single request. Composio loads only the tools a task needs, so you do not spend that budget on tools you are not using.
  • Cross-app automation. Chain actions across apps in one run. Pull a thread, summarize it in Notion, and post the highlights to Slack from a single prompt.

Prerequisites

  • Grok Build installed and signed in. Install with curl -fsSL https://x.ai/cli/install.sh | bash on macOS or Linux, or irm https://x.ai/cli/install.ps1 | iex on Windows PowerShell. On first launch Grok opens a browser to authenticate; for headless or CI use, set an XAI_API_KEY environment variable instead (create the key at console.x.ai).
  • Access to the Browser tool account you want to connect.
  • The Composio MCP endpoint. Composio's server is remote and hosted, so there is nothing to run locally and no tunnel to set up.

Step-by-step: Connect Browser tool to Grok Build

1. Install and verify Grok Build

Install the CLI, then restart your shell so the grok binary lands on your PATH:

bash
curl -fsSL https://x.ai/cli/install.sh | bash
which grok

On Windows, install with PowerShell instead: irm https://x.ai/cli/install.ps1 | iex. If which grok returns a path, you are set. Grok Build runs on Grok 4.5 by default; you can switch models inside the session with /model <name>.

2. Add the Composio server

Add Composio as a remote HTTP MCP server with the grok mcp add command:

bash
grok mcp add --transport http composio https://connect.composio.dev/mcp

You can also add and manage servers from inside a session. Run /mcps to open the extensions modal on the MCP tab, then add a new server and paste the Composio URL. Added this way, Grok auto-detects the name from the URL and lists the server as connect:

bash
https://connect.composio.dev/mcp
Grok Build /mcps extensions modal listing MCP servers Grok Build adding the Composio MCP server with its URL

Grok also reads Claude Code-style config, so an entry in ~/.grok/config.toml or a project .mcp.json works the same way.

3. Authenticate

Composio uses OAuth. In the /mcps modal, select the Composio server and press i to authenticate (Grok also triggers this browser flow automatically the first time it uses a Composio tool). Click Allow to authorize access. Grok stores the tokens under ~/.grok/mcp_credentials.json, and /mcps shows Composio as connected.

Grok Build prompting to authenticate the Composio MCP server Composio authorization screen with the Allow button for Grok Build

4. Start building

Ask Grok to work with your Browser tool account through Composio. On the first Browser tool action, Composio prompts you to connect the account through OAuth. Approve the scopes once, and Composio handles token refresh from there.

What you can do after connecting Browser tool

  • Copy highlighted text from this webpage
  • Drag and drop a file to upload section
  • Fetch and summarize main page content
  • Click login button at top right corner

Security + privacy notes (important)

  • Use least-privilege access. Grant only the Browser tool scopes you actually need.
  • Review OAuth scopes before approving. Check that the requested scopes match what you expect Composio and Grok Build to do.
  • Keep write actions human-reviewed. Grok Build proposes a plan before it acts. Leave that approval step on for actions like sending messages or editing records.
  • Keep secrets out of version control. Your XAI_API_KEY and any tokens should never be committed. Use environment variables or a secrets manager.
TOOLS

Supported Tools

Every Browser tool action and event your agent gets out of the box.

Run Browser Task

Run an AI-powered browser automation task.

Download Task File

Get a download URL for a file generated by a task.

Get Session Live URL

Get the live URL to watch a browser session in real-time.

Stop Browser Task

Kill a browser task and its session.

Watch Browser Task

Poll a browser task to check progress and get results.

FRAMEWORKS

How to build Browser tool MCP Agent with another framework

ChatGPT Work logo

ChatGPT Work

Use Browser tool MCP with ChatGPT Work

Antigravity logo

Antigravity

Use Browser tool MCP with Antigravity

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Browser tool MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Browser tool MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Browser tool MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Browser tool MCP with Claude Cowork

Codex logo

Codex

Use Browser tool MCP with Codex

Cursor logo

Cursor

Use Browser tool MCP with Cursor

VS Code logo

VS Code

Use Browser tool MCP with VS Code

OpenCode logo

OpenCode

Use Browser tool MCP with OpenCode

OpenClaw logo

OpenClaw

Use Browser tool MCP with OpenClaw

Hermes logo

Hermes

Use Browser tool MCP with Hermes

CLI logo

CLI

Use Browser tool MCP with CLI

Google ADK logo

Google ADK

Use Browser tool MCP with Google ADK

LangChain logo

LangChain

Use Browser tool MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Browser tool MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Browser tool MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Browser tool MCP with LlamaIndex

CrewAI logo

CrewAI

Use Browser tool MCP with CrewAI

FAQ

Frequently asked questions

A standalone Browser tool MCP server gives Grok Build a fixed set of Browser tool tools tied to that one server. The Composio Tool Router lets Grok Build load tools from Browser tool and many other apps on demand, based on the task, all through a single endpoint.

Yes. Grok Build ships with native MCP support. Add a server with the grok mcp add command, from the in-session /mcps modal, or by editing ~/.grok/config.toml. It also reads Claude Code-style .mcp.json files, so Grok Build discovers the tools automatically.

Yes. Grok Build has zero-migration compatibility with Claude Code's configuration, so the same Composio server entry works in both without edits.

Tokens, keys, and configuration are encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant, so your Browser tool data and credentials are handled to that standard.

Start with Browser tool.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Browser tool tool your agent needs.Free to start.

Start building
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati
Harsha Gaddipati
Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya
Abhi Arya
Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave
Nirman Dave
CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu
Ryan Yu
Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola
Tomisin Jenrola
Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche
Jerome Leclanche
Co-Founder, Ingram Technologies