Cookwala / MCP server and AI agents

Experimental

Cookwala for AI agents, with no server to run

An MCP server for Claude, Codex, Copilot, Cursor, Windsurf, Devin, Antigravity and any other agent. It searches and reads the recipes, dry-runs a recipe against a device, checks a temperature trace, an agent mandate or a food-rescue SMS, and it can look recipes up on fifi.cooking. It is read-only and it never starts cooking.

Install in one line

  1. Claude Code

    claude mcp add cookwala -- npx -y @cookwala/mcp
  2. Codex

    codex mcp add cookwala -- npx -y @cookwala/mcp
  3. Claude Desktop, Cursor, Windsurf, Antigravity, Gemini CLI, Copilot CLI: add this to the client's MCP configuration file.

    {
      "mcpServers": {
        "cookwala": { "command": "npx", "args": ["-y", "@cookwala/mcp"] }
      }
    }
  4. VS Code (Copilot), the Copilot cloud agent and Devin have their own file or settings page; the command is the same. Every client, with the exact file.

Needs Node 20 or later. Published on npm as @cookwala/mcp (version 0.2.0) and listed in the official MCP Registry as ai.cookwala/cookwala. Experimental: the tool names may still change.

Why there is nothing to host

This site is a set of static files on GitHub Pages, and Pages cannot answer a remote MCP request. So the server does not live here. Your agent starts it on your own machine over stdio, and it reads the same public files you can open in a browser: the signed index, the recipes, the vocabularies and the device presets.

Every index file is checked against the hash in the manifest, and every recipe's hash is recomputed before anything is returned. A mismatch returns an error and no content. After the first run it works offline from its cache. It sends no telemetry and has no accounts.

There is also an optional hosted endpoint, mcp.cookwala.ai, on Cloudflare rather than on this site. It serves the same read-only tools and exists so directories such as mcprush.com can list and count calls to it. The /mcp route needs a token; for your own agent use the npm package above, or the open routes: POST https://mcp.cookwala.ai (the same tools, no token) and the recipe REST API for plain HTTP clients. Details.

agent ──stdio──▶ npx @cookwala/mcp
                   │  checks hashes, caches
                   ▼ HTTPS GET
cookwala.ai (GitHub Pages)
  /v1/manifest.json   /v1/index/…
  /v1/recipes/<id>    /v1/vocab/…
  /v1/capabilities/…
                   │ optional, facts only
                   ▼
fifi.cooking  /data/…

24 read-only tools

Every tool is marked read-only. Results are structured JSON. Recipe text comes back as data, never as instructions.

Find and read

search_recipes (by words, cuisine, course, level, collection, allergen-free), get_recipe (summary, ingredients, process, text or full, hash verified), list_collections.

Ask anything about the catalog

query_recipes filters by country, ingredients, nutrition, diet (vegetarian, halal, kosher, gluten-free), allergens, cooking method, source, kids, time and language. similar_recipes, compare_recipes, ingredient_profile, catalog_stats, plan_meals, shopping_list and catalog_listing do the rest. get_recipe takes include for any parts. Same operations as the REST API.

Can this device cook it?

dry_run against a built-in preset or your own capabilities, list_device_presets, explain_step. Refused or accepted, with the reason, before anything heats.

Safe bands

check_envelope checks a temperature trace against an operation's band, with altitude. list_operations shows each operation's envelope and sensor ladder.

Agent safety

check_mandate says whether an action is inside a signed mandate. verify_recipe recomputes a recipe's hash. verify_certification and current_certifications check halal, kosher and other certifications against the authority keys you trust. None of them can start or change anything.

Food rescue

parse_sms turns a Humanitarian Profile message (OFFER, FARM, CLAIM, HAND, DIST, MENU) into a structured command, Arabic digits included.

fifi.cooking

fifi_search and fifi_source find recipes the catalog does not have yet, under the same rights rules: steps only where they may be shown.

Also six resources (cookwala://recipe/<id>, schemas, any doc page, device presets, the operation list, llms.txt) and three prompts. Full reference.

fifi.cooking and Cookwala's standard

fifi.cooking is where the recipes are written. Cookwala is the standard form they are published in: one document per recipe, with a hash, a licence, a credit and a link back to the original page. Agents read that form through get_recipe.

fifi.cooking is a static site (React, TypeScript, Vite and Tailwind CSS on GitHub Pages) and its recipes are plain JSON files under /data. That is what fifi_search and fifi_source read, so no fifi.cooking server is involved. How it is built.

Recipes added to fifi.cooking after the last export are visible through fifi_search with ingredients and times, and the 499 world-cuisine recipes (China, Ethiopia, France, Greece, India, Indonesia, Iran, Italy, Japan, Korea, Lebanon, Malaysia, Morocco, Mexico, Nigeria, Peru, the Philippines, Spain, Thailand, Turkey, Vietnam) are in the catalog. Where a collection's rights are not confirmed, as for the book, channel and world collections, steps are withheld. Bringing a newer recipe into the standard is an export run by a maintainer, described in the export guide.

Try it in your browser

This page runs the same JavaScript core as the server, against the live files on this site. No request leaves for any other service. That is the proof that nothing runs on a server.

Loading the catalog…

What it will not do