Unchained Infra MCP Server

Open infrastructure and control plane for Unchained, a browser automation system built on raw Chrome DevTools Protocol. That is what the unchained infra mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

• The browser tunnel is here. You can inspect how agent auth, relay routing, and
• The deployment path is here. Docker Compose, Caddy routing, EC2 deploy scripts,
• The trust boundary is explicit. Public services do not directly import private
• The local dev path is real. You can run the relay and web app locally with

The tools it exposes

The server publishes 1 tool. What each one is for:

• docker-compose.yml — production deployment topology

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

What it needs from you

Configuration is passed through the environment: HOSTED_AGENT_SERVICE_TOKEN, TRIAL_AGENT_KEY, PRIVATE_CORE_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Unchained Infra's toolset — docker-compose.yml — is a fair guide to whether it matches your workflow. It is maintained by protostatis; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Things to watch

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.