MCP Server Template
The MCP Server Template allows you to create and customize a Model Context Protocol (MCP) server for integration with clients like Cursor or Claude Desktop.
Build Custom MCP Servers: Create tailored MCP implementations using TypeScript
Define Custom Tools: Implement and configure tools with Zod schemas for parameter validation
Sample Implementation: Includes a basic
sample-toolthat accepts string inputClient Integration: Easily connects with MCP clients like Cursor and Claude Desktop
Extensible Structure: Modify
index.tsto add more tools or customize functionalityDeployment Ready: Compile and deploy via
/build/index.js
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 Template show me how to create a new tool for Claude Desktop"
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 Template 🛠️
A starter template for building your own Model Context Protocol (MCP) server. This template provides the basic structure and setup needed to create custom MCPs that can be used with Cursor or Claude Desktop.
Features
Basic MCP server setup with TypeScript
Sample tool implementation
Ready-to-use project structure
Built with @modelcontextprotocol/sdk
Related MCP server: Python MCP Server Template
Project Structure
mcp-server-template/
├── index.ts # Main server implementation
├── package.json # Project dependencies
├── tsconfig.json # TypeScript configuration
└── build/ # Compiled JavaScript outputGetting Started
Clone this template:
git clone [your-repo-url] my-mcp-server
cd my-mcp-serverInstall dependencies:
pnpm installBuild the project:
pnpm run buildThis will generate the /build/index.js file - your compiled MCP server script.
Using with Cursor
Go to Cursor Settings -> MCP -> Add new MCP server
Configure your MCP:
Name: [choose your own name]
Type: command
Command:
node ABSOLUTE_PATH_TO_MCP_SERVER/build/index.js
Using with Claude Desktop
Add the following MCP config to your Claude Desktop configuration:
{
"mcpServers": {
"your-mcp-name": {
"command": "node",
"args": ["ABSOLUTE_PATH_TO_MCP_SERVER/build/index.js"]
}
}
}Development
The template includes a sample tool implementation in index.ts. To create your own MCP:
Modify the server configuration in
index.ts:
const server = new McpServer({
name: "your-mcp-name",
version: "0.0.1",
});Define your custom tools using the
server.tool()method:
server.tool(
"your-tool-name",
"Your tool description",
{
// Define your tool's parameters using Zod schema
parameter: z.string().describe("Parameter description"),
},
async ({ parameter }) => {
// Implement your tool's logic here
return {
content: [
{
type: "text",
text: "Your tool's response",
},
],
};
}
);Build and test your implementation:
npm run buildContributing
Feel free to submit issues and enhancement requests!
License
MIT
Available Tools
1 toolsample-toolC
A sample tool for demonstration purposes
Inputs: input (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to confuse it with. The single tool's purpose is clearly distinct by default in this minimal set.
The tool name 'sample-tool' uses a consistent hyphenated noun pattern, and with only one tool, there is no inconsistency to evaluate. The naming is straightforward and follows a simple convention.
A single tool is too few for most practical server purposes, as it severely limits functionality and scope. This feels thin and inadequate for handling any meaningful domain or workflow beyond basic demonstration.
The server is severely incomplete, with only a sample tool that lacks any clear domain or operational coverage. There are obvious gaps, as no CRUD, lifecycle, or specific functionality is provided, making it impossible for agents to perform useful 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
- FlicenseNot gradedqualityDmaintenanceA starter template for building Model Context Protocol (MCP) servers, enabling developers to create and add custom tools that can be integrated with Claude Desktop.2-
- AlicenseDqualityDmaintenanceA template repository for creating custom Model Context Protocol (MCP) servers in Python that can be integrated with applications like Claude Desktop or Cursor.36MIT
- FlicenseBqualityDmaintenanceA starter template for building Model Context Protocol servers that can integrate AI assistants with custom tools, resource providers, and prompt templates.187 npm1-
- 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.25 npm-