Summary

One connection instead of twelve, with containers and stored secrets in between.

The part that saves real time is adding a server by URL and letting the analysis work out how to run it, rather than reading someone's README to find the launch command. Secret files are handled properly — encrypted at rest, mounted read-only, and never returned in profile listings — which is the thing that usually stops teams from sharing a server setup.

What it is

A gateway that installs MCP servers from GitHub repositories, keeps their credentials, and re-exposes the tools you enable through a single connection.

What you get

Add a server by pasting a GitHub URL — the repository is analyzed and configured automatically
Each server runs in its own Docker container, with npx, uvx and Docker runtimes supported
Per-server tool enablement, so a client sees only the tools you switched on
Centralized API keys, plus encrypted secret files — JSON credentials, PEM certificates, PKCS12, Java KeyStores — mounted read-only into the container and exposed as a path in an environment variable you name
Start, stop and restart servers from the web interface, with container health monitoring and remounting
Google OAuth sign-in with optional domain restriction, session auth for the web UI, and JWT tokens for API access
Runs as stdio for a local desktop client, or over HTTP with OAuth for a shared deployment

Requirements

SECRET_KEY and ANTHROPIC_API_KEY — the Anthropic key is what analyzes repositories on add. Docker is needed for the isolation. Install with uv sync or pip, then start with mcp-anywhere serve http and open port 8000, or mcp-anywhere serve stdio for a local desktop client. Google sign-in is optional and needs GOOGLE_OAUTH_CLIENT_ID and GOOGLE_OAUTH_CLIENT_SECRET. The project describes itself as beta.