MCP Configuration

Browserman provides native support for the Model Context Protocol (MCP), allowing you to use browser automation capabilities directly from Claude and other AI assistants.

Overview

The Browserman MCP server is hosted at:

https://mcp.browserman.run

This MCP server provides tools for interacting with various social media platforms and browser automation tasks.

Supported MCP Clients

Browserman supports multiple MCP clients:

• Claude Code (Recommended) - Anthropic's official CLI for Claude
• Cursor - AI-first code editor
• Codex - OpenAI's code assistant with MCP support
• Cline - Autonomous AI coding agent for VS Code
• Continue - Open-source AI code assistant
• Windsurf - Codeium's AI flow editor
• Zed - High-performance code editor
• Claude Desktop - Requires mcp-remote wrapper
• And more...

TIP

For the best experience, we recommend Claude Code for its easy CLI-based setup.

Quick Setup

Option 1: Claude Code (Recommended)

Claude Code provides the easiest setup with a single CLI command:

1. Install Claude Code (if not already installed):

   npm install -g @anthropic-ai/claude-code

2. Get your API key from app.browserman.run:

   • Click API Keys in the sidebar
   • Click + New Key
   • Copy your key

3. Add Browserman MCP server:

   claude mcp add --transport http browserman https://mcp.browserman.run --header "X-API-Key: YOUR_API_KEY_HERE"

   Replace YOUR_API_KEY_HERE with your actual API key.

4. Verify installation:

   claude mcp list

That's it! You can now use Browserman tools in Claude Code.

Option 2: Cursor

For Cursor, add the configuration to your MCP config file:

1. Open your Cursor MCP config:

   • Linux/macOS: ~/.cursor/mcp.json
   • Windows: %USERPROFILE%\.cursor\mcp.json

2. Add this configuration:

{
  "mcpServers": {
    "browserman": {
      "url": "https://mcp.browserman.run",
      "headers": {
        "X-API-Key": "YOUR_API_KEY_HERE"
      }
    }
  }
}

3. Replace YOUR_API_KEY_HERE with your actual API key.

4. Restart Cursor.

Option 3: Codex

For OpenAI Codex, use TOML format in your Codex configuration file:

[mcp_servers.browserman]
url = "https://mcp.browserman.run"
http_headers = { "X-API-Key" = "YOUR_API_KEY_HERE" }

Other Clients

For detailed configuration instructions for all supported clients including Cline, Continue, Zed, Windsurf, Claude Desktop, and more:

1. Visit app.browserman.run/mcp
2. Select your MCP client from the dropdown
3. Copy the generated configuration
4. Follow the client-specific instructions

Claude Desktop

Claude Desktop requires the mcp-remote wrapper to connect to HTTP MCP servers. For simpler setup, we recommend using Claude Code instead.

Getting Your API Key

1. Visit app.browserman.run
2. Sign in or create an account
3. Navigate to Settings > API Keys
4. Click Generate New Key
5. Copy the key and store it securely

WARNING

Treat your API key like a password. Never commit it to version control or share it publicly.

Available Tools

Once configured, you'll have access to the following MCP tools:

Account Management

• accounts_list - List all accounts you have access to
• Filter by platform to see specific accounts

Twitter/X

• twitter_createTweet - Post a new tweet
• twitter_likeTweet - Like an existing tweet
• twitter_reTweet - Retweet a tweet
• twitter_replyTweet - Reply to a tweet
• twitter_quoteTweet - Quote tweet with your comment

Xueqiu (雪球)

• xueqiu_post - Post content to Xueqiu platform

Eastmoney (东方财富)

• eastmoney_postWithCode - Post a comment to a stock page

Tonghuashun (同花顺)

• tonghuashun_post - Post text and images to Tonghuashun

Task Management

• tasks_getStatus - Get the status and result of a task by task ID

Utilities

• brdtest_mygeo - Get geolocation information from proxy

Usage Examples

Example 1: Post a Tweet

In Claude Desktop, you can simply say:

"Post a tweet that says 'Hello from Browserman!' using my jingo account"

Claude will use the twitter_createTweet tool with the appropriate parameters.

Example 2: List Accounts

"Show me all my Twitter accounts"

Claude will use the accounts_list tool filtered by platform.

Example 3: Complex Workflow

"Post the same message 'Check out this new feature!' to both my Twitter and Xueqiu accounts"

Claude will coordinate multiple tool calls to accomplish this.

Configuration Options

Custom Headers

You can add custom headers to your MCP configuration:

{
  "mcpServers": {
    "browserman": {
      "url": "https://mcp.browserman.run",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY",
        "X-Custom-Header": "value"
      }
    }
  }
}

Timeout Settings

Most MCP clients allow you to configure timeout settings. For long-running browser automation tasks, you may want to increase the timeout:

{
  "mcpServers": {
    "browserman": {
      "url": "https://mcp.browserman.run",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      },
      "timeout": 300000
    }
  }
}

Execution Modes

Browserman supports two execution modes:

Lite Mode (Default)

• Faster execution
• Lower resource usage
• Suitable for most tasks
• May be detected by some platforms

Full Mode

• Complete browser emulation
• Better for avoiding detection
• Higher resource usage
• Recommended for sensitive operations

You can specify the execution mode in tool parameters:

{
  "preferredEngine": "full"
}

Security Best Practices

1. Rotate API Keys Regularly - Generate new API keys periodically and revoke old ones
2. Use Environment Variables - Store API keys in environment variables, not in config files
3. Limit Permissions - Create separate API keys for different use cases
4. Monitor Usage - Regularly check your task history in the dashboard
5. Enable 2FA - Protect your Browserman account with two-factor authentication

Troubleshooting

See the Troubleshooting Guide for common issues and solutions.

Next Steps

• View MCP Usage Examples
• Explore the API Reference
• Learn about Account Binding