MCP Containers

Created By
metoriala year ago
Containerized versions of hundreds of MCP servers 📡 🧠
Overview

What is MCP Containers?

MCP Containers provides containerized versions of hundreds of Model Context Protocol (MCP) servers, simplifying the setup and management of these servers for developers and researchers.

How to use MCP Containers?

To use MCP Containers, simply pull the Docker image for the desired MCP server from the repository. A list of available servers is provided in the documentation, along with their respective readme files for guidance.

Key features of MCP Containers?

  • 🚀 Simple Setup: Easily pull Docker images to use any MCP server.
  • 🛠️ Always Up-to-Date: Images are automatically updated daily to ensure the latest features and security patches.
  • 🔒 Secure: Run MCP servers in isolated containers for enhanced security.

Use cases of MCP Containers?

  1. Quickly deploy various MCP servers for testing and development.
  2. Use containerized servers for research purposes without complex setup.
  3. Integrate multiple MCP servers into applications seamlessly.

FAQ from MCP Containers?

  • Can I contribute to MCP Containers?

Yes! Contributions are welcome. You can open an issue or submit a pull request to add new containerized MCP servers.

  • Are the containers secure?

Yes! The containers run in isolated environments, providing a secure way to use MCP servers.

  • How often are the images updated?

The images are automatically updated daily to ensure you have the latest versions.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
metorial
Star
863
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago
Voyei

4 hours ago