pixl.directory
Browserbase logo

Browserbase

Automate browser interactions in the cloud with powerful browser automation and testing capabilities, supporting parallel execution and cross-browser testing.

Installation Instructions →

How to Use Model Context Protocol (MCP) in Cursor

What is MCP?

Model Context Protocol (MCP) is an open protocol that allows you to provide custom tools to agentic LLMs (Large Language Models) in Cursor's Composer feature.

Installation Steps

  1. Open Cursor Settings
    • Navigate to Cursor Settings > Features > MCP
    • Click the "+ Add New MCP Server" button
  2. Configure the Server
    • Name: Give your server a nickname
    • Type: Select the transport type (stdio or sse)
    • Command/URL: Enter either:
      • For SSE servers: The URL of the SSE endpoint
      • For stdio servers: A valid shell command to run the server

Example Configurations

For stdio Server (Browserbase Example):

Command: node ~/mcp-quickstart/browserbase-server/build/index.js --api-key $BROWSERBASE_API_KEY --project-id $BROWSERBASE_PROJECT_ID --region $BROWSERBASE_REGION

For SSE Server:

URL: https://api.browserbase.io/v1/sse

Using MCP Tools

Tool Availability

  • • After adding a server, it will appear in your MCP servers list
  • • You may need to click the refresh button to populate the tool list

Using Tools in Composer

  • • The Composer Agent automatically uses MCP tools when relevant
  • • You can explicitly prompt tool usage by:
    • Referring to the tool by name
    • Describing the tool's function

Tool Execution Process

  • • Displays a message in chat requesting approval
  • • Shows tool call arguments (expandable)
  • • Executes the tool upon user approval
  • • Displays the tool's response in the chat

Important Notes

  • • MCP tools may not work with all models
  • • MCP tools are only available to the Agent in Composer
  • • For Browserbase integration, you need to set up BROWSERBASE_API_KEY, BROWSERBASE_PROJECT_ID, and BROWSERBASE_REGION environment variables
  • • Create an account and get your API key from the Browserbase dashboard
  • • Create a project and note down the project ID
  • • Choose your preferred region for browser instances (e.g., us-east, eu-west)
  • • For security, use a wrapper script that sets the environment variables before running the server
  • • Configure browser preferences (viewport, user agent, etc.) in your automation scripts
  • • Be mindful of concurrent session limits and timeout settings
  • • Implement proper error handling for network issues and browser crashes
  • • Consider implementing session pooling for better resource utilization
  • • Use appropriate waits and retries for dynamic content loading
  • • Monitor browser memory and CPU usage for optimal performance
← Back to Home