MCP Server Boilerplate
Offers complete TypeScript support with proper type definitions for building MCP servers with type safety.
Utilizes Zod for schema validation of tool parameters, enabling strong typing and validation for inputs to custom tools and prompts.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP Server Boilerplate show me how to add a new tool that fetches weather data"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Server Boilerplate
A starter template for building MCP (Model Context Protocol) servers. This boilerplate provides a clean foundation for creating your own MCP server that can integrate with Claude, Cursor, or other MCP-compatible AI assistants.
Purpose
This boilerplate helps you quickly start building:
Custom tools for AI assistants
Resource providers for dynamic content
Prompt templates for common operations
Integration points for external APIs and services
Related MCP server: MCP Template
Features
Simple "hello-world" tool example
TypeScript support with proper type definitions
Easy installation scripts for different MCP clients
Clean project structure ready for customization
How It Works
This MCP server template provides:
A basic server setup using the MCP SDK
Example tool implementation
Build and installation scripts
TypeScript configuration for development
The included example demonstrates how to create a simple tool that takes a name parameter and returns a greeting.
Getting Started
# Clone the boilerplate
git clone <your-repo-url>
cd mcp-server-boilerplate
# Install dependencies
pnpm install
# Build the project
pnpm run build
# Start the server
pnpm startInstallation Scripts
This boilerplate includes convenient installation scripts for different MCP clients:
# For Claude Desktop
pnpm run install-desktop
# For Cursor
pnpm run install-cursor
# For Claude Code
pnpm run install-code
# Generic installation
pnpm run install-serverThese scripts will build the project and automatically update the appropriate configuration files.
Usage with Claude Desktop
The installation script will automatically add the configuration, but you can also manually add it to your claude_desktop_config.json file:
{
"mcpServers": {
"your-server-name": {
"command": "node",
"args": ["/path/to/your/dist/index.js"]
}
}
}Then restart Claude Desktop to connect to the server.
Customizing Your Server
Adding Tools
Tools are functions that the AI assistant can call. Here's the basic structure:
server.tool(
"tool-name",
"Description of what the tool does",
{
// Zod schema for parameters
param1: z.string().describe("Description of parameter"),
param2: z.number().optional().describe("Optional parameter"),
},
async ({ param1, param2 }) => {
// Your tool logic here
return {
content: [
{
type: "text",
text: "Your response",
},
],
};
}
);Adding Resources
Resources provide dynamic content that the AI can access:
server.resource(
"resource://example/{id}",
"Description of the resource",
async (uri) => {
// Extract parameters from URI
const id = uri.path.split("/").pop();
return {
contents: [
{
uri,
mimeType: "text/plain",
text: `Content for ${id}`,
},
],
};
}
);Adding Prompts
Prompts are reusable templates:
server.prompt(
"prompt-name",
"Description of the prompt",
{
// Parameters for the prompt
topic: z.string().describe("The topic to discuss"),
},
async ({ topic }) => {
return {
description: `A prompt about ${topic}`,
messages: [
{
role: "user",
content: {
type: "text",
text: `Please help me with ${topic}`,
},
},
],
};
}
);Project Structure
├── src/
│ └── index.ts # Main server implementation
├── scripts/ # Installation and utility scripts
├── dist/ # Compiled JavaScript (generated)
├── package.json # Project configuration
├── tsconfig.json # TypeScript configuration
└── README.md # This fileDevelopment
Make changes to
src/index.tsRun
pnpm run buildto compileTest your server with
pnpm startUse the installation scripts to update your MCP client configuration
Next Steps
Update
package.jsonwith your project detailsCustomize the server name and tools in
src/index.tsAdd your own tools, resources, and prompts
Integrate with external APIs or databases as needed
License
MIT
Available Tools
2 toolsget-mcp-docsD
Make an MCP server
Inputs: name (required).
hello-worldB
Say hello to the user
Inputs: name (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one is for creating MCP servers (get-mcp-docs) and the other is for greeting users (hello-world). There is no overlap or ambiguity between these functions, making tool selection straightforward.
The naming is inconsistent: get-mcp-docs uses kebab-case with a verb-noun structure, while hello-world uses kebab-case but is a phrase rather than a clear action. There is no predictable pattern across the tool set, making it harder to infer functionality from names alone.
With only 2 tools, this server feels thin and under-scoped for a 'boilerplate' purpose, which typically implies a foundational set of utilities. The count is too low to provide meaningful coverage or demonstrate a coherent tool surface for server development.
The server is severely incomplete for a boilerplate MCP server domain. It lacks essential operations like configuration, testing, deployment, or common utilities, leaving obvious gaps that would hinder agent workflows and fail to support typical development tasks.
Maintenance
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
A Model Context Protocol server for Wix AI tools
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
The Telnyx MCP server is an official implementation of the Model Context Protocol that enables AI clients (like Claude Desktop, Cursor, and OpenAI Agents) to interact with Telnyx's telephony, messaging, and AI assistant APIs. It provides comprehensive capabilities including making and managing phone calls, sending SMS/MMS messages, purchasing and configuring phone numbers, creating AI assistants with custom instructions, managing cloud storage buckets, scraping and embedding website content, and handling integration secrets. The server exists as both a local implementation and a remotely hosted version, allowing developers to integrate real-world communication infrastructure directly into AI applications.
Related MCP Servers
- AlicenseCqualityDmaintenanceA starter template for building Model Context Protocol servers that can be integrated with Cursor or Claude Desktop, allowing developers to create custom tools and extensions for AI assistants.114ISC
- AlicenseAqualityDmaintenanceA template for building Model Context Protocol servers that allow AI assistants to interact with custom data and services through queryable resources and specialized tools.6MIT
- FlicenseBqualityDmaintenanceA starter template for building Model Context Protocol servers that can integrate AI assistants with custom tools, resource providers, and prompt templates.181-
- FlicenseCqualityDmaintenanceA starter template for building Model Context Protocol servers that integrate with AI assistants like Claude and Cursor, providing custom tools, resource providers, and prompt templates.2-