Skip to main content
Glama
deenesjakoruzh
c0dr

Canteen MCP

by c0dr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

食堂MCP

シンプルな API 統合を介して食堂のランチ メニューへのアクセスを提供するモデル コンテキスト プロトコル (MCP) サーバー。

説明

Canteen MCPは、FastMCPベースのサーバーで、食堂から毎日のランチメニューを取得するためのツールを公開しています。メニューAPIに接続し、特定の日付のメニューデータを照会するための構造化インターフェースを提供します。

Related MCP server: Strapi MCP Server

特徴

  • 特定の日付のランチメニューを入手

  • リアルタイム通信のためのhttpStreamベースのトランスポート

  • 環境ベースの構成

  • 入力検証を備えた型安全なAPI

インストール

npm install

構成

サンプル環境ファイルをコピーし、値で更新します。

cp .env.example .env

環境変数

変数

説明

例

API_URL

ランチメニューAPIのURL

https://lunch-menu-ai.vercel.app/api/v1/menu

ポート

MCP サーバーのポート

8080

終点

HTTPエンドポイント

/終点

使用法

サーバーを起動します。

npm start

利用可能なツール

ランチメニューを取得する

特定の日付のランチ メニューを取得します。

  • パラメータ:

    • date : YYYY-MM-DD形式の文字列

  • 戻り値: メニューデータを含むJSON文字列

  • 例：

    const result = await tool.execute({ date: "2024-10-05" });

発達

前提条件

  • Node.js >= 18

  • npm

開発モードで実行

npm run dev

ドッカー

イメージの構築

docker build -t canteen-mcp .

コンテナの実行

docker run -d \
  -p 8080:3000 \
  -e API_URL=your_api_url \
  -e PORT=3000 \
  -e ENDPOINT=/http \
  --name canteen-mcp \
  canteen-mcp

GitHub コンテナレジストリの使用

最新のイメージをプルします:

docker pull ghcr.io/[your-username]/canteen-mcp:latest

展開

Hetznerへの導入

  1. Hetzner サーバーに SSH で接続します。

ssh root@your-server-ip

  1. まだインストールされていない場合は Docker をインストールします。

curl -fsSL https://get.docker.com | sh

  1. docker-compose.yml ファイルを作成します。

version: '3.8'
services:
  canteen-mcp:
    image: ghcr.io/c0dr/canteen-mcp:latest
    restart: always
    ports:
      - "8080:3000"
    environment:
      - API_URL=your_api_url
      - PORT=3000
      - ENDPOINT=/http

  1. サービスを開始します:

docker-compose up -d

ライセンス

このプロジェクトは MIT ライセンスに基づいてライセンスされています - 詳細については LICENSE ファイルを参照してください。

https://github.com/punkpeye/fastmcp-boilerplateに基づいています

Available Tools

1 tool
get_lunch_menuA
Read-only

Get the lunch menu from the canteen for a specific date

ParametersJSON Schema
NameRequiredDescriptionDefault
dateYesThe date to get the menu for (YYYY-MM-DD)

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already provide readOnlyHint=true and openWorldHint=true, indicating this is a safe read operation with open-world assumptions. The description adds context about retrieving a menu for a date but does not disclose additional behavioral traits like error handling, data freshness, or format details. No contradiction with annotations is present.

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

Conciseness5/5

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

The description is a single, clear sentence that efficiently conveys the tool's purpose without any wasted words. It is appropriately sized and front-loaded, making it easy to understand quickly.

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

Completeness4/5

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

Given the tool's low complexity (one parameter, read-only, no output schema), the description is reasonably complete. It covers the main action and parameter intent, though it could benefit from mentioning the return format or potential limitations. With annotations handling safety and world assumptions, the description is adequate but not exhaustive.

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%, with the parameter 'date' fully documented in the schema (including description, pattern, and type). The description mentions 'for a specific date' but adds no extra meaning beyond what the schema provides, so it meets the baseline of 3 for high schema coverage.

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

Purpose4/5

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

The description clearly states the tool's purpose with a specific verb ('Get') and resource ('lunch menu from the canteen'), including the scope ('for a specific date'). It distinguishes what the tool does effectively, though there are no sibling tools to differentiate from, which prevents a perfect score of 5.

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

Usage Guidelines3/5

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

The description implies usage by specifying 'for a specific date', suggesting when to use it (when you need a menu for a particular date). However, it lacks explicit guidance on when not to use it or alternatives, and there are no sibling tools mentioned, so no comparison is provided.

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 observedget_lunch_menu
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

A3.5/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'get_lunch_menu' has a clear and distinct purpose that cannot be confused with any other tool in this set.

Naming Consistency5/5

Since there is only one tool, it inherently follows a consistent naming pattern. The tool name 'get_lunch_menu' uses a verb_noun structure, which is clear and predictable, though no comparison with other tools is possible.

Tool Count2/5

A single tool is too few for a server named 'Canteen MCP', which suggests a broader scope related to canteen operations. This minimal set severely limits functionality, as it only allows retrieving the lunch menu without any other operations like ordering, payment, or menu management.

Completeness1/5

The tool set is severely incomplete for a canteen domain. It only provides a 'get' operation for the lunch menu, with no coverage for creating, updating, or deleting menu items, handling orders, payments, or other typical canteen workflows, leading to significant gaps that will cause agent failures.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • OpenCTI MCP Server

    zxzinn
    A
    license
    A
    quality
    C
    maintenance
    A Model Context Protocol server that facilitates integration with OpenCTI, allowing users to query and retrieve cyber threat intelligence data via a standardized interface.
    16
    40
    MIT

  • Senechal MCP Server

    mattjoyce
    A
    license
    Not graded
    quality
    D
    maintenance
    A Model Context Protocol server that provides health data from the Senechal API to LLM applications, enabling AI assistants to access, analyze, and respond to personal health information.
    GPL 3.0

  • 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