This MCP Server Template enables you to build and test Model Context Protocol (MCP) compatible servers with the following capabilities:
Build custom MCP servers: Create TypeScript-based servers that adhere to the MCP protocol
Create and manage tools: Define tools with specific input schemas and handlers (like the included
example-tool)Process data: Handle MCP protocol requirements for tool registration, validation, processing, and formatting
Development features: Leverage TypeScript support, dependency injection, and service-based architecture
Testing utilities: Debug using the TestClient, MCP Inspector for visual debugging, and direct Cursor IDE integration
This template provides everything needed to quickly develop, test, and implement MCP-compatible tools and services.
Enables local testing and linking of the MCP server as an npm package, allowing for development and testing workflows.
Provides full TypeScript support for building MCP-compatible servers with type safety and proper tooling.
Integrated testing framework for writing and running tests for MCP tools and services.
Click on "Install 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 Templateshow me how to add a new tool to the template"
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 template for creating Model Context Protocol (MCP) servers in TypeScript. This template provides a solid foundation for building MCP-compatible servers with proper tooling, type safety, and best practices.
Features
π Full TypeScript support
ποΈ Container-based dependency injection
π¦ Service-based architecture with DataProcessor interface
π οΈ Example tool implementation with tests
π§ͺ Vitest testing framework
π Type definitions
π MCP SDK integration
Related MCP server: MCP Server Starter
Getting Started
Development
Install dependencies:
npm installStart the development server with hot reload:
npm run devBuild the project:
npm run buildRun tests:
npm testStart the production server:
npm start
Project Structure
src/
βββ index.ts # Entry point
βββ interfaces/ # Interface definitions
β βββ tool.ts # DataProcessor interface
βββ tools/ # Tool implementations
βββ example.ts # Example toolCreating Tools
Export your tool and handlers following the example in
src/tools/example.ts:// In your-tool.ts export const YOUR_TOOLS = [ { name: "your-tool-name", description: "Your tool description", parameters: { // Your tool parameters schema }, }, ]; export const YOUR_HANDLERS = { "your-tool-name": async (request) => { // Your tool handler implementation return { toolResult: { content: [{ type: "text", text: "Result" }], }, }; }, };Register your tool in the
ALL_TOOLSandALL_HANDLERSconstants insrc/index.ts:// In src/index.ts import { YOUR_TOOLS, YOUR_HANDLERS } from "./tools/your-tool.js"; // Combine all tools const ALL_TOOLS = [...EXAMPLE_TOOLS, ...YOUR_TOOLS]; const ALL_HANDLERS = { ...EXAMPLE_HANDLERS, ...YOUR_HANDLERS };
The server will automatically:
List your tool in the available tools
Handle input validation
Process requests to your tool
Format responses according to the MCP protocol
Testing
The template includes a built-in TestClient for local testing and the MCP Inspector for visual debugging.
Using TestClient
The TestClient provides a simple way to test your tools:
import { TestClient } from "./utils/TestClient";
describe("YourTool", () => {
const client = new TestClient();
it("should process data correctly", async () => {
await client.assertToolCall(
"your-tool-name",
{ input: "test" },
(result) => {
expect(result.toolResult.content).toBeDefined();
}
);
});
});Using MCP Inspector
The template includes the MCP Inspector for visual debugging of your tools:
Start the inspector:
npx @modelcontextprotocol/inspector node dist/index.jsOpen the inspector UI at http://localhost:5173
The inspector provides:
Visual interface for testing tools
Real-time request/response monitoring
Tool metadata inspection
Interactive testing environment
Local Testing with Cursor
To test your MCP server locally with Cursor:
Build and link the package:
npm run build npm run linkVerify the binary works:
npx example-mcp-toolAdd the server to Cursor:
Open Cursor settings
Navigate to the Features tab
Scroll down to MCP Servers section
Click "Add Server"
Select "Command" type
Give it a name (e.g., "Local Example Tool")
Enter the command:
npx example-mcp-toolClick Confirm
Verify the server starts correctly in Cursor by checking the MCP Servers section shows your server as running.
Note: If you make changes to your code, remember to rebuild and relink:
npm run build
npm run linkWhen you're done testing, you can unlink the package:
npm run unlinkThis will remove the global symlink created during development.
Resources
Looking for Admin?
Admins can modify the Dockerfile, update the server description, and track usage metrics. If you are the server author, to access the admin panel.