Skip to main content
Glama
io.github.smlfg/chefkoch-mcp

io.github.smlfg/chefkoch-mcp

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CHEFKOCH_BASE_URLNoAPI-Basis (Test/Fake-Server)https://api.chefkoch.de

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_recipesB

Sucht Rezepte auf Chefkoch.de mit Filtern und liefert eine sortierte Trefferliste. Search Chefkoch recipes with filters; read-only.

get_recipeB

Zeigt ein Chefkoch-Rezept per ID, URL oder Suchbegriff mit auf Portionen skalierten Zutaten. Show a Chefkoch recipe; read-only.

shopping_listA

Erstellt aus mehreren Chefkoch-Rezepten eine zusammengefasste Einkaufsliste mit skalierten Mengen. Build a shopping list; read-only.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 3 tools

Disambiguation4/5

search_recipes and get_recipe are mostly distinct (discovery vs. retrieval), but get_recipe also accepts a search term, creating mild overlap with search_recipes. shopping_list is clearly separate, and the descriptions do enough to guide selection.

Naming Consistency4/5

Two of three tools follow a clear verb_noun snake_case pattern (search_recipes, get_recipe). shopping_list breaks the verb-first convention as a bare noun, a minor but noticeable deviation.

Tool Count4/5

Three tools form a tight, focused surface for a recipe lookup server: discovery, retrieval, and aggregation. Slightly thin, but each tool clearly earns its place with no filler.

Completeness3/5

The core read-only workflow (search → fetch → shopping list) is covered, but there are notable gaps: no browsing by category/cuisine, no ingredient-based search, and no way to inspect or adjust an existing shopping list. Agents can work around these but will hit dead ends for common recipe tasks.

Maintenance

ActivityMaintained
ResponsivenessSyncing