Skip to main content
Glama
Xxx00xxX33

Browserbase MCP Server

by Xxx00xxX33

browserbase_session_create

Create a single cloud browser session for web automation tasks like data extraction, form filling, and page interaction using Browserbase with Stagehand initialization.

Instructions

Create or reuse a single cloud browser session using Browserbase with fully initialized Stagehand. WARNING: This tool is for SINGLE browser workflows only. If you need multiple browser sessions running simultaneously (parallel scraping, A/B testing, multiple accounts), use 'multi_browserbase_stagehand_session_create' instead. This creates one browser session with all configuration flags (proxies, stealth, viewport, cookies, etc.) and initializes Stagehand to work with that session. Updates the active session.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdNoOptional session ID to use/reuse. If not provided or invalid, a new session is created.

Implementation Reference

  • The main handler function `handleCreateSession` that executes the tool's logic: creates or reuses a Browserbase session using SessionManager, connects Stagehand, updates context, and returns session view/debug URLs.
    async function handleCreateSession(
      context: Context,
      params: CreateSessionInput,
    ): Promise<ToolResult> {
      const action = async (): Promise<ToolActionResult> => {
        try {
          const config = context.config; // Get config from context
          let targetSessionId: string;
    
          if (params.sessionId) {
            const projectId = config.browserbaseProjectId || "";
            targetSessionId = `${params.sessionId}_${projectId}`;
            process.stderr.write(
              `[tool.createSession] Attempting to create/assign session with specified ID: ${targetSessionId}`,
            );
          } else {
            targetSessionId = defaultSessionId;
          }
    
          let session: BrowserSession;
          if (targetSessionId === defaultSessionId) {
            session = await ensureDefaultSessionInternal(config);
          } else {
            // When user provides a sessionId, we want to resume that Browserbase session
            session = await createNewBrowserSession(
              targetSessionId,
              config,
              params.sessionId,
            );
          }
    
          if (
            !session ||
            !session.browser ||
            !session.page ||
            !session.sessionId ||
            !session.stagehand
          ) {
            throw new Error(
              `SessionManager failed to return a valid session object with actualSessionId for ID: ${targetSessionId}`,
            );
          }
    
          context.currentSessionId = targetSessionId;
          const bb = new Browserbase({
            apiKey: config.browserbaseApiKey,
          });
          const debugUrl = (await bb.sessions.debug(session.sessionId))
            .debuggerFullscreenUrl;
          process.stderr.write(
            `[tool.connected] Successfully connected to Browserbase session. Internal ID: ${targetSessionId}, Actual ID: ${session.sessionId}`,
          );
    
          process.stderr.write(
            `[SessionManager] Browserbase Live Session View URL: https://www.browserbase.com/sessions/${session.sessionId}`,
          );
    
          process.stderr.write(
            `[SessionManager] Browserbase Live Debugger URL: ${debugUrl}`,
          );
    
          return {
            content: [
              {
                type: "text",
                text: `Browserbase Live Session View URL: https://www.browserbase.com/sessions/${session.sessionId}\nBrowserbase Live Debugger URL: ${debugUrl}`,
              },
            ],
          };
        } catch (error: unknown) {
          const errorMessage =
            error instanceof Error ? error.message : String(error);
          process.stderr.write(
            `[tool.createSession] Action failed: ${errorMessage}`,
          );
          // Re-throw to be caught by Context.run's error handling for actions
          throw new Error(`Failed to create Browserbase session: ${errorMessage}`);
        }
      };
    
      // Return the ToolResult structure expected by Context.run
      return {
        action: action,
        waitForNetwork: false,
      };
    }
  • Zod input schema (CreateSessionInputSchema) and tool schema definition (createSessionSchema) including name, description, and inputSchema for the browserbase_session_create tool.
    const CreateSessionInputSchema = z.object({
      // Keep sessionId optional, but clarify its role
      sessionId: z
        .string()
        .optional()
        .describe(
          "Optional session ID to use/reuse. If not provided or invalid, a new session is created.",
        ),
    });
    type CreateSessionInput = z.infer<typeof CreateSessionInputSchema>;
    
    const createSessionSchema: ToolSchema<typeof CreateSessionInputSchema> = {
      name: "browserbase_session_create",
      description:
        "Create or reuse a single cloud browser session using Browserbase with fully initialized Stagehand. WARNING: This tool is for SINGLE browser workflows only. If you need multiple browser sessions running simultaneously (parallel scraping, A/B testing, multiple accounts), use 'multi_browserbase_stagehand_session_create' instead. This creates one browser session with all configuration flags (proxies, stealth, viewport, cookies, etc.) and initializes Stagehand to work with that session. Updates the active session.",
      inputSchema: CreateSessionInputSchema,
    };
  • Tool object definition `createSessionTool` that registers the schema and handler for browserbase_session_create, exported as part of sessionTools array.
    const createSessionTool: Tool<typeof CreateSessionInputSchema> = {
      capability: "core", // Add capability
      schema: createSessionSchema,
      handle: handleCreateSession,
    };
  • Main TOOLS export array in tools index that includes `...sessionTools` (containing browserbase_session_create), used for MCP server tool registration.
    export const TOOLS = [
      ...multiSessionTools,
      ...sessionTools,
      navigateTool,
      actTool,
      extractTool,
      observeTool,
      screenshotTool,
    ];
  • TypeScript type definition for CreateSessionParams used in session creation, related to browserbase_session_create parameters.
    export type CreateSessionParams = {
      apiKey?: string;
      projectId?: string;
      modelName?: string;
      modelApiKey?: string;
      browserbaseSessionID?: string;
      browserbaseSessionCreateParams?: any;
      meta?: Record<string, any>;
    };

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations, but description details session initialization with config flags and active session update. Lacks disclosure of side effects or permissions, but adequate given tool simplicity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three concise sentences, front-loaded with purpose and warning, no extraneous content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Simple tool with single param and no output schema; description covers creation/reuse, initialization, and usage scope fully.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only parameter sessionId is described in schema; description adds optional reuse and fallback creation behavior, improving clarity beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clear verb 'create or reuse' and resource 'single cloud browser session'. Distinct from sibling 'multi_browserbase_stagehand_session_create'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit warning about single vs multi-browser workflows and directs to sibling tool for parallel sessions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.