MCP Server Starter Template

MCP Server Starter Template

A comprehensive template for building MCP servers that expose UI component registries and design systems to AI assistants. It enables users to browse, fetch, and retrieve implementation details from registries following the shadcn/ui format.

Category
Visit Server

README

MCP Server Starter Template

A comprehensive starter template for building Model Context Protocol (MCP) servers, specifically designed for UI libraries and component registries. This template provides a robust foundation for creating MCP servers that can fetch, categorize, and provide component information to AI assistants like Claude.

šŸŒŽ Real world example?

Check out the stackzero-labs/mcp which uses this template to expose its UI components and blocks to AI models. You can also checkout the UI referenced project stackzero/ui

šŸš€ Features

  • Ready-to-use MCP server with TypeScript support
  • Component registry integration for UI libraries
  • Categorized component organization with flexible category system
  • Zod schema validation for type safety
  • Development tools including hot reload and inspector
  • Example implementation using a real project URL for demonstration
  • Extensible architecture for custom component types and categories

šŸ“‹ Prerequisites

  • Node.js 18 or higher
  • pnpm (recommended) or npm
  • Basic understanding of TypeScript and MCP

šŸ¤ Intended Use Cases

This template is specifically designed for libraries following the registry format (like shadcn/ui), making it ideal for:

  • UI component libraries
  • Design systems
  • Component registries that need to be accessible via AI assistants
  • Tools, utilities, and frameworks that require a structured way to expose UI components to AI models

Read more about components registries like shadcn/ui here Component Registries.

With some customizations however, it can be adapted for other types of MCP servers as well.

šŸ› ļø Installation

  1. Clone or download this template:
git clone https://github.com/mnove/mcp-starter.git
cd mcp-starter
  1. Install dependencies:
pnpm install
  1. Build the project:
pnpm run build

āš™ļø Configuration

1. Update Project Configuration

Edit src/lib/config.ts to point to your own component registry:

export const mcpConfig = {
  projectName: "your-project-name",
  // Replace with your actual project URL
  baseUrl: "https://your-ui-library.com",
  registryUrl: "https://your-ui-library.com/r",
  registryFileUrl: "https://your-ui-library.com/registry.json",
};

Note: This template currently uses https://ui.stackzero.co as a demonstration URL. You must replace this with your actual project URL for production use.

2. Define Component Categories

Customize src/lib/categories.ts to match your component structure:

export const componentCategories = {
  Buttons: ["button-primary", "button-secondary", "button-ghost"],
  Forms: ["input-text", "input-email", "textarea"],
  // Add your categories here
};

3. Update Server Metadata

Modify src/server.ts to customize your server information:

const server = new McpServer({
  name: "your-mcp-server-name",
  version: "1.0.0",
});

šŸƒā€ā™‚ļø Development

Start Development Server

pnpm run dev

Build for Production

pnpm run build

Inspect MCP Server

pnpm run inspect

This opens the MCP Inspector to test your server tools interactively.

šŸ“š Available Tools

The MCP server provides the following tools:

getUIComponents

Returns a comprehensive list of all UI components from your registry.

Category-specific Tools

Dynamic tools are created for each category defined in componentCategories:

  • getButtons - Get all button components
  • getForms - Get all form components
  • etc.

Each category tool provides:

  • Component implementation details
  • Usage examples
  • Installation instructions
  • Related components

šŸ—ļø Project Structure

mcp-starter/
ā”œā”€ā”€ src/
│   ā”œā”€ā”€ server.ts              # Main MCP server implementation
│   ā”œā”€ā”€ lib/
│   │   ā”œā”€ā”€ config.ts          # Configuration settings
│   │   └── categories.ts      # Component categories
│   └── utils/
│       ā”œā”€ā”€ api.ts             # API fetching utilities
│       ā”œā”€ā”€ formatters.ts      # Data formatting helpers
│       ā”œā”€ā”€ schemas.ts         # Zod validation schemas
│       └── index.ts           # Utility exports
ā”œā”€ā”€ dist/                      # Built files
ā”œā”€ā”€ package.json
└── README.md

šŸ”§ Customization

Adding New Component Types

  1. Update schemas in src/utils/schemas.ts:
export const CustomComponentSchema = z.object({
  name: z.string(),
  category: z.string(),
  // Add your fields
});
  1. Add API functions in src/utils/api.ts:
export async function fetchCustomComponents() {
  // Your implementation
}
  1. Register new tools in src/server.ts:
server.tool("getCustomComponents" /*...*/);

Extending Categories

Simply add new categories to src/lib/categories.ts:

export const componentCategories = {
  // Existing categories...
  Navigation: ["navbar", "sidebar", "breadcrumbs"],
  DataDisplay: ["table", "card", "badge"],
};

The server will automatically create tools for new categories.

Why categories?

Categories help organize components logically, making it easier for AI assistants to find and suggest relevant components based. Also, some models and IDE have a limit on the number of tools they can handle, so categorizing helps to keep the number of tools manageable.

šŸ“– Registry Format

Your component registry should follow this structure:

Registry File (registry.json)

{
  "registry": [
    {
      "name": "button-primary",
      "type": "registry:component",
      "description": "Primary button component"
    }
  ]
}

Component Details (/r/{component-name}.json)

{
  "name": "button-primary",
  "type": "registry:component",
  "files": [
    {
      "content": "// Component implementation"
    }
  ]
}

šŸš€ Deployment

As a Local MCP Server

  1. Build the project:
pnpm run build
  1. Configure in your MCP client (e.g., Claude Desktop):
{
  "mcpServers": {
    "your-mcp-server": {
      "command": "node",
      "args": ["/path/to/mcp-starter/dist/server.js"]
    }
  }
}

As an NPM Package

You can also publish this template as an NPM package for easy installation in other projects.

  1. Update package.json with your details
  2. Build and publish:
pnpm run build
npm publish

šŸ¤ Contributing

See CONTRIBUTING.md for details on how to contribute to this project.

šŸ“„ License

This project is licensed under the MIT License - see the LICENSE file for details.

šŸ¤ Contact

Marcello - @mnove

šŸ™ Acknowledgments

  • Built with Model Context Protocol SDK
  • Inspired by the need for better AI-component integration
  • Thanks to the MCP community for their contributions

āš ļø Important: Remember to replace https://ui.stackzero.co with your actual project URL before using this template in production!

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
E2B

E2B

Using MCP to run code via e2b.

Official
Featured