RooCode-MCP-Server-Installer

Created By
suttonwilliamda year ago
Overview

what is RooCode-MCP-Server-Installer?

RooCode-MCP-Server-Installer is a tool designed to automate the installation of the RooCode MCP server, simplifying the setup process for users.

how to use RooCode-MCP-Server-Installer?

To use the installer, clone the repository from GitHub, navigate to the project directory, and run the installation script provided in the documentation.

key features of RooCode-MCP-Server-Installer?

  • Automated installation process for the RooCode MCP server
  • Easy setup with minimal user intervention
  • Comprehensive documentation for installation and configuration

use cases of RooCode-MCP-Server-Installer?

  1. Quickly setting up a development environment for RooCode applications.
  2. Streamlining server deployment for production environments.
  3. Reducing manual configuration errors during installation.

FAQ from RooCode-MCP-Server-Installer?

  • Is RooCode-MCP-Server-Installer free to use?

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

  • What platforms does the installer support?

The installer is designed to work on various operating systems, including Windows, macOS, and Linux.

  • Where can I find the documentation?

Documentation is available in the GitHub repository under the 'docs' folder.

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

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year 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)

a day ago