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 this is intended to set the direction we're going.
The mcp tool acts as an MCP Server for Clients like Claude and Zed. It is unique in that it doesn't provide any capabilities on its own. Instead it acts as a sort of broker between Clients and any number of installed Servers. The mcp tool facilitates that by helping you discover and install MCP Servers. It talks to a public registry of MCP Servers and is able to download, configure and run these in a secure and frictionless way.
In addition to acting as a broker, mcp:
- Allows Servers to request OAuth2 credentials and manages the flow for obtaining, storing and refreshing these credentials.
- Keeps an audit log of all operations going through it and provides a UI for reviewing audit logs across different sessions and Clients.
- Reduces host system dependencies to
docker. By leveragingdocker,mcpallows you to run Servers without mutating your host with any necessary tool-chains or dependencies. In addition,mcpleverages the containerization and isolation technology indockerto isolate your host system from malicious or buggy MCP Servers.
Install mcp run <protocol> as an MCP Server for the supplied Client.
Search the public MCP server Registry for servers matching the query. A rich description will be shown for matching servers.
Install an MCP Server from the public package Registry. This will start a flow that captures any required configuration for the MCP package, persist it locally and then start it.
Uninstall an MCP Server that was previously installed. Running clients will be notified such that they reload resources, tools, etc.
This is the entrypoint used by Clients that speak the stdio protocol. It will run mcp as an MCP Server that acts as a broker for all installed MCP Servers.