YAMCP (YAM-C-P) is a command-line tool for organizing multiple MCP servers into local workspaces, and its name comes from "Yet Another MCP." It can seamlessly connect multiple local or remote MCP servers, group them into unified workspaces, and expose them to AI applications as a "Yet Another MCP server (YAM)".
Main uses:
- Create dedicated workspaces by specific function, such as for programming, design, research, and other scenarios.
- Create workspaces by the AI application consuming the servers, such as building a separate YAM for Cursor, Claude, and Windsurf, or any combination.
- Simplify monitoring and debugging of MCP servers: centralize all server communication logs into a single storage location, without having to dig into each AI client application's logs separately.
Core concepts:
- MCP server: A remote or local server that provides Model Context Protocol services.
- Workspace (YAM): A collection of MCP servers that can be shared with AI applications, such as workspaces for programming, writing, design, and so on.
- Gateway: A local MCP server that manages connections to the configured MCP servers in the current workspace and exposes them to the AI application's MCP client through one unified server.
What you can do:
- Create workspaces by AI application (such as Cursor, Claude, GitHub Copilot) to group MCP servers.
- Group servers by workflow purpose (such as software development, data science, technical writing).
- Connect AI applications to a single gateway to access all servers in the workspace.
- Manage and monitor multiple MCP server connections through a unified interface.
- Track all server communication with detailed logs and debugging capabilities.
Top-level commands:
- server: Manage MCP providers.
- yam: Manage workspaces (yams).
- run: Run the gateway with a specified workspace.
- log: View server log locations.
System architecture components:
- CLI commands: The user interface for managing servers and workspaces.
- McpGateway: The core component that coordinates the gateway server and router.
- GatewayServer: Handles communication with AI applications over stdio transport.
- GatewayRouter: Manages connections to configured MCP servers.
- Logger: Provides unified logging for all components.
- Store: Manages provider and workspace configurations.
- MCP servers: Local (stdio) and remote (SSE) servers that provide MCP services.
YAMCP also provides YAMCP UI created by @eladcandroid, which offers an intuitive web interface through a general-purpose dashboard to manage MCP servers and workspaces. Full documentation is available at https://github.com/eladcandroid/yamcp-ui .
Information such as installation methods, specific command syntax, platform support, fees, and pricing is not provided in the given materials.
