Skip to main content
Glama
stemado

scout-mcp-server

by stemado

launch_session

Launch a new browser session with anti-detection. Optionally navigate to an initial URL and configure headless mode, profile, proxy, or download directory.

Instructions

Launch a new browser session via Botasaurus with anti-detection enabled.

The browser stays alive across all subsequent tool calls until close_session is called. Optionally navigate to an initial URL.

Args: url: Initial URL to navigate to after launch. If omitted, opens a blank page. headless: Run browser in headless mode. Default: false (headed, for observation). profile: Optional Chrome profile for session persistence. A bare name (e.g., 'work-portal') creates a Scout-managed profile at /.scout/profiles// that persists cookies, localStorage, and all browser state across sessions. An absolute path (e.g., 'C:\Users...\User Data') uses an existing Chrome profile directory directly. If omitted, a temporary profile is used and deleted on close. proxy: Optional proxy URL (e.g., 'http://user:pass@host:port'). WARNING: Using a proxy triggers botasaurus-driver's proxy authentication subsystem, which imports javascript-fixes — a package that runs 'npm install' at import time without a lockfile. Only use proxy in trusted environments where Node.js is installed. download_dir: Directory for downloaded files. Default: '/.scout/downloads'. Relative paths are resolved from the server's working directory. connection_mode: How to connect to Chrome. 'launch' (default) starts a new browser instance. 'extension' connects to your existing Chrome via the Scout extension, preserving logged-in sessions. allowed_domains: Optional list of domains allowed for fill_secret credential typing and cross-origin navigation (extension mode). Example: ['example.com', 'login.example.com']. If omitted, fill_secret works on any domain (with a warning). allow_localhost_port: Optional port number (1-65535) to allow localhost/loopback navigation on. Example: 3000 permits http://localhost:3000 only. If omitted, localhost is blocked. The SCOUT_ALLOW_LOCALHOST env var overrides this to allow all ports.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNo
headlessNo
profileNo
proxyNo
download_dirNo
connection_modeNolaunch
allowed_domainsNo
allow_localhost_portNo
Behavior5/5

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

Without annotations, description fully discloses persistence, anti-detection, profile lifetimes, proxy npm install caveat, allowed_domains scope, and localhost blocking.

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

Conciseness4/5

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

Structured with sections and bullet points, but verbose; could be slightly trimmed without losing key information.

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?

Comprehensive for a launch tool with 8 parameters and no output schema; covers lifecycle, security, and parameter interactions.

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

Parameters5/5

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

Despite 0% schema coverage, each of the 8 parameters is documented with defaults, valid formats, side effects (e.g., profile persistence, proxy warning), and usage context.

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?

The description clearly states the tool launches a browser session with anti-detection, and the sibling context includes close_session and browse, making its role distinct.

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

Usage Guidelines4/5

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

Explicitly states session persists until close_session, and provides guidance on connection modes and proxy risks. Lacks explicit when-to-avoid scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/stemado/scout-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server