# How to integrate Browserbase tool MCP with Kimi Code

```json
{
  "title": "How to integrate Browserbase tool MCP with Kimi Code",
  "toolkit": "Browserbase tool",
  "toolkit_slug": "browserbase_tool",
  "framework": "Kimi Code",
  "framework_slug": "kimi",
  "url": "https://composio.dev/toolkits/browserbase_tool/framework/kimi",
  "markdown_url": "https://composio.dev/toolkits/browserbase_tool/framework/kimi.md",
  "updated_at": "2026-05-12T10:04:17.094Z"
}
```

## Introduction

### 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 SDK](https://composio.dev/toolkits/browserbase_tool/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/browserbase_tool/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/browserbase_tool/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/browserbase_tool/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/browserbase_tool/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/browserbase_tool/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/browserbase_tool/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/browserbase_tool/framework/cli)
- [Google ADK](https://composio.dev/toolkits/browserbase_tool/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/browserbase_tool/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/browserbase_tool/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/browserbase_tool/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/browserbase_tool/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/browserbase_tool/framework/crew-ai)

## TL;DR

### 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

### 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
```

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

The Browserbase tool MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Browserbase account. It provides structured and secure access to your headless browser environments, so your agent can launch browser sessions, capture artifacts, retrieve debug info, and manage session contexts—all at scale and with zero manual setup.
- Automated browser session management: Instantly create, retrieve, and update browser sessions to run automated browsing tasks in isolated environments.
- Headless testing and monitoring: Let your agent spin up new browser contexts for advanced testing, monitoring, or web scraping workflows—no local infrastructure needed.
- Artifact and log retrieval: Automatically collect session artifacts (like screenshots, HAR files, or logs) after browser tasks complete for audit, debugging, or analytics purposes.
- Real-time session debugging: Fetch live debug URLs so your agent (or you!) can connect and troubleshoot active sessions on demand.
- Comprehensive session tracking: List, filter, and inspect all your browser sessions, including metadata, statuses, and historical activity, to stay on top of your automation fleet.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `BROWSERBASE_TOOL_CONTEXTS_CREATE` | Create a new browser context | Tool to create a new browser context. Use when you need to obtain upload credentials for a custom user-data-directory in a project. |
| `BROWSERBASE_TOOL_CONTEXTS_GET` | Retrieve a browser context | Tool to retrieve details of a specific browser context. Use when you have a context ID and need its metadata. |
| `BROWSERBASE_TOOL_CONTEXTS_UPDATE` | Update Browser Context | Tool to update a specific browser context. Use when you need fresh upload URL and encryption details for an existing context, after obtaining a valid context ID. |
| `BROWSERBASE_TOOL_CREATE_BROWSER_SESSION` | Create Browser Session | Tool to create a new browser session. Use when you need an isolated browser context before performing any page interactions. |
| `BROWSERBASE_TOOL_DELETE_CONTEXT` | Delete a browser context | Tool to delete a browser context and all its stored data (cookies, localStorage, etc.). Use when you need to permanently remove a context. |
| `BROWSERBASE_TOOL_DELETE_EXTENSION` | Delete a browser extension | Tool to delete an uploaded browser extension by its ID. Use when you need to remove an extension from Browserbase. |
| `BROWSERBASE_TOOL_DELETE_SESSION_DOWNLOADS` | Delete Session Downloads | Tool to delete all file downloads from a specific browser session. Use when you need to clean up session artifacts or free storage space. |
| `BROWSERBASE_TOOL_GET_EXTENSION` | Retrieve a browser extension | Tool to retrieve details of a specific browser extension. Use when you have an extension ID and need its metadata (file name, timestamps, project ID). |
| `BROWSERBASE_TOOL_GET_PROJECT` | Retrieve a project | Tool to retrieve details of a specific project including settings and configuration. Use when you have a project ID and need its metadata. |
| `BROWSERBASE_TOOL_GET_PROJECT_USAGE` | Get project usage statistics | Tool to retrieve usage statistics for a project including browser minutes and proxy bytes consumed. Use when you need to monitor or track resource usage for a specific project. |
| `BROWSERBASE_TOOL_LIST_PROJECTS` | List Projects | Tool to list all projects for the authenticated account. Use when you need to retrieve all projects associated with the current API key. |
| `BROWSERBASE_TOOL_SESSIONS_GET` | Retrieve a browser session | Tool to retrieve details of a specific browser session. Use when you have a session ID and need its metadata (status, URLs, timestamps). |
| `BROWSERBASE_TOOL_SESSIONS_GET_DEBUG` | Retrieve Session Debug URLs | Tool to retrieve live debug URLs for a specific session. Use when you need to connect to a running session for debugging. |
| `BROWSERBASE_TOOL_SESSIONS_GET_DOWNLOADS` | Download Session Artifacts | Tool to download files from a specific session. Use after session completion to retrieve all generated artifacts in a ZIP archive. |
| `BROWSERBASE_TOOL_SESSIONS_GET_LOGS` | Retrieve Session Logs | Tool to retrieve logs of a specific session. Use after actions in a session to inspect network events and data exchange. |
| `BROWSERBASE_TOOL_SESSIONS_LIST` | List Browser Sessions | Tool to list all browser sessions. Use when you need to retrieve sessions with optional filtering by status or metadata query. |
| `BROWSERBASE_TOOL_SESSIONS_UPDATE` | Update Browser Session | Tool to update the status of a specific browser session. Use when you need to request session completion before timeout to avoid additional charges. |
| `BROWSERBASE_TOOL_UPLOAD_EXTENSION` | Upload Browser Extension | Tool to upload a browser extension for use in sessions. Supports Chrome extension format (ZIP). Use when you need to add custom browser extensions to your Browserbase project. |
| `BROWSERBASE_TOOL_UPLOAD_SESSION_FILE` | Upload File to Session | Tool to upload files to a browser session for file input operations. Use when you need to make files available for file input fields or downloads within a browser automation session. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

Once connected, Kimi Code can access the Browserbase tool MCP server via Composio to run the app actions you authorize directly from your terminal coding workflow.

## Complete Code

None listed.

## Conclusion

### 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.

## How to build Browserbase tool MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/browserbase_tool/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/browserbase_tool/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/browserbase_tool/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/browserbase_tool/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/browserbase_tool/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/browserbase_tool/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/browserbase_tool/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/browserbase_tool/framework/cli)
- [Google ADK](https://composio.dev/toolkits/browserbase_tool/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/browserbase_tool/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/browserbase_tool/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/browserbase_tool/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/browserbase_tool/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/browserbase_tool/framework/crew-ai)

## Related Toolkits

- [Supabase](https://composio.dev/toolkits/supabase) - Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure.
- [Codeinterpreter](https://composio.dev/toolkits/codeinterpreter) - Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms.
- [GitHub](https://composio.dev/toolkits/github) - GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place.
- [Ably](https://composio.dev/toolkits/ably) - Ably is a real-time messaging platform for live chat and data sync in modern apps. It offers global scale and rock-solid reliability for seamless, instant experiences.
- [Abuselpdb](https://composio.dev/toolkits/abuselpdb) - Abuselpdb is a central database for reporting and checking IPs linked to malicious online activity. Use it to quickly identify and report suspicious or abusive IP addresses.
- [Alchemy](https://composio.dev/toolkits/alchemy) - Alchemy is a blockchain development platform offering APIs and tools for Ethereum apps. It simplifies building and scaling Web3 projects with robust infrastructure.
- [Algolia](https://composio.dev/toolkits/algolia) - Algolia is a hosted search API that powers lightning-fast, relevant search experiences for web and mobile apps. It helps developers deliver instant, typo-tolerant, and scalable search without complex infrastructure.
- [Anchor browser](https://composio.dev/toolkits/anchor_browser) - Anchor browser is a developer platform for AI-powered web automation. It transforms complex browser actions into easy API endpoints for streamlined web interaction.
- [Apiflash](https://composio.dev/toolkits/apiflash) - Apiflash is a website screenshot API for programmatically capturing web pages. It delivers high-quality screenshots on demand for automation, monitoring, or reporting.
- [Apiverve](https://composio.dev/toolkits/apiverve) - Apiverve delivers a suite of powerful APIs that simplify integration for developers. It's designed for reliability and scalability so you can build faster, smarter applications without the integration headache.
- [Appcircle](https://composio.dev/toolkits/appcircle) - Appcircle is an enterprise-grade mobile CI/CD platform for building, testing, and publishing mobile apps. It streamlines mobile DevOps so teams ship faster and with more confidence.
- [Appdrag](https://composio.dev/toolkits/appdrag) - Appdrag is a cloud platform for building websites, APIs, and databases with drag-and-drop tools and code editing. It accelerates development and iteration by combining hosting, database management, and low-code features in one place.
- [Appveyor](https://composio.dev/toolkits/appveyor) - AppVeyor is a cloud-based continuous integration service for building, testing, and deploying applications. It helps developers automate and streamline their software delivery pipelines.
- [Backendless](https://composio.dev/toolkits/backendless) - Backendless is a backend-as-a-service platform for mobile and web apps, offering database, file storage, user authentication, and APIs. It helps developers ship scalable applications faster without managing server infrastructure.
- [Baserow](https://composio.dev/toolkits/baserow) - Baserow is an open-source no-code database platform for building collaborative data apps. It makes it easy for teams to organize data and automate workflows without writing code.
- [Bench](https://composio.dev/toolkits/bench) - Bench is a benchmarking tool for automated performance measurement and analysis. It helps you quickly evaluate, compare, and track your systems or workflows.
- [Better stack](https://composio.dev/toolkits/better_stack) - Better Stack is a monitoring, logging, and incident management solution for apps and services. It helps teams ensure application reliability and performance with real-time insights.
- [Bitbucket](https://composio.dev/toolkits/bitbucket) - Bitbucket is a Git-based code hosting and collaboration platform for teams. It enables secure repository management and streamlined code reviews.
- [Blazemeter](https://composio.dev/toolkits/blazemeter) - Blazemeter is a continuous testing platform for web and mobile app performance. It empowers teams to automate and analyze large-scale tests with ease.
- [Blocknative](https://composio.dev/toolkits/blocknative) - Blocknative delivers real-time mempool monitoring and transaction management for public blockchains. Instantly track pending transactions and optimize blockchain interactions with live data.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Browserbase tool MCP?

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.

### Can I use Tool Router MCP with Kimi Code?

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.

### Can I manage the permissions and scopes for Browserbase tool while using Tool Router?

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.

### How safe is my data with Composio Tool Router?

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.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)
