Scrapybara MCP
Un servidor de Protocolo de Contexto de Modelo para Scrapybara . Este servidor permite que clientes MCP como Claude Desktop , Cursor y Windsurf interactúen con escritorios virtuales de Ubuntu y realicen acciones como navegar por la web, ejecutar código, etc.
Prerrequisitos
Node.js 18+
pnpm
Clave API de Scrapybara (obtenga una en scrapybara.com )
Related MCP server: taw-computer
Instalación
Clonar el repositorio:
git clone https://github.com/scrapybara/scrapybara-mcp.git
cd scrapybara-mcpInstalar dependencias:
pnpm installConstruir el proyecto:
pnpm buildAgregue lo siguiente a la configuración de su cliente MCP:
{
"mcpServers": {
"scrapybara-mcp": {
"command": "node",
"args": ["path/to/scrapybara-mcp/dist/index.js"],
"env": {
"SCRAPYBARA_API_KEY": "<YOUR_SCRAPYBARA_API_KEY>",
"ACT_MODEL": "<YOUR_ACT_MODEL>", // "anthropic" or "openai"
"AUTH_STATE_ID": "<YOUR_AUTH_STATE_ID>" // Optional, for authenticating the browser
}
}
}
}¡Reinicie su cliente MCP y listo!
Herramientas
start_instance : Inicia una instancia de Scrapybara en Ubuntu. Úsala como entorno de escritorio para acceder a la web o ejecutar código. Muestra siempre la URL de la transmisión al usuario posteriormente para que pueda ver la instancia en tiempo real.
get_instances : obtiene todas las instancias de Scrapybara en ejecución.
stop_instance - Detiene una instancia de Scrapybara en ejecución.
bash : ejecuta un comando bash en una instancia de Scrapybara.
Actuar : Realizar acciones en una instancia de Scrapybara mediante un agente. El agente puede controlar la instancia con el ratón, el teclado y comandos bash.
Contribuyendo
Scrapybara MCP es un proyecto impulsado por la comunidad. Ya sea que envíes una idea, corrijas un error tipográfico, añadas una nueva herramienta o mejores una existente, ¡tus contribuciones son muy apreciadas!
Antes de contribuir, revisa los problemas y las solicitudes de incorporación de cambios para ver si alguien más está trabajando en algo similar. Así evitarás duplicar esfuerzos.
Si hay más herramientas o funciones que le gustaría ver, no dude en sugerirlas en la página de problemas .
Available Tools
5 toolsactB
Take action on a Scrapybara instance through an agent. The agent can control the instance with mouse/keyboard and bash commands.
Inputs: instance_id (required), prompt (required), schema.
bashC
Run a bash command in a Scrapybara instance.
Inputs: instance_id (required), command (required).
get_instancesB
Get all running Scrapybara instances.
Inputs: no named parameters.
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.
Inputs: no named parameters.
stop_instanceC
Stop a running Scrapybara instance.
Inputs: instance_id (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to control Unreal E…
A Model Context Protocol server for Wix AI tools
The Telnyx MCP server is an official implementation of the Model Context Protocol that enables AI clients (like Claude Desktop, Cursor, and OpenAI Agents) to interact with Telnyx's telephony, messaging, and AI assistant APIs. It provides comprehensive capabilities including making and managing phone calls, sending SMS/MMS messages, purchasing and configuring phone numbers, creating AI assistants with custom instructions, managing cloud storage buckets, scraping and embedding website content, and handling integration secrets. The server exists as both a local implementation and a remotely hosted version, allowing developers to integrate real-world communication infrastructure directly into AI applications.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA desktop automation MCP server that enables AI agents to interact with Linux environments through screenshots, window inspection, and input simulation. It provides tools for mouse control, keyboard input, and screen capture using xdotool and XDG Desktop Portals.MIT
- AlicenseBqualityDmaintenanceAn MCP server that provides AI agents with a full Ubuntu desktop environment inside Docker, enabling them to perform complex computer tasks like browsing, coding, testing, and GUI automation.3613MIT
- FlicenseAqualityDmaintenanceA Model Context Protocol server that enables AI assistants to create, control, and interact with virtual desktop environments through E2B's secure cloud sandboxes.64-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that gives any AI full control over a Windows PC, enabling application control, mouse/keyboard automation, screen capture, browser automation, and more.67 PyPI6MIT