roo-mcp-server

Created By
mows21a year ago
Roo MCP Server - Real-world automation for web scraping and browser control
Overview

what is Roo MCP Server?

Roo MCP Server is a tool designed for real-world automation, specifically for web scraping and browser control, allowing users to automate repetitive tasks in web environments.

how to use Roo MCP Server?

To use Roo MCP Server, set up the server by following the installation instructions on the GitHub repository, then configure your scraping tasks and execute them through the provided commands.

key features of Roo MCP Server?

  • Real-world automation capabilities for web scraping.
  • Control over browser actions to automate tasks.
  • Easy setup and configuration through a server interface.

use cases of Roo MCP Server?

  1. Automating data extraction from websites for research purposes.
  2. Performing repetitive tasks like form submissions and data entry.
  3. Monitoring web pages for changes and updates.

FAQ from Roo MCP Server?

  • Can Roo MCP Server handle dynamic web pages?

Yes! It is designed to interact with dynamic content and can handle JavaScript-rendered pages.

  • Is there a limit to the number of tasks I can automate?

No, you can automate as many tasks as your server resources allow.

  • Is Roo MCP Server free to use?

Yes! It is open-source and free to use for everyone.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mows21
Star
0
Language
-
License
-

Recommend Servers

View All
Crevio

a day ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

19 hours ago