stygian-mcp

Unified MCP (Model Context Protocol) server aggregating stygian-graph, stygian-browser, and stygian-proxy into a single JSON-RPC 2.0 process over stdin/stdout.

An LLM agent connecting to this server can scrape URLs, run pipeline DAGs, automate browsers, manage proxy pools, and combine all three capabilities — without needing to connect to three separate processes.

Installation

# Standalone binary
cargo install stygian-mcp

# Or add to your project
cargo add stygian-mcp

Usage

Run the binary directly:

stygian-mcp

This starts a JSON-RPC 2.0 server on stdin/stdout. Connect any MCP-compatible client (VS Code, Claude, IDE plugins, etc.) to begin calling scraping, browser, and proxy tools.

Features

Enable extraction (requires stygian-browser/extract and stygian-graph/extract):

cargo install stygian-mcp --features extract

Enable CDP attach (lets agents attach to a running Chrome/Chromium profile):

cargo install stygian-mcp --features mcp-attach

MCP Tools

All tools from the three underlying crates are available under their respective prefixes:

* browser_attach requires the mcp-attach feature.

Runner-first tool:

• browser_acquire_and_extract is the recommended high-level browser path for acquisition + extraction in one call.
• Supported mode values are fast, resilient, hostile, and investigate.

The aggregator also adds two cross-crate tools:

Architecture

  LLM / IDE / Chat Interface
     │  JSON-RPC 2.0 (stdin/stdout)
     ▼
┌─────────────────────────────────────┐
│        McpAggregator                │
│  tools/list ── merge & dispatch     │
│  tools/call ── route by prefix ─┐  │
└──────────────────┬──────────────┼──┘
                   │              │
        ┌──────────┼──────────────┘
        ▼          ▼              ▼
   GraphHandler  BrowserHandler  ProxyHandler

Tool Execution Flow

1. Client calls tools/list → aggregator merges all three sub-server tool lists
2. Client calls tools/call with a tool name + params
3. Aggregator routes:

• graph_* → strips prefix, forwards to graph sub-server
• browser_* → forwards to browser sub-server
• proxy_* → forwards to proxy sub-server
• scrape_proxied, browser_proxied → handled by aggregator (cross-crate coordination)

Examples

Scrape with Proxy Rotation

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "scrape_proxied",
    "arguments": {
      "url": "https://example.com"
    }
  }
}

Browser Screenshot Through Proxy

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "browser_proxied",
    "arguments": {
      "url": "https://example.com"
    }
  }
}

Capture and Resume a Login Session

Capture login state after a manual or automated auth flow:

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "browser_auth_session",
    "arguments": {
      "session_id": "01HV4...",
      "mode": "capture",
      "file_path": "/tmp/reddit-session.json",
      "ttl_secs": 86400
    }
  }
}

Restore it in a subsequent session:

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "browser_auth_session",
    "arguments": {
      "session_id": "01HV5...",
      "mode": "resume",
      "file_path": "/tmp/reddit-session.json"
    }
  }
}

Extract Structured Data

With extract feature enabled, use browser_extract:

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "browser_extract",
    "arguments": {
      "session_id": "01HV4...",
      "url": "https://example.com/products",
      "root_selector": "article.product",
      "schema": {
        "name": { "selector": "h2" },
        "href": { "selector": "a", "attr": "href" }
      }
    }
  }
}

Runner-First Acquisition by Mode

Use browser_acquire_and_extract when you want deterministic strategy escalation with minimal orchestration code.

fast mode:

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "browser_acquire_and_extract",
    "arguments": {
      "url": "https://example.com",
      "mode": "fast"
    }
  }
}

resilient mode:

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "browser_acquire_and_extract",
    "arguments": {
      "url": "https://example.com/catalog",
      "mode": "resilient",
      "wait_for_selector": "article.item"
    }
  }
}

hostile mode:

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "browser_acquire_and_extract",
    "arguments": {
      "url": "https://example.com/challenged",
      "mode": "hostile",
      "wait_for_selector": "main",
      "total_timeout_secs": 60
    }
  }
}

investigate mode:

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "browser_acquire_and_extract",
    "arguments": {
      "url": "https://example.com",
      "mode": "investigate",
      "extraction_js": "({ title: document.title, href: location.href })"
    }
  }
}

Migration note (old low-level path vs new runner path):

• Old low-level MCP path: browser_acquire -> browser_navigate -> browser_eval or browser_extract -> browser_release.
• New runner path: browser_acquire_and_extract with one call and explicit mode.
• The low-level path remains supported for custom multi-step interactions.

License

Licensed under either the GNU Affero General Public License v3.0 (AGPL-3.0-only) or the Commercial License at your option.