MCP Server Template
Plantilla de servidor MCP
Una plantilla para crear servidores de Protocolo de Contexto de Modelo (MCP) en TypeScript. Esta plantilla proporciona una base sólida para construir servidores compatibles con MCP con las herramientas adecuadas, seguridad de tipos y las mejores prácticas.
Características
🚀 Compatibilidad total con TypeScript
🏗️ Inyección de dependencia basada en contenedores
📦 Arquitectura basada en servicios con interfaz DataProcessor
🛠️ Ejemplo de implementación de la herramienta con pruebas
Marco de pruebas Vitest
📝 Definiciones de tipos
🔌 Integración del SDK de MCP
Related MCP server: MCP Server Template
Empezando
Desarrollo
Instalar dependencias:
npm installInicie el servidor de desarrollo con recarga en caliente:
npm run devConstruir el proyecto:
npm run buildEjecutar pruebas:
npm testInicie el servidor de producción:
npm start
Estructura del proyecto
src/
├── index.ts # Entry point
├── interfaces/ # Interface definitions
│ └── tool.ts # DataProcessor interface
└── tools/ # Tool implementations
└── example.ts # Example toolCreación de herramientas
Exporte su herramienta y controladores siguiendo el ejemplo en
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" }], }, }; }, };Registre su herramienta en las constantes
ALL_TOOLSyALL_HANDLERSensrc/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 };
El servidor automáticamente:
Enumere su herramienta en las herramientas disponibles
Manejar la validación de entrada
Procesar solicitudes a su herramienta
Formatear respuestas según el protocolo MCP
Pruebas
La plantilla incluye un TestClient integrado para pruebas locales y el MCP Inspector para depuración visual.
Uso de TestClient
TestClient proporciona una forma sencilla de probar sus herramientas:
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();
}
);
});
});Uso del inspector MCP
La plantilla incluye el Inspector MCP para la depuración visual de sus herramientas:
Iniciar el inspector:
npx @modelcontextprotocol/inspector node dist/index.jsAbra la interfaz de usuario del inspector en http://localhost:5173
El inspector proporciona:
Interfaz visual para herramientas de prueba
Monitoreo de solicitudes y respuestas en tiempo real
Inspección de metadatos de la herramienta
Entorno de pruebas interactivo
Pruebas locales con cursor
Para probar su servidor MCP localmente con Cursor:
Construya y vincule el paquete:
npm run build npm run linkVerificar que el binario funciona:
npx example-mcp-toolAñade el servidor al Cursor:
Abrir la configuración del cursor
Vaya a la pestaña Características
Desplácese hacia abajo hasta la sección Servidores MCP
Haga clic en "Agregar servidor"
Seleccione el tipo "Comando"
Asígnele un nombre (por ejemplo, "Herramienta de ejemplo local")
Ingrese el comando:
npx example-mcp-toolHaga clic en Confirmar
Verifique que el servidor se inicie correctamente en Cursor verificando que la sección Servidores MCP muestre que su servidor está en ejecución.
Nota: Si realiza cambios en su código, recuerde reconstruirlo y volver a vincularlo:
npm run build
npm run linkCuando hayas terminado de probar, puedes desvincular el paquete:
npm run unlinkEsto eliminará el enlace simbólico global creado durante el desarrollo.
Available Tools
1 toolexample-toolC
An example tool that processes input data
| Name | Required | Description | Default |
|---|---|---|---|
| input | Yes | Input string to process |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'processes input data', which implies some action but doesn't reveal behavioral traits like whether it's read-only, destructive, requires authentication, has side effects, or rate limits. This leaves significant gaps in understanding how the tool behaves.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence with no wasted words, making it appropriately concise. However, it's front-loaded with the basic purpose but lacks structure or additional details that could enhance clarity, keeping it simple but under-specified.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (1 parameter, no output schema, no annotations), the description is incomplete. It doesn't explain what 'processes' means, the expected output, or behavioral context, leaving the agent with insufficient information to use the tool effectively despite the straightforward schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description adds no specific meaning about the 'input' parameter beyond what the schema provides, which has 100% coverage and describes it as 'Input string to process'. With high schema coverage, the baseline is 3, as the schema adequately documents the parameter, and the description doesn't compensate or add further semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states the tool 'processes input data', which provides a basic purpose but is vague about what 'processes' entails. It doesn't specify the type of processing or outcome, and with no sibling tools, differentiation isn't needed. This is a minimal viable description that communicates a general function without specifics.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description offers no guidance on when to use this tool, such as context, prerequisites, or alternatives. With no sibling tools, it doesn't need to distinguish from others, but it lacks any usage instructions or scenarios, leaving the agent without direction on appropriate application.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- First observed
example-tool
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 compare it against. The single tool's purpose is clearly defined, eliminating any ambiguity in tool selection.
Since there is only one tool, naming consistency is inherently perfect—there are no other tools to create inconsistency. The tool name 'example-tool' follows a simple, clear pattern without any conflicting conventions to evaluate.
A single tool is generally too few for a server's purpose, as it limits functionality and suggests an incomplete or trivial implementation. For a server named 'MCP Server Template', one tool feels insufficient to demonstrate a coherent set of capabilities, making it borderline inadequate.
The server's purpose is unclear from the name 'MCP Server Template', but with only one generic tool ('example-tool'), there are significant gaps in coverage. It lacks any CRUD operations, lifecycle management, or domain-specific functions, making it severely incomplete for any practical application.
Maintenance
Related MCP Connectors
Kickstart development with a customizable TypeScript template featuring sample tools for greeting,…
A Model Context Protocol server for Wix AI tools
A simple Typescript MCP server built using the official MCP Typescript SDK and smithery/cli. This…
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Related MCP Servers
- AlicenseCqualityDmaintenanceA production-ready template for creating Model Context Protocol servers with TypeScript, providing tools for efficient testing, development, and deployment.137 npm47MIT
- AlicenseBqualityDmaintenanceA template for creating Model Context Protocol (MCP) servers in TypeScript, offering features like container-based dependency injection, a service-based architecture, and integration with the LLM CLI for architectural design feedback through natural language.19 npm7ISC
- AlicenseCqualityDmaintenanceA TypeScript-based template for building Model Context Protocol servers, featuring fast testing, automated version management, and a clean structure for MCP tool implementations.137 npm4MIT
- FlicenseNot gradedqualityDmaintenanceA template repository for building Model Context Protocol (MCP) servers with TypeScript, featuring full TypeScript support, testing setup, CI/CD pipelines, and modular architecture for easy extension.7 npm-