add-mcp-server

Create a workspace package and register an MCP server in the proto-mcp CLI registry.

Updated Jul 5, 2025
One-click install
npx skills add https://github.com/nsuberi/proto-portal-showcase-hub --skill add-mcp-server-nsuberi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-mcp-server
Source: https://github.com/nsuberi/proto-portal-showcase-hub/tree/main/.claude/skills/add-mcp-server
Command: npx skills add https://github.com/nsuberi/proto-portal-showcase-hub --skill add-mcp-server-nsuberi

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about add-mcp-server

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new MCP server to a Node.js CLI workspace?

To add an MCP server, create a new workspace package under shared/mcp-servers, update the root package.json workspaces, add it to shared/mcp-cli dependencies, and register it in the CLI registry.

What files need to be updated to register an MCP server in the proto-mcp CLI?

Registering an MCP server requires updating the root package.json workspaces, adding workspace dependencies to shared/mcp-cli, and inserting an entry in shared/mcp-cli/src/registry.ts for CLI discovery.

How do I scaffold a standalone TypeScript MCP server package?

Scaffolding a TypeScript MCP server package involves creating a directory under shared/mcp-servers, configuring package.json and tsconfig, and defining source entry points to expose tools, resources, or prompts.

Can I integrate a new MCP server with automated tooling or Claude?

Yes, after building and testing the MCP server package, you can optionally register it in a .mcp.json configuration file to enable consumption by automated tooling or Claude integration.

Why do I need to update the CLI registry when adding an MCP server?

Updating the CLI registry in shared/mcp-cli/src/registry.ts is required to expose the new MCP server package for discovery and consumption by the proto-mcp CLI, preventing visibility errors.

What is the best way to coordinate multiple repository changes for a new MCP server?

The best way to coordinate MCP server changes is to follow a step-by-step pattern that consistently handles packaging, workspace integration, CLI dependencies, and registry updates to avoid errors.