How to integrate Browser tool MCP with Pi

Connect Pi to Browser tool MCP. Copy highlighted text from this webpage, drag and drop a file to upload section, and more using natural language, with authentication handled for you.

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

Introduction

Pi is a minimal, self-extensible coding agent that lives in your terminal — one agent loop over Claude, GPT-5, Gemini, Grok, DeepSeek, and 20+ other providers, with maximum extension surface and minimum product opinion. Its core ships four tools (read, write, edit, bash) and self-extends at runtime through skills, extensions, and packages.

This guide explains the easiest and most robust way to connect your Browser tool account to Pi. You can do this through either Composio Connect CLI or Composio Connect MCP. Because Pi already runs shell commands as first-class tools and ships no built-in MCP, the CLI is the recommended path — it's faster to set up, needs no server config, and chains multi-step tasks more reliably. The MCP path is also fully supported through Pi's official pi-mcp-adapter extension.

Also integrate Browser tool with

What is Composio Connect?

Composio Connect is a consumer offering that lets anyone plug 1,000+ applications directly into their agent harness — including Pi. It can:

  • Search and load tools from relevant toolkits on-demand, reducing context usage.
  • Chain multiple tools to accomplish complex workflows via a remote workbench, without excessive back-and-forth with the LLM.
  • Manage app authentication end-to-end with zero manual overhead.

Connect Browser tool to Pi with Composio

Prerequisites: Install Pi

Pi needs Node.js 18+ (Node 22 recommended). Install the agent globally with npm:

bash
npm install -g --ignore-scripts @earendil-works/pi-coding-agent

On Linux or macOS you can use the installer script instead:

bash
curl -fsSL https://pi.dev/install.sh | sh

Then run pi in any project directory and authenticate your model provider — use /login inside Pi for subscription providers (Claude Pro/Max, ChatGPT, GitHub Copilot), or set an API key such as ANTHROPIC_API_KEY before starting. Confirm it's working:

bash
pi --version

Full first-run details are in the Pi Quickstart.

Option 1: Composio CLI (recommended)

Pi runs shell commands as first-class tools, so the Composio Universal CLI is the most natural fit — no MCP server to configure and reliable multi-step tool chaining. Install and authenticate:

bash
# Install the Composio CLI
curl -fsSL https://composio.dev/install | bash

# Log in to Composio
composio login

Connect to Browser tool

Ask Pi to connect to Browser tool, or simply request any Browser tool-related task. Under the hood Pi calls Composio commands like any other shell tool:

bash
composio search "what can I do with Browser tool?"
composio link browser_tool

On the first Browser tool call, composio link browser_tool opens an OAuth prompt so you can authorize access. After that, every Browser tool command works with your stored credentials automatically — just talk to Pi and it will search, execute, and chain Browser tool tools as needed.

Option 2: Composio MCP

Pi's core intentionally ships no built-in MCP, but the official pi-mcp-adapter extension adds full MCP support — exposing every server through a single lightweight proxy tool (~200 tokens) instead of loading hundreds of tool definitions into context.

1. Install the MCP adapter extension

bash
pi install npm:pi-mcp-adapter

Restart Pi after installation.

2. Add the Composio MCP server

Create (or edit) a .mcp.json file in your project root, or ~/.config/mcp/mcp.json for a user-global setup:

bash
{
  "mcpServers": {
    "composio": {
      "url": "https://connect.composio.dev/mcp"
    }
  }
}

The adapter connects lazily by default — the server won't start until Pi actually calls one of its tools, and cached metadata keeps search and describe working without a live connection.

3. Authenticate

Run /mcp-auth inside Pi to open the authentication modal and select composio from the list. Complete the sign-in in your browser, then on the consent screen click Allow access to authorize Composio. Once approved, the server shows as connected inside Pi:

Pi /mcp-auth modal listing the composio MCP server
Composio OAuth consent screen with the Allow access button
Composio MCP server connected inside Pi

4. Done!

Confirm the server is live with /mcp to open the interactive panel, then ask Pi to connect to Browser tool or request any Browser tool-related task — it will prompt you to authorize Browser tool on first use.

What is the Browser tool MCP server, and what's possible with it?

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.

Way Forward

With Browser tool connected, Pi can now act on your behalf whenever you ask it to.

From here, you can extend Pi further:

  • Connect more apps: Calendar, Slack, Notion, Linear, and hundreds of others are available through the same Composio Connect setup. Each new integration compounds what Pi can do for you.
  • Build workflows across tools: Once multiple apps are connected, Pi can chain actions together — turn an email into a calendar invite, a Slack message into a Linear ticket, or a meeting note into a follow-up draft.
  • Lean into Pi's extension surface: Wrap common Browser tool flows as Pi skills or prompt templates so recurring tasks become one-line commands, and use directTools in the MCP adapter to promote your most-used Browser tool tools into Pi's tool list directly.

If you run into trouble or want to share what you've built, join the community or check out the Docs for deeper configuration options.

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.

FAQ

Frequently asked questions

With a standalone Browser tool MCP server, the agents and LLMs can only access a fixed set of Browser tool tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Browser tool and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Pi fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Browser tool tools.

Yes, absolutely. You can configure which Browser tool scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Browser tool data and credentials are handled as safely as possible.

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