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
Payai X402 Tools

6 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago