Skip to main content
Glama
zhangzhefang-github

MCP Add Server

Agregar servidor MCP

Un servidor de Protocolo de Contexto de Modelo (MCP) minimalista que proporciona una herramienta sencilla add(a, b) . Este proyecto sirve como ejemplo básico de la implementación de un servidor MCP.

Características

  • Implementa un servidor compatible con el Protocolo de Contexto de Modelo.

  • Proporciona una única herramienta: add(a, b) que devuelve la suma de dos números.

Related MCP server: Basic Math MCP Server

Prerrequisitos

  • Node.js (versión 18.xx o superior recomendada)

  • npm (viene con Node.js)

Instalación

  1. Clonar el repositorio:

    git clone <你的仓库URL> # 当你推送到 GitHub 后,替换这里的 URL
    cd mcp-add-server
  2. Instalar dependencias:

    npm install

Uso

Hay varias formas de ejecutar mcp-add-server :

1. Usando npx (recomendado para la mayoría de los usuarios):

Si tiene Node.js y npm instalados, puede ejecutar el servidor directamente sin clonar ni instalar globalmente:

npx mcp-add-server

Este comando descargará la última versión de mcp-add-server (si aún no está en caché) y la ejecutará.

2. Ejecución desde un repositorio clonado:

Después de clonar el repositorio e instalar las dependencias (ver Instalación ):

npm start

Esto utiliza el script start definido en package.json .

3. Instalación global (para uso frecuente o desarrollo):

Puede instalar el paquete globalmente:

npm install -g .  # From the cloned repository directory
# or once published to npm:
# npm install -g mcp-add-server

Luego puedes ejecutarlo desde cualquier directorio:

mcp-add-server

4. Enlace local para desarrollo: En el directorio raíz del proyecto, ejecute npm link . Esto hará que el comando mcp-add-server esté disponible globalmente, apuntando a los archivos locales del proyecto.

# In project directory
npm link

# Then, in any directory:
mcp-add-server

Una vez que el servidor esté en funcionamiento (independientemente del método utilizado), estará disponible para los clientes de MCP.

Ejemplo de llamada a herramienta (conceptual)

Un cliente MCP podría llamar a la herramienta add de esta manera (los detalles dependen de la implementación del cliente):

{
  "tool_name": "add",
  "arguments": {
    "a": 5,
    "b": 3
  }
}

El servidor respondería con:

{
  "result": 8
}

Ejecución de pruebas

(Cuando se agreguen pruebas, describa aquí cómo ejecutarlas)

npm test

(Actualmente, npm test mostrará el mensaje "Error: no se especificó ninguna prueba". Actualice el script test en package.json cuando se agreguen pruebas).

Estructura del proyecto

mcp-add-server/
├── .git/               # Git directory
├── .gitignore          # Specifies intentionally untracked files that Git should ignore
├── .cursor/            # Cursor specific files (if any)
├── node_modules/       # Project dependencies
├── src/                # Source code
│   └── server.js       # Main server logic
├── bin.js              # Executable for the server
├── LICENSE             # Project license
├── package-lock.json   # Records exact versions of dependencies
├── package.json        # Project metadata and dependencies
└── README.md           # This file

Contribuyendo

¡Agradecemos sus contribuciones! No dude en enviar una solicitud de incorporación de cambios o abrir un problema.

Licencia

Este proyecto está licenciado bajo la licencia MIT .

Available Tools

1 tool
addD
NameRequiredDescriptionDefault
aYes第一个加数
bYes第二个加数

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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 update
    • First observedadd

TDQS

D1.7/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap with other tools. The single tool 'add' stands alone without any ambiguity in purpose.

Naming Consistency5/5

A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'add' is straightforward and follows a simple verb pattern.

Tool Count2/5

A single tool is generally too few for most server purposes, as it limits functionality and scope. Without a description, it's unclear if this minimal set is justified, but typically one tool feels thin and incomplete.

Completeness1/5

With only one tool and no description, it is impossible to assess coverage of any domain. The surface is severely incomplete, lacking any context or additional operations that might be expected for a coherent toolset.

Maintenance

ActivityInactive
ResponsivenessNo issues

Related MCP Connectors

Related MCP Servers

  • F
    license
    B
    quality
    D
    maintenance
    A simple server that provides basic mathematical operations (sum and subtraction) through the Model Context Protocol.
    2
    1
    -
  • A
    license
    Not graded
    quality
    D
    maintenance
    A minimal, production-ready MCP server with a simple addition calculator tool that demonstrates integration with the Model Context Protocol.
    5 npm
    1
    MIT
  • F
    license
    B
    quality
    Not graded
    maintenance
    A minimal Model Context Protocol server that provides a simple tool for adding two integers. It serves as a demonstration of the official Python MCP SDK and is designed for local execution via stdio.
    1
    -