Organize your MCP servers in local workspaces, share them as Yet-Another-MCP through a single command
Most developer tooling work still happens through a UI a human drives. 🍠 YAMCP MCP server moves it into the conversation instead. Organize your MCP servers in local workspaces, share them as Yet-Another-MCP through a single command.
YAMCP (YAM-C-P) is a command-line tool for organizing and managing MCP servers as local workspaces. It seamlessly connects to multiple MCP servers, local or remote, grouping them into a unified workspace exposed as Yet Another MCP server (YAM) for AI applications. You can create dedicated workspaces based on specific functionality (e.g., a YAM workspace for coding, design, research, ...) or based on the AI apps that consume servers (e.g., a YAM for Cursor, Claude, Windsurf) or any other combination in between. In addition, it simplifies monitoring and debugging MCP servers by centralizing all server
yamcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The server publishes 4 tools. What each one is for:
server — Manage MCP providersyam — Manage workspaces (yams)run — Run the gateway with a workspacelog — View the server log locationPlenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. 🍠 YAMCP's toolset — server, yam, run and 1 more — is a fair guide to whether it matches your workflow. It is maintained by hamidra; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| server | Manage MCP providers |
| yam | Manage workspaces (yams) |
| run | Run the gateway with a workspace |
| log | View the server log location |
{
"mcpServers": {
"yamcp": {
"command": "npx",
"args": ["-y", "yamcp"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.