How to integrate Browserbase tool MCP with Kimi Code

How to integrate Browserbase tool MCP with Kimi Code Kimi Code is Moonshot AI's open-source coding agent, powered by Kimi K2.6. It runs in your terminal, reads and edits code, executes shell commands, and plans multi-step tasks, with native MCP support for extending it to outside tools. In this guide, I will explain the easiest and most secure way to connect your Browserbase tool account to Kimi Code via Composio Connect, so it can start a new headless browser session now, download all artifacts from last session, retrieve debug URLs for active sessions, and more without ever putting your account credentials at risk.

Get started for freeGet a demo
Browserbase tool logoBrowserbase tool
Api Key

Browserbase is a serverless platform for running and managing headless browsers at scale. It lets you automate and monitor browser tasks with Playwright, Puppeteer, and Selenium—no infrastructure headaches.

19 Tools

How to integrate Browserbase tool MCP with Kimi Code

Kimi Code is Moonshot AI's open-source coding agent, powered by Kimi K2.6. It runs in your terminal, reads and edits code, executes shell commands, and plans multi-step tasks, with native MCP support for extending it to outside tools.

In this guide, I will explain the easiest and most secure way to connect your Browserbase tool account to Kimi Code via Composio Connect, so it can start a new headless browser session now, download all artifacts from last session, retrieve debug URLs for active sessions, and more without ever putting your account credentials at risk.

Also integrate Browserbase tool with

OpenAI Agents SDKClaude Agent SDKClaude CodeClaude CoworkCodexOpenClawHermesCLIGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAI

Why use Composio?

Composio provides:

  • Access to 1,000+ managed apps from a single MCP endpoint. This makes it convenient for agents to run cross-app workflows.
  • Managed OAuth. You do not have to worry about authentication and authorization flows for every app.
  • Programmatic tool calling. Allows LLMs to write code in a remote workbench to handle complex tool chaining. This reduces back-and-forth for frequent tool calls.
  • Large tool response handling outside the LLM context. This minimizes context bloat from large tool responses.
  • Dynamic just-in-time access to thousands of tools across hundreds of apps. Composio loads the tools your agent needs, so LLMs are not overwhelmed by tools they do not need.

Connect Browserbase tool to Kimi Code

Kimi Code is a TypeScript agent distributed through npm. It acts as an MCP client and reads server definitions from an mcp.json file, and it can also add and authenticate servers conversationally through /mcp-config. Composio is a remote HTTP server that authenticates with OAuth, so no API key is stored anywhere.

1. Install Kimi Code

The quickest way is the official install script, which requires no pre-installed Node.js and places the kimi executable on your PATH.

bash
# macOS or Linux
curl -fsSL https://code.kimi.com/kimi-code/install.sh | bash

# Windows PowerShell
irm https://code.kimi.com/kimi-code/install.ps1 | iex

# Confirm the installation
kimi --version

2. Log in

Start Kimi Code in your project directory, then sign in from the interactive UI:

bash
kimi

Run /login and choose Kimi Code OAuth using the device-code flow, or use a Moonshot API key.

3. Add Composio with /mcp-config

In current versions of Kimi Code, MCP servers are managed inside the app, not with a shell subcommand. From the interactive UI, run:

bash
/mcp-config
Kimi Code MCP config flow for adding the Composio MCP server

Tell it the server name and URL in plain language. For example:

Server name is Composio, and here is the server URL: https://connect.composio.dev/mcp

Kimi Code asks whether to add it globally, at ~/.kimi-code/mcp.json, or project-local for the current checkout, then writes the entry for you:

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

There is no transport field to set. Kimi Code infers HTTP from the url.

4. Restart the session

The new server is picked up on a fresh session, not the current one. Start a new session:

bash
/new

On the new session, Kimi Code detects that the server needs authorization and prompts you to run:

bash
/mcp-config login Composio

5. Authorize with OAuth

Run the command Kimi suggests:

bash
/mcp-config login composio

Kimi Code opens Composio's authorization page or surfaces a URL. Approve access, then return to the session. You should see confirmation that the Composio MCP server is connected.

Composio authorization page for Kimi Code MCP setup

Check the connection status any time with /mcp. Composio should appear as connected with its tools listed.

Kimi Code showing Composio connected after OAuth authorization

Connect your Browserbase tool account

Back in a Kimi Code session, ask the agent to connect to Browserbase tool or give it any Browserbase tool-related task.

For example, ask it to:

  • "Start a new headless browser session now"
  • "Download all artifacts from last session"
  • "Retrieve debug URLs for active sessions"

It will prompt you to authenticate and authorize access to Browserbase tool.

That is it. Composio tools are now available in Kimi Code, and your Browserbase tool account is ready to use.

Conclusion

You have successfully connected Browserbase tool to Kimi Code using Composio Connect. Your agent can now manage Browserbase tool from the terminal with natural language, without exposing credentials in prompts or local scripts.

Since the same Composio endpoint exposes 1,000+ apps, you can add Slack, Calendar, Linear, and more to the same server and chain them into cross-app workflows.

TOOLS

Supported Tools

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

Create a new browser context

Tool to create a new browser context.

Retrieve a browser context

Tool to retrieve details of a specific browser context.

Update Browser Context

Tool to update a specific browser context.

Create Browser Session

Tool to create a new browser session.

Delete a browser context

Tool to delete a browser context and all its stored data (cookies, localStorage, etc.

Delete a browser extension

Tool to delete an uploaded browser extension by its ID.

Delete Session Downloads

Tool to delete all file downloads from a specific browser session.

Retrieve a browser extension

Tool to retrieve details of a specific browser extension.

Retrieve a project

Tool to retrieve details of a specific project including settings and configuration.

Get project usage statistics

Tool to retrieve usage statistics for a project including browser minutes and proxy bytes consumed.

List Projects

Tool to list all projects for the authenticated account.

Retrieve a browser session

Tool to retrieve details of a specific browser session.

Retrieve Session Debug URLs

Tool to retrieve live debug URLs for a specific session.

Download Session Artifacts

Tool to download files from a specific session.

Retrieve Session Logs

Tool to retrieve logs of a specific session.

List Browser Sessions

Tool to list all browser sessions.

Update Browser Session

Tool to update the status of a specific browser session.

Upload Browser Extension

Tool to upload a browser extension for use in sessions.

Upload File to Session

Tool to upload files to a browser session for file input operations.

FRAMEWORKS

How to build Browserbase tool MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Browserbase tool MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Browserbase tool MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Browserbase tool MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Browserbase tool MCP with Claude Cowork

Codex logo

Codex

Use Browserbase tool MCP with Codex

OpenClaw logo

OpenClaw

Use Browserbase tool MCP with OpenClaw

Hermes logo

Hermes

Use Browserbase tool MCP with Hermes

CLI logo

CLI

Use Browserbase tool MCP with CLI

Google ADK logo

Google ADK

Use Browserbase tool MCP with Google ADK

LangChain logo

LangChain

Use Browserbase tool MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Browserbase tool MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Browserbase tool MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Browserbase tool MCP with LlamaIndex

CrewAI logo

CrewAI

Use Browserbase tool MCP with CrewAI

FAQ

Frequently asked questions

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

Yes, you can. Kimi Code 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 Browserbase tool tools.

Yes, absolutely. You can configure which Browserbase 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 Browserbase tool data and credentials are handled as safely as possible.

Start with Browserbase tool.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Browserbase 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