Skip to main content
Glama
Browserbase MCP server

Browserbase MCP server

by jannikco

Prepare and clean up a temporary browser session

Browserbase + your AI assistant · powered by PipMCP

You want to prepare and clean up a temporary browser session, using the account your team has actually connected.

Made for: Teams preparing a browser workflow

For real use, you will need PipMCP and access to Browserbase.

Ask your AI to set this up

Paste this into a coding assistant that can open project files and run commands, such as Codex, Claude Code or Grok Build. You do not need to understand the code first.

Help me use this project: https://github.com/jannikco/browserbase-mcp

I'm not a programmer. My goal is: Prepare and clean up a temporary browser session.

Read the project instructions and set it up in a new folder without overwriting my work.
Guide me through PipMCP and its private key setup; never ask me to paste secrets into this
chat. Run a documented sample-data demo if available, then help me get a first small
result from my connected app. Explain the result in plain English. Ask before changing
records, sending messages or publishing anything.

Related MCP server: AI Super MCP

Three useful things to ask for

Show existing browser sessions and inspect the one I choose.
If a new session is needed, show the plan and ask before creating it. Explain that driving
the browser needs separate tooling, and release the session when explicitly requested.
Prepare a browser-session handover showing which session we selected, its current status
and the next control step.

Your path to a real result

flowchart LR
  A["Ask your AI"] --> B["Connect PipMCP"] --> C["Prepare and clean up a<br/>temporary browser…"] --> D["Review together"]
  1. Open PipMCP setup and sign in or create your account.

  2. Connect the app in PipMCP with the permissions you want to grant.

  3. Create the product API key through the official setup, add it privately to your AI project's environment, and ask your AI to try a small read.

What to expect: Connect Browserbase in your PipMCP account, then use your PipMCP key for the supported actions. Review proposed changes before they are sent. This client manages session setup and release. Actually driving the browser requires separate browser-control tooling.

Add your PipMCP key privately in your project settings. Keep keys out of chat and public repositories.

Keep going

Browserbase MCP server

Use Browserbase from Claude Code, Codex, Grok Build and MCP clients through PipMCP. One PipMCP API key connects this package to private execution.

Activate with PipMCP · Integration directory

Build something useful

Inspect existing sessions, approve creation only if needed, then request release of the returned session ID and inspect its final state. Actual browser driving requires a separate CDP client.

The package is an authenticated client: discovery, schemas, policy decisions and execution come from PipMCP. Provider implementation remains on the server.

Quick start

Requires Node.js 22+. Clone this repository, then:

npm ci --ignore-scripts
npm test
npm start
# After configuring your provider in PipMCP and setting PIPMCP_API_KEY:
npm start -- --live
# Launch the stdio MCP bridge:
npm run server

Create a PipMCP API key with explicit connectors:read and connectors:call scopes. Set PIPMCP_API_KEY in the calling process environment. Provider credentials are configured in PipMCP. Multiple accounts require explicit PIPMCP_INTEGRATION_ID and PIPMCP_CONNECTION_ID from discovery. Existing keys do not gain scopes automatically.

Built for coding agents

Install this repository's skill into your project:

node lib/cli.mjs agents install --client codex --scope project --project /path/to/project
# Use claude or grok for those clients.

Connect AI agents to Browserbase using one PipMCP API key and actual hosted tool discovery. Native AGENTS.md, CLAUDE.md and project skills support the current coding session. No additional AI model key is required. capabilities.json describes the package; llms.txt indexes its instructions.

Inspect actual tools before calling

import {PipMCPGatewayClient} from './lib/index.mjs';
const client = new PipMCPGatewayClient(); // PIPMCP_API_KEY
const inventory = await client.getTools("browserbase");
console.log(inventory.data.tools);
// Select a real tool and validate your arguments against its returned schema.
// client.callTool(provider, actualToolName, reviewedArguments, {idempotencyKey});

PipMCP enforces workspace, role, connection, policy/approval and usage controls. Preserve the original idempotency key when retrieving/resuming a receipt. Pending and confirmation_required are not completed provider results; uncertain writes are held for reconciliation. The bridge never auto-approves a hosted action.

Version 1 migration

This release uses the authenticated PipMCP gateway for real discovery/execution. Upgrade your MCP launch command and configure PIPMCP_API_KEY before reconnecting. Historical local runtimes remain available under their original MIT license in Git history.

Evidence and support

Transport, package and agent fixtures are tested. Authentication/provider access must be checked in your own configured workspace; synthetic fixtures do not establish live provider execution. Do not include credentials or customer records in public issues. MIT covers this public client.

Provider setup reference

Official provider documentation. Credentials are entered in PipMCP; this package does not accept or store provider secrets.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Connects AI agents and MCP clients to Azure DevOps through a single PipMCP API key, exposing hosted tool discovery, schema validation, and policy-governed execution so agents can read project and pipeline data and approve selected write actions.
      1,134 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Connects AI agents and MCP clients to Firecrawl through a single PipMCP API key, enabling hosted tool discovery, schema validation, governed execution, and page-to-Markdown retrieval.
      181,410 npm
      MIT