MCP Server Boilerplate
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 to my server"
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 Server Boilerplate
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 toolsjson_extractA
Extract specific data using paths, filters, patterns, or slices from JSON files. Always use this tool when you need to retrieve particular values, filter arrays/objects by conditions, search for patterns, or slice data. Ideal for targeted data extraction, data transformation, and focused analysis of specific JSON elements.
Inputs: file_path (required), path, filter, pattern, +5 more.
json_readA
Read and analyze JSON. Always use this tool to explore JSON structure, understand data schema, or get high-level overviews of large JSON. Use this for initial data exploration or when you need to understand the shape and types of data before extracting specific values.
Inputs: file_path (required), path, max_depth, max_keys, +4 more.
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 clearly distinct purposes with no overlap. json_extract is for targeted data extraction and transformation, while json_read is for initial exploration and schema understanding. The descriptions explicitly guide when to use each tool, eliminating any ambiguity.
Both tools follow a consistent verb_noun pattern with 'json_' prefix and descriptive actions (extract, read). The naming is perfectly uniform and predictable across the tool set.
With only 2 tools, the server feels too thin for a general-purpose JSON handling domain. While the tools are well-defined, a complete JSON manipulation surface would typically include additional operations like validation, transformation, or writing capabilities. The count is insufficient for comprehensive JSON workflows.
There are significant gaps in the JSON manipulation surface. The server only provides read/extract capabilities with no tools for creating, updating, validating, or writing JSON data. This creates dead ends for agents needing to modify or generate JSON, making it incomplete for common JSON-related tasks.
Maintenance
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
A simple Typescript MCP server built using the official MCP Typescript SDK and smithery/cli. This…
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
Augments MCP Server - A comprehensive framework documentation provider for Claude Code
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA starter template for building MCP servers with TypeScript support, example tools, and automated installation scripts for Claude Desktop, Cursor, and other MCP-compatible AI assistants. Provides a foundation for creating custom tools, resource providers, and prompt templates.-
- FlicenseBqualityDmaintenanceA starter template for building custom MCP servers that can integrate with Claude Desktop, Cursor, and other AI assistants. Provides example tools, TypeScript support, and automated publishing workflows to help developers quickly create their own MCP integrations.1-
- FlicenseAqualityDmaintenanceA starter template for building custom MCP servers that can integrate with Claude Desktop, Cursor, and other AI assistants. Provides example tools, TypeScript support, and automated publishing workflows to help developers quickly create their own MCP servers.7-
- FlicenseCqualityDmaintenanceA starter template for building custom MCP (Model Context Protocol) servers that can integrate with Claude, Cursor, or other MCP-compatible AI assistants. Provides a clean foundation with TypeScript support, example implementations, and installation scripts for quickly creating custom tools, resources, and prompts.2-