FerrumMCP

FerrumMCP is a browser automation server that implements the Model Context Protocol (MCP) to let AI assistants interact with web pages through a standardized API. It supports session-based management, navigation, interaction (clicking, typing, form filling, and cookie/CAPTCHA handling), extraction (text, HTML, screenshots, metadata), and advanced features like JavaScript evaluation and Shadow DOM access. Enterprise features include BotBrowser integration for anti-detection automation and fingerprint management. You can run FerrumMCP via Docker (recommended), or install from RubyGems or source if you prefer a local Ruby environment. Once running, you can manage multiple browser sessions, perform automated navigation and interactions, extract content, and monitor health and metrics through the provided API endpoints.

Prerequisites:

• Docker installed on your host (recommended) or a Ruby environment if you prefer gems or source builds.
• Basic familiarity with MCP tooling and API usage.

Option A: Docker (recommended)

1. Pull the image: docker pull eth3rnit3/ferrum-mcp:latest
2. Run the container (exposes MCP API on port 3000): docker run --security-opt seccomp=unconfined -p 3000:3000 eth3rnit3/ferrum-mcp:latest
3. Optional BotBrowser variant (anti-detection) requires additional profiles and env vars as shown in the FerrumMCP docs.

Option B: Ruby Gem (local development)

1. Install Ruby (3.2+ is recommended).
2. Install the gem: gem install ferrum-mcp
3. Start the server: ferrum-mcp start

Option C: From Source

1. Clone the repository: git clone https://github.com/Eth3rnit3/FerrumMCP.git
2. Change into the directory: cd FerrumMCP
3. Install dependencies: bundle install
4. Run the server: ruby bin/ferrum-mcp

For full installation details, refer to the Getting Started guide in the FerrumMCP documentation.

Tips and common considerations:

• Docker deployment is the simplest path to production, with options for standard Chromium and BotBrowser anti-detection modes.
• FerrumMCP supports multiple sessions per instance; monitor idle timeouts and resource usage as sessions multiply.
• If enabling BotBrowser, you’ll need valid trial/premium profiles; demo profiles can cause instability.
• Environment variables (example): BROWSER_BOTBROWSER=botbrowser:/opt/botbrowser/chrome:BotBrowser:Anti-detection browser BOT_PROFILE_MACOS_1=/profiles/profile_1.enc:Profile 1:Trial profile 1
• The API provides 27+ tools across 6 categories (Session Management, Navigation, Interaction, Extraction, Advanced, and Enterprise features). Review API_REFERENCE.md for exact method names and usage examples.
• Keep your server up to date with the latest Docker image or gem to benefit from security and feature updates.