Scrapybara MCP
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 |
|---|---|
| start_instanceA | Start a Scrapybara Ubuntu instance. Use it as a desktop sandbox to access the web or run code. Always present the stream URL to the user afterwards so they can watch the instance in real time. |
| get_instancesB | Get all running Scrapybara instances. |
| stop_instanceC | Stop a running Scrapybara instance. |
| bashC | Run a bash command in a Scrapybara instance. |
| actB | Take action on a Scrapybara instance through an agent. The agent can control the instance with mouse/keyboard and bash commands. |
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 5 tools
Each tool has a clearly distinct purpose: act controls the instance via agent, bash runs commands, get_instances lists instances, start_instance creates one, and stop_instance terminates one. There is no overlap or ambiguity between these functions.
Four tools follow a consistent verb_noun pattern (get_instances, start_instance, stop_instance, run_command would fit but bash is used instead). The tool 'act' deviates as a single verb, and 'bash' is a noun, but overall the naming is mostly consistent and readable.
With 5 tools, this is well-scoped for managing Scrapybara instances. It covers core lifecycle operations (start, stop, list) and usage actions (act, bash), with each tool earning its place without bloat or thinness.
The toolset provides good coverage for instance management and interaction, including lifecycle (start, stop, list) and control (act, bash). A minor gap is the lack of a tool for configuring or modifying instances, but agents can work around this using bash or act.