Log inSubmit server
Fortress logo

Fortress

fortress MCP server gives AI agents stealth Chromium browsing for protected pages and clean web-data extraction.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Fortress

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "fortress": {
      "command": "npx",
      "args": [
        "-y",
        "tilion-mcp"
      ],
      "env": {
        "TILION_LICENSE_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y tilion-mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 7d ago.

Overview

The fortress MCP server connects AI agents to Fortress, a Chromium-based browser engine designed to reduce blocks from bot-detection systems. It runs through the `tilion mcp` CLI and exposes 29 browser tools for agent-driven web access. Reach for it when ordinary browser automation cannot load pages protected by Cloudflare, DataDome, CAPTCHA, or similar systems. Fortress can run headlessly and is available through Docker, Python, npm, or portable builds.

Use cases

  • Fetch pages protected by bot-detection systems
  • Extract structured data from rendered websites
  • Navigate paginated web content
  • Crawl product or content detail pages

Key features

  • Stealth Chromium engine
  • MCP server with 29 documented tools
  • Headless browser operation
  • CDP connectivity for Playwright and Puppeteer
  • Docker and Python/npm installation options
  • Configurable license activation for CI and agents

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

8/8 checks healthy over the last 44d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 7d ago via OSV.dev · tilion-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars771Stargazers on the source repository.
npm downloads44Package downloads in the last 30 days.
Last commit17d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Fortress works

What fortress MCP server does

The fortress MCP server gives an AI agent access to the Fortress Chromium engine through Model Context Protocol tools. Fortress is intended for browser automation against websites that may reject standard scripted browsers.

The underlying browser is a modified Chromium build. Its fingerprint changes are implemented inside Chromium rather than added as page-level JavaScript patches or browser extensions. This lets existing automation workflows connect to the engine over Chrome DevTools Protocol while keeping their normal browser logic.

How it works

Run tilion mcp to start the MCP server. The server uses the Fortress browser engine and presents its browsing functionality to an MCP-compatible agent.

Fortress can also be launched independently and exposed through CDP. Playwright and Puppeteer can connect to that endpoint, so the same engine can serve both MCP-based agents and conventional browser-automation code. The engine is designed to run headlessly, including on datacenter infrastructure and in Docker.

The fortress MCP server is most relevant when an agent needs to load real pages instead of relying on a public API or static HTTP requests. It may also fit crawling tasks that require navigation across pages or collecting fields from detail pages, as shown by the repository’s examples.

Setup and configuration

Install the available Fortress distribution through Python or npm, or run the published Docker image:

  • pip install tilion-fortress
  • npm install tilion-fortress
  • docker run --rm -p 9222:9222 tilion/fortress:latest

The CLI is included in the project workflow. Use tilion mcp for the MCP mode. The browser engine can also be started with tilion, which prints a CDP endpoint for external clients.

Version 3 activation is free for developers and has no stated machine, session, or concurrency caps. Activation is optional: without it, Fortress runs on the public first-generation engine. For CI, Docker, or agent environments, provide TILION_LICENSE_KEY or use tilion activate --token <jwt>. Interactive activation can use GitHub, Google, or email, while headless activation supports remote hosts.

Prebuilt distributions are listed for Linux and Windows, with additional portable Linux architectures and macOS source builds.

Tools and capabilities

The fortress MCP server is described as exposing stealth browsing as agent tools. Supported use cases documented in the repository include:

  • Loading pages protected by common bot-detection services.
  • Navigating paginated sites.
  • Crawling product or content detail pages.
  • Extracting clean or structured data from rendered pages.
  • Running browser sessions fully headlessly.

The README identifies 29 MCP tools but does not enumerate their operations, parameters, return formats, authentication behavior, or session controls. Confirm those details in the project’s MCP documentation before building against specific tool names.

Limitations and notes

Results can depend on the target’s detection system, network address, session state, and other site-specific controls. A stealth browser does not replace permission to collect or process a site’s content.

The repository reports benchmark results for a set of protected sites, but those results should not be treated as universal performance guarantees.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Fortress

fortress is an MCP server that connects AI agents to the Fortress stealth Chromium engine and exposes browser automation tools for navigating and extracting web data. It targets pages where ordinary automation is blocked by bot detection.

Run `tilion mcp` after installing the Fortress distribution or CLI.

Yes, Fortress can run in Docker. The documented command is `docker run --rm -p 9222:9222 tilion/fortress:latest`; use `tilion mcp` for MCP mode, while port 9222 is documented for the browser’s CDP endpoint.

Set `TILION_LICENSE_KEY` to a license key or run `tilion activate --token <jwt>`.

Related MCP servers

All in Cloud Platforms All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewFortress AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/fortress?style=directory)](https://allmcps.com/mcp/fortress)
HTML Embed
<a href="https://allmcps.com/mcp/fortress"><img src="https://allmcps.com/api/badge/fortress?style=directory" alt="Fortress on AllMCPs" /></a>