Browserless MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| initialize_browserlessC | Initialize connection to Browserless instance |
| generate_pdfC | Generate PDF from URL or HTML content |
| take_screenshotC | Take screenshot of a webpage |
| get_contentC | Extract rendered HTML content from a webpage |
| execute_functionC | Execute custom JavaScript function in browser context |
| download_filesD | Handle file downloads |
| export_pageC | Export webpage with resources |
| run_performance_auditC | Run Lighthouse performance audit |
| unblockC | Bypass bot detection and anti-scraping measures |
| execute_browserqlC | Execute BrowserQL GraphQL queries |
| create_websocket_connectionC | Create WebSocket connection for Puppeteer/Playwright |
| get_healthB | Get health status of Browserless instance |
| get_sessionsC | Get active sessions |
| get_configD | Get configuration |
| get_metricsD | Get metrics |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Most tools have distinct purposes targeting different browser automation tasks like PDF generation, screenshots, content extraction, and performance audits. However, 'execute_browserql' and 'execute_function' both involve executing code in the browser context and could potentially be confused for similar use cases, though their descriptions differentiate GraphQL queries from custom JavaScript.
The naming follows a consistent verb_noun pattern throughout, such as 'create_websocket_connection', 'generate_pdf', and 'take_screenshot'. There are minor deviations like 'unblock' (a single verb without a noun) and 'get_config' (which could be more descriptive), but overall the pattern is clear and readable.
With 15 tools, this is well-scoped for a browser automation server, covering essential operations like connection management, content extraction, file handling, and performance analysis. Each tool appears to serve a specific purpose without obvious redundancy, making the count appropriate for the domain.
The tool set provides comprehensive coverage for browser automation, including initialization, session management, content retrieval (HTML, PDF, screenshots), performance auditing, anti-scraping bypass, and configuration/health checks. There are no apparent gaps; agents can handle full workflows from setup to data extraction and cleanup.