📌Overview

Purpose: MCP is designed to facilitate the discovery, installation, and management of Model Context Protocol servers via a command-line tool and local user interface.

Overview: The MCP tool operates as a broker between clients (such as Claude and Zed) and multiple installed MCP servers. It streamlines the process of managing these servers by connecting to a public registry for discovery, installation, and secure operation without altering the local system environment.

Key Features:

Server Discovery and Installation: MCP connects to a public registry to search for and install various MCP servers, handling configuration and ensuring a seamless setup process.
OAuth2 Credential Management: The tool manages the OAuth2 credential lifecycle for MCP servers, facilitating secure requests and refreshing of credentials automatically.
Audit Log Tracking: MCP maintains an audit log of all operations, providing a UI for reviewing activity across different sessions and clients, ensuring transparency and traceability.
Docker Integration: By utilizing Docker, MCP minimizes host system dependencies and isolates MCP servers to protect the system from potential risks associated with malicious or faulty servers.

MCP

MCP is a command-line tool and local UI for discovering, installing, and managing Model Context Protocol servers.

Note:
This README describes an aspirational vision. Almost none of this is ready, but it is intended to set the direction.

The mcp tool acts as an MCP Server for clients like Claude and Zed. It does not provide capabilities on its own but functions as a broker between clients and any number of installed servers. The tool helps discover and install MCP servers by communicating with a public registry. It can download, configure, and run these servers securely and frictionlessly.

In addition to acting as a broker, mcp:

Allows servers to request OAuth2 credentials and manages obtaining, storing, and refreshing these credentials.
Keeps an audit log of all operations and provides a UI for reviewing logs across different sessions and clients.
Reduces host system dependencies to just docker. By leveraging Docker, mcp allows running servers without modifying the host system with additional tool-chains or dependencies. Additionally, Docker isolation protects the host system from malicious or buggy MCP servers.

CLI Interface

mcp install <claude|zed|...>

Install mcp run <protocol> as an MCP Server for the specified client.

mcp registry search

Search the public MCP server registry for servers matching the query. A detailed description is shown for matching servers.

mcp package install <package[@]>

Install an MCP Server from the public package registry. This starts a flow to capture any required configuration, persists it locally, and then starts the server.

mcp package uninstall

Uninstall a previously installed MCP Server. Running clients will be notified to reload resources, tools, etc.

mcp run stdio

Used by clients that speak the stdio protocol. Runs mcp as an MCP Server acting as a broker for all installed MCP Servers.