BrowserCat MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BROWSERCAT_API_KEY | Yes | Your BrowserCat API key (required). You can get one for free at https://browsercat.xyz/mcp. |
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 |
|---|---|
| browsercat_navigateB | Navigate to a URL |
| browsercat_screenshotB | Take a screenshot of the current page or a specific element |
| browsercat_clickB | Click an element on the page |
| browsercat_fillC | Fill out an input field |
| browsercat_selectB | Select an option from a dropdown menu |
| browsercat_hoverC | Hover over an element on the page |
| browsercat_evaluateC | Execute JavaScript in the browser console |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Browser console logs |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose targeting specific browser interactions: clicking, evaluating JavaScript, filling inputs, hovering, navigating, taking screenshots, and selecting dropdown options. There is no overlap in functionality, making tool selection straightforward for an agent.
All tools follow a consistent 'browsercat_verb' pattern with clear, descriptive verbs (click, evaluate, fill, hover, navigate, screenshot, select). This uniformity enhances predictability and readability across the toolset.
With 7 tools, this server is well-scoped for browser automation, covering essential interactions without bloat. Each tool earns its place by addressing a common web automation task, making the count appropriate for the domain.
The toolset provides strong coverage for core browser automation tasks like navigation, interaction, and inspection. Minor gaps exist, such as lacking tools for scrolling, handling alerts, or managing cookies, but agents can work around these with existing tools like evaluate for JavaScript.