Skip to main content
Glama
Sign In
Chop MCP TypeScript

Chop MCP TypeScript

by LucasDelgado
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Chop MCP TypeScript

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.

Características

  • 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

Requisitos Previos

  • Node.js (versión recomendada: >= 16)

  • npm o yarn

  • TypeScript

  1. Instala las dependencias:

npm install

Configuración

El 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

Uso

Para iniciar el servidor MCP:

npm start

Herramientas Disponibles

obtener-setup

Esta 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 JSON

Estructura del Proyecto

  • main.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

Scripts Disponibles

  • npm start: Inicia el servidor MCP

  • npm run build: Compila el proyecto TypeScript

Desarrollo

Para contribuir al proyecto:

  1. Asegúrate de tener todas las dependencias instaladas

  2. Realiza tus cambios en una nueva rama

  3. Ejecuta las pruebas (cuando estén implementadas)

  4. Envía un pull request

Add to client LLM

  • 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

Available Tools

1 tool
obtener-setupD

Inputs: setup_id (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    D1.5/5.0

    Scored across 1 tool

    Disambiguation5/5

    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.

    Naming Consistency3/5

    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.

    Tool Count2/5

    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.

    Completeness1/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers

    • ConnectWise API Gateway MCP

      jasondsmith72
      F
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server that provides a comprehensive interface for interacting with the ConnectWise Manage API, simplifying API discovery, execution, and management for both developers and AI assistants.
      12 npm
      19
      -

    • OpenAPI MCP Server

      rahgadda
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol Server that enables LLMs to interact with and execute REST API calls through natural language prompts, supporting GET/PUT/POST/PATCH operations on configured APIs.
      6
      Apache 2.0

    • MCP REST API Server

      vinaykp
      F
      license
      Not graded
      quality
      D
      maintenance
      A server implementation of the Model Context Protocol (MCP) that provides REST API endpoints for managing and interacting with MCP resources.
      -

    • OpenAPI MCP Server

      oneWalker
      A
      license
      Not graded
      quality
      D
      maintenance
      A server that implements the Model Context Protocol (MCP) with StreamableHTTP transport, enabling standardized interaction with model services through a RESTful API interface.
      376 npm
      2
      MIT