What problem does it solve?
Adding a new MCP server to the proto-mcp CLI requires multiple coordinated repository changes (new workspace package, build config, CLI dependency, and registry entry) and can be error-prone without clear guidance; this Skill provides a step-by-step pattern to create, register, and test a server package consistently.
Core Features & Use Cases
- Scaffold and packaging: Prescribes package.json, tsconfig, and source entry points for a standalone MCP server workspace.
- Workspace & CLI integration: Shows how to add the package to root workspaces, add workspace:* dependencies to shared/mcp-cli, and register the server in the CLI registry for discovery.
- Testing and runtime: Covers build and test commands and optional .mcp.json registration for automated tooling or Claude integration.
- Use Case: Add a design-tokens MCP server or a domain-specific resource server that exposes tools, resources, and prompts to the proto-mcp CLI.
Quick Start
Create a new workspace directory under shared/mcp-servers named {server-name}, add it to the root package.json workspaces and to shared/mcp-cli dependencies, and then add a registry entry in shared/mcp-cli/src/registry.ts to expose the server to the CLI.