my-mcp-server
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., "@my-mcp-server say hello to John"
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 MCP (Model Context Protocol) servers in TypeScript
What You Get
A working MCP server with an example
hellotoolTypeScript with ES modules
Testing with Vitest
Linting (ESLint) and formatting (Prettier)
CI pipeline and npm publishing workflow
VS Code, Claude Desktop, and Cursor configuration examples
┌─────────────────┐ ┌────────────┐ ┌──────────────────┐
│ AI Assistant │────▶│ MCP Client │────▶│ Your MCP Server │
│ (Copilot/Claude) │◀────│ │◀────│ │
└─────────────────┘ └────────────┘ └──────────────────┘Related MCP server: MCP Server Starter (TypeScript)
Quick Start
1. Create your project
npx -y degit matracey/mcp-server-template my-mcp-server
cd my-mcp-server
npm install2. Customize
Update
name,description, andbininpackage.jsonReplace the example
hellotool insrc/server.tswith your own toolsUpdate the server name/version in
src/server.ts
3. Build and test
npm run build
npm test4. Run locally
npm run dev # Run with auto-restart on file changes
npm start # Run the built versionAdding Tools
Edit src/server.ts and register a new tool:
server.tool(
'my_tool',
'Description of what this tool does.',
{
param: z.string().describe('Parameter description'),
},
async ({ param }) => {
return {
content: [{ type: 'text' as const, text: `Result: ${param}` }],
}
}
)The template includes an example hello tool to demonstrate the pattern.
Client Configuration
Once published (or running locally), configure your AI client:
VS Code (GitHub Copilot)
Add to .vscode/mcp.json:
{
"servers": {
"my-server": {
"type": "stdio",
"command": "npx",
"args": ["-y", "my-mcp-server"]
}
}
}Claude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"my-server": {
"command": "npx",
"args": ["-y", "my-mcp-server"]
}
}
}Cursor
Add to .cursor/mcp.json:
{
"mcpServers": {
"my-server": {
"command": "npx",
"args": ["-y", "my-mcp-server"]
}
}
}Replace
my-mcp-serverwith your published package name.
Project Structure
src/
├── index.ts # Entry point — stdio transport setup
├── server.ts # MCP server & tool definitions
├── __tests__/ # Tests (vitest)
└── data/ # Static data (if needed)
scripts/ # Dev-time scriptsDevelopment
Prerequisites
Node.js >= 20
npm
Commands
npm run build # TypeScript compilation
npm test # Run tests
npm run test:watch # Watch mode
npm run test:coverage # With coverage report
npm run dev # Run with auto-restart on changes
npm run validate # Run all CI checks (format, lint, build, test)Contributing
Contributions are welcome! Please see CONTRIBUTING.md for guidelines.
License
MIT — see LICENSE for details.
Available Tools
1 toolhelloB
A simple greeting tool that returns a hello message.
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 1 tool
With only one tool, there is no possibility of confusion or overlap between tools, as there are no other tools to disambiguate from. The tool's purpose is clearly distinct by default in this minimal set.
A single tool inherently has perfect naming consistency, as there are no other tool names to compare against or create patterns with. The name 'hello' is straightforward and follows a simple verb-like convention without deviation.
A single tool is generally too few for most server purposes, as it offers very limited functionality and scope, making it feel thin and inadequate for handling typical tasks or workflows in a domain. This server appears to be a trivial example rather than a practical toolset.
The server's purpose is unclear from the single tool, but for any inferred domain (e.g., greeting or basic interaction), the surface is severely incomplete—it lacks any CRUD operations, lifecycle coverage, or meaningful workflows, making it impossible for agents to perform substantive tasks.
Maintenance
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
MCP server for building and testing AI agents with multi-model experimentation and insights.
Kickstart development with a customizable TypeScript template featuring sample tools for greeting,…
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
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.21 npm-
- AlicenseNot gradedqualityDmaintenanceA minimal, production-ready TypeScript starter template for building Model Context Protocol (MCP) servers with auto-loading architecture for tools, resources, and prompts. Provides boilerplate code, generators, and examples to quickly create MCP servers that can connect AI applications to any data source or tool.MIT
- FlicenseAqualityDmaintenanceA starter template for building MCP (Model Context Protocol) servers with TypeScript support. Provides a clean foundation with example tools, resources, and prompts for creating custom integrations with Claude, Cursor, or other MCP-compatible AI assistants.28 npm-
- FlicenseCqualityDmaintenanceA starter template for building MCP (Model Context Protocol) servers that integrate with Claude, Cursor, or other MCP-compatible AI assistants. Provides a clean foundation with TypeScript support, example tool implementation, and installation scripts for quick customization.26 npm-