Used for making HTTP requests to the Chop Setup API, enabling retrieval of setup information by ID from the local REST API.
Runtime environment required for the MCP server, with version 16 or higher recommended for optimal compatibility.
Provides type safety and structure for the implementation, with strict typing for the setup information data models.
Provides schema validation for the setup data retrieved from the Chop system, ensuring type safety and data integrity.
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., "@Chop MCP TypeScript get setup details for ID 12345"
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.
Este proyecto implementa un servidor MCP (Model Context Protocol) para interactuar con el sistema de Setups de Chop. Proporciona una interfaz para obtener información de setups a través de una API REST.
Implementación del Model Context Protocol (MCP)
Herramienta para obtener información de setups por ID
Comunicación con API REST local
Implementado en TypeScript con tipado estricto
Related MCP server: OpenAPI MCP Server
Node.js (versión recomendada: >= 16)
npm o yarn
TypeScript
Instala las dependencias:
npm installEl proyecto utiliza TypeScript y está configurado con tsconfig.json. Las principales dependencias incluyen:
@modelcontextprotocol/sdk: SDK para implementación de MCP
axios: Cliente HTTP para realizar peticiones
zod: Validación de esquemas
TypeScript y herramientas de desarrollo relacionadas
Para iniciar el servidor MCP:
npm startEsta herramienta permite obtener información detallada de un setup específico.
Parámetros:
setup_id (number): El ID del setup a consultar
Ejemplo de uso:
// La herramienta se conecta a http://localhost:8080/backoffice/setup/{setup_id}
// y devuelve la información del setup en formato JSONmain.ts: Punto de entrada de la aplicación y configuración del servidor MCP
types.ts: Definiciones de tipos TypeScript
package.json: Configuración del proyecto y dependencias
tsconfig.json: Configuración de TypeScript
npm start: Inicia el servidor MCP
npm run build: Compila el proyecto TypeScript
Para contribuir al proyecto:
Asegúrate de tener todas las dependencias instaladas
Realiza tus cambios en una nueva rama
Ejecuta las pruebas (cuando estén implementadas)
Envía un pull request
Agregarlo al client modo Dev
"ChopSetup-ts": {
"command": "npx",
"args": [
"-y",
"tsx",
"{your}/chop-mcp-ts/main.ts"
]
}Correr el debug
npx -y @modelcontextprotocol/inspector npx -y tsx main.ts: Compila el proyecto TypeScript
| Name | Required | Description | Default |
|---|---|---|---|
| setup_id | Yes | El id del setup a obtener |
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.
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.
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.
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.
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.
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.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
obtener-setupScored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to confuse it with. The tool's purpose, while not described, is inherently distinct by being the sole option.
With a single tool, consistency cannot be assessed across multiple tools, but the tool name 'obtener-setup' uses a Spanish verb ('obtener') with a hyphenated noun, which is readable but lacks a pattern to evaluate against other tools. This places it in the middle of the scale due to the inability to judge consistency.
One tool is generally too few for most server purposes, as it suggests a very limited or trivial scope, making it difficult to perform meaningful operations. For a server named 'Chop MCP TypeScript', which might imply code or development tasks, a single tool feels insufficient and mismatched.
The server has only one tool with no description, making it impossible to infer the domain or assess coverage. With no clear purpose or additional tools, the surface is severely incomplete and will likely cause agent failures due to lack of functionality.
Model Context Protocol server for Studex tools, notifications, and profile integrations
A Model Context Protocol (MCP) server for Selise Blocks Cloud integration
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
A Model Context Protocol server for Wix AI tools
