Skip to main content
Glama
Cafeteria MCP

Cafeteria MCP

Cafeteria MCP

Configurable MCP server for cafeteria menu lookup.

Deploy to Render

The server exposes a single MCP tool, get_cafeteria_menu, and supports stdio plus HTTP/SSE transports.

Configuration

Set these environment variables in your runtime or hosting provider:

CAFETERIA_API_URL=<form-post-api-url>
CAFETERIA_CAMPUS=<campus-code>
CAFETERIA_SEQ=<cafeteria-sequence>
CAFETERIA_ORIGIN=<optional-origin-header>
CAFETERIA_SKIP_TLS_VERIFY=false
MCP_TRANSPORT=http

CAFETERIA_ORIGIN is optional. When omitted, the origin is derived from CAFETERIA_API_URL. The upstream request is sent as POST with query parameters and Content-Length: 0. Set CAFETERIA_SKIP_TLS_VERIFY=true only when the upstream cafeteria API requires curl-style -k behavior.

Related MCP server: munich-mensa-mcp

Tool

get_cafeteria_menu

  • ymd: lookup date, YYYYMMDD or YYYY-MM-DD. Defaults to today in Asia/Seoul.

  • mealType: LN for lunch, DN for dinner.

Local stdio

npm start

MCP client example:

{
  "mcpServers": {
    "cafeteria": {
      "command": "node",
      "args": [
        "/absolute/path/to/src/server.mjs"
      ]
    }
  }
}

HTTP/SSE

MCP_TRANSPORT=http PORT=3333 npm start
  • Health check: GET http://127.0.0.1:3333/health

  • MCP SSE: GET http://127.0.0.1:3333/sse

  • MCP SSE message post: POST http://127.0.0.1:3333/messages?sessionId=...

  • MCP JSON-RPC test endpoint: POST http://127.0.0.1:3333/mcp

Hosting environments that provide PORT automatically run the HTTP/SSE transport.

Render

Deploy the repository with the included render.yaml Blueprint.

After deployment, set the required secret environment variables in Render. The public MCP SSE URL will be:

https://<render-service-name>.onrender.com/sse

See outputs/render-sse-mcp.md for a short registration note.

Supabase Probe

This repository also includes a Supabase Edge Function probe at supabase/functions/cafeteria-probe. Use it before porting the MCP server to confirm whether the Supabase runtime can reach the cafeteria API.

Required Supabase secrets:

CAFETERIA_API_URL
CAFETERIA_CAMPUS
CAFETERIA_SEQ
CAFETERIA_ORIGIN

Probe URLs after deployment:

https://<project-ref>.functions.supabase.co/cafeteria-probe?target=google
https://<project-ref>.functions.supabase.co/cafeteria-probe?target=cafeteria&ymd=20260608&mealType=LN

Supabase MCP

The Supabase Edge Function MCP endpoint is available at:

https://<project-ref>.functions.supabase.co/cafeteria-mcp

It supports MCP JSON-RPC methods including initialize, tools/list, and tools/call.

Tests

npm run test:sse
npm run test:mcp
npm run test:api -- 20260608 LN

test:api requires the environment variables above.

Available Tools

1 tool
get_cafeteria_menuA

환경변수로 설정된 식당 API에서 메뉴를 조회합니다.

Inputs: ymd, mealType.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 1 tool

    Disambiguation5/5

    The server has only one tool, so there is no ambiguity or risk of confusing it with others. Its purpose is clearly described as retrieving the cafeteria menu.

    Naming Consistency5/5

    The single tool name follows a clear verb_noun pattern (get_cafeteria_menu), which is standard and unambiguous. With only one tool, there is no inconsistency.

    Tool Count3/5

    The server has only one tool, which feels thin and borderline for a general-purpose server. However, it may be acceptable for a narrowly-scoped cafeteria menu fetcher, though it limits broader utility.

    Completeness4/5

    The tool covers the core use case of retrieving the cafeteria menu. However, it lacks any parameters for specifying a date or restaurant, and there is no backup or additional features, making it somewhat limited but not severely incomplete.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers