Skip to main content
Glama
enesjakozh
MatthewDailey

MCP Starter Server

by MatthewDailey
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Servidor de inicio MCP

Una plantilla de servidor ModelContextProtocol minimalista para crear herramientas de asistentes de IA. Esta plantilla de inicio proporciona una estructura básica para crear herramientas MCP compatibles con asistentes de IA como Claude.

Características

  • Ejemplo simple de la herramienta "Hola mundo"

  • Configuración de TypeScript + esbuild

  • Herramientas de desarrollo preconfiguradas

Related MCP server: MCP Server Scaffold

Configuración para construir y ejecutar con Claude

  1. Descargue e instale la aplicación de escritorio Claude desde claude.ai/download

  2. Clonar el repositorio, instalar dependencias y compilar:

npm install
npm run build

  1. Configure Claude para usar este servidor MCP. Si este es su primer servidor MCP, ejecute lo siguiente en la raíz del proyecto:

echo '{
  "mcpServers": {
    "mcp-starter": {
      "command": "node",
      "args": ["'$PWD'/dist/index.cjs"]
    }
  }
}' > ~/Library/Application\ Support/Claude/claude_desktop_config.json

Esto debería generar una entrada en su claude_desktop_config.json como:

"mcpServers": {
  "mcp-starter": {
    "command": "node",
    "args": ["/Users/matt/code/mcp-starter/dist/index.cjs"]
  }
}

Si ya tiene servidores MCP, agregue el bloque mcp-starter a su configuración. Es importante que el args sea la ruta a <path_to_repo_on_your_machine>/mcp-starter/dist/index.cjs .

  1. Reinicie Claude Desktop.

  2. Busque el ícono del martillo con el número de herramientas disponibles en la interfaz de Claude para confirmar que el servidor está funcionando.

  3. Si todo esto funciona, deberías poder desarrollar tu servidor MCP con npm run dev y probarlo en Claude. Deberás reiniciar Claude cada vez que se reinicie el servidor MCP.

Desarrollando con Inspector

Para fines de desarrollo y depuración, puede utilizar la herramienta Inspector de MCP. El Inspector proporciona una interfaz visual para probar y supervisar las interacciones con el servidor MCP.

Visita la documentación del Inspector para obtener instrucciones de configuración detalladas.

Para realizar pruebas locales con Inspector:

npm run inspect

Para aprovechar los cambios de archivo, ejecute:

npm run watch

O ejecute tanto el observador como el inspector:

npm run dev

Publicación

¡Una vez que esté listo para distribuir su servidor, es simple!

  1. Configurar una cuenta NPM .

  2. Ejecute npm publish . Esto publicará un paquete con el nombre del proyecto en package.json

  3. Una vez publicado, otros pueden instalar el servidor con una entrada de configuración como:

"mcpServers": {
  "<your-package-name>": {
    "command": "npx",
    "args": ["<your-package-name>"]
  }
}

Herramientas disponibles

El servidor proporciona:

  • hello_tool : Una herramienta de ejemplo simple que toma un parámetro de nombre y devuelve un saludo

Creando nuevas herramientas

Para agregar nuevas herramientas:

  1. Defina el esquema de herramientas en index.ts

  2. Agreguelo a la matriz de herramientas en el controlador ListToolsRequestSchema

  3. Agregue la implementación en el controlador CallToolRequestSchema

Vea la implementación hello_tool como ejemplo.

Available Tools

1 tool
hello_toolD

Hello tool

ParametersJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the person to greet

TDQS

D1.7/5.0
Behavior1/5

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. 'Hello tool' discloses nothing about side effects, return values, or operational behavior, leaving the agent completely uninformed beyond the tool's name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short, but this is under-specification rather than effective conciseness. It is a two-word tautology that provides no informative structure or front-loaded value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

While the tool is simple and the schema fully documents its one parameter, the description still fails to state the tool's purpose or expected behavior. An agent may infer from the name and parameter that it greets a person, but the description itself is incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%: the only parameter, 'name', is described as 'The name of the person to greet'. This meets the baseline where the schema does the heavy lifting. The description itself adds no additional parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Hello tool' simply restates the tool name without a verb, resource, or outcome. It does not specify that the tool greets a person or what action it performs, and it fails to distinguish itself from siblings like plan_trip or search_location.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool or when to prefer an alternative. There are no exclusions, conditions, or context clues to help an agent decide between hello_tool and its siblings.

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. 1 tool updatev1.0.0
    • First observedhello_tool
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

C2.2/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools, making it perfectly clear which tool to use for any task within this server's scope.

Naming Consistency5/5

The single tool name 'hello_tool' follows a consistent verb_noun pattern, and with no other tools to compare, there is no inconsistency in naming conventions.

Tool Count2/5

One tool is generally too few for a server's purpose unless it is extremely trivial, which 'hello_tool' suggests. This feels thin and under-scoped for a typical MCP server, indicating a mismatch in tool count appropriateness.

Completeness1/5

With only a 'hello_tool', the server lacks any meaningful coverage of a domain. It is severely incomplete, as there are no operations for CRUD, lifecycle management, or any substantive workflows, making it inadequate for agent-driven tasks.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • MCP Server Scaffold

    vjouenne76
    F
    license
    B
    quality
    D
    maintenance
    A basic starter project for building Model Context Protocol (MCP) servers that enables standardized interactions between AI systems and various data sources through secure, controlled tool implementations.
    2
    -

  • Hello World MCP FastAPI

    bankszach
    F
    license
    Not graded
    quality
    D
    maintenance
    A minimal Model Context Protocol server built with FastAPI that provides a basic "Hello World" resource and tool. Serves as a starting point for building and validating MCP client integrations with richer resources and tools.
    -

  • mcp-base

    sesopenko
    A
    license
    Not graded
    quality
    D
    maintenance
    A bare-bones FastMCP server template designed to serve as a starting point for building custom Model Context Protocol servers. It provides a foundational structure for implementing tools over HTTP and includes a built-in health check utility.
    GPL 3.0

Appeared in Searches