weekplan-mcp-server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@weekplan-mcp-server List all my ingredients"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
WeekPlan MCP Server
An MCP (Model Context Protocol) server that gives AI assistants like Claude the ability to manage recipes and ingredients in your WeekPlan app via its REST API. See WeekPlan for the main app. See WeekPlan Watch for an Apple Watch companion app.
What It Does
Once connected, Claude can:
List, add, and delete ingredients (name + unit)
List, add, and delete recipes (name, ingredients with quantities, and step-by-step instructions)
Automatically create missing ingredients when adding a recipe
Related MCP server: cookwith-mcp
Prerequisites
Node.js 18+ — Download here
A running WeekPlan API server (defaults to
http://localhost:3000)
Installation
Option 1 — Clone and build (recommended for local development)
git clone <your-repo-url> weekplan-mcp-server
cd weekplan-mcp-server
npm install
npm run buildThe compiled server will be at dist/index.js.
Option 2 — Install globally from npm (once published)
npm install -g weekplan-mcp-serverThis makes the weekplan-mcp-server command available system-wide.
Configuration
The server is configured via a single environment variable:
Variable | Default | Description |
|
| Base URL of your WeekPlan REST API |
Adding to Claude Code
Run the following command to register the server with Claude Code:
claude mcp add weekplan-mcp-server -e WEEKPLAN_URL=http://localhost:3000 -- node /absolute/path/to/weekplan-mcp-server/dist/index.jsReplace /absolute/path/to/weekplan-mcp-server with the actual path where you cloned the repo.
Or edit ~/.claude.json to add it to a specific project.
Or edit claude_desktop_config.json directly (see the Claude Desktop section below — the format is the same).
Adding to Claude Desktop
Edit your Claude Desktop config file:
macOS:
~/Library/'Application Support'/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.jsonLinux:
~/.config/Claude/claude_desktop_config.json
Add the server under mcpServers:
{
"mcpServers": {
"weekplan": {
"command": "node",
"args": ["/absolute/path/to/weekplan-mcp-server/dist/index.js"],
"env": {
"WEEKPLAN_URL": "http://localhost:3000"
}
}
}
}Restart Claude Desktop after saving the file.
Adding to Cursor
Open Cursor settings and navigate to Features → MCP Servers, then add:
{
"weekplan": {
"command": "node",
"args": ["/absolute/path/to/weekplan-mcp-server/dist/index.js"],
"env": {
"WEEKPLAN_URL": "http://localhost:3000"
}
}
}Adding to VS Code (Copilot / MCP extension)
In your .vscode/mcp.json or user settings:
{
"servers": {
"weekplan": {
"type": "stdio",
"command": "node",
"args": ["/absolute/path/to/weekplan-mcp-server/dist/index.js"],
"env": {
"WEEKPLAN_URL": "http://localhost:3000"
}
}
}
}Available Tools
Ingredients
Tool | Description | Parameters |
| List all ingredients | (none) |
| Add or update an ingredient |
|
| Delete an ingredient |
|
Recipes
Tool | Description | Parameters |
| List all recipes | (none) |
| Add or update a recipe |
|
| Delete a recipe |
|
The ingredients array in weekplan_add_recipe accepts objects with:
ingredientName— name of the ingredient (created automatically if missing)quantity— numeric amountunit— unit of measurement (e.g."g","ml","tbsp")
IDs are generated automatically from names (e.g. "Olive Oil" → "olive-oil"), so add operations are idempotent — running them twice won't create duplicates.
Example Prompts
Once the server is connected, try asking Claude:
Add a recipe for spaghetti bolognese with ingredients and steps.List all my ingredients.Add 500g of chicken breast as an ingredient.Delete the recipe for lasagne.Development
# Run directly from TypeScript (no build step needed)
npm run dev
# Build to dist/
npm run build
# Run the compiled server
npm startThe server communicates over stdio, so it has no open ports and is safe to run as a subprocess managed by your AI client.
Project Structure
src/
├── index.ts # Entry point — connects stdio transport
├── server.ts # Registers all tools with the MCP server
├── api-client.ts # HTTP client for the WeekPlan REST API
├── slugify.ts # Converts names to stable IDs
└── tools/
├── ingredients.ts # Ingredient tool handlers
└── recipes.ts # Recipe tool handlersTroubleshooting
"Cannot connect to WeekPlan API"
Make sure your WeekPlan server is running and WEEKPLAN_URL points to the correct address.
"command not found: node" Node.js is not installed or not on your PATH. Install it from nodejs.org.
Tools don't appear in Claude
Confirm the path in your config points to
dist/index.js(notsrc/index.ts)Make sure you ran
npm run buildafter cloningRestart your AI client after changing the config
Build errors
Run npm install first to ensure all dependencies are present, then npm run build.
Available Tools
8 toolsweekplan_add_ingredientAIdempotent
Add or update an ingredient. Creates a stable slug ID from the name. Always use Dutch for the name.
Inputs: name (required), unit (required).
weekplan_add_recipeAIdempotent
Add or update a recipe with its ingredients list and cooking steps. Each ingredient references a name and quantity/unit. Missing ingredients are created automatically. Always use Dutch for the name, ingredient names, and steps.
Inputs: name (required), steps (required), ingredients (required).
weekplan_delete_ingredientCDestructive
Delete an ingredient by id.
Inputs: id (required).
weekplan_delete_recipeCDestructive
Delete a recipe by id.
Inputs: id (required).
weekplan_edit_ingredientAIdempotent
Edit an existing ingredient by id. Supply only the fields you want to change; omitted fields keep their current values. The ingredient id never changes, so recipe references stay intact. Always use Dutch for the name.
Inputs: id (required), name, unit.
weekplan_edit_recipeAIdempotent
Edit an existing recipe by its id. All fields are optional — only the fields you provide will be updated. Use this to rename a recipe, translate it, change steps, or replace ingredients. Always use Dutch for the name, ingredient names, and steps.
Inputs: id (required), name, steps, ingredients.
weekplan_list_ingredientsBRead-only
List all ingredients in the week plan.
Inputs: no named parameters.
weekplan_list_recipesARead-only
List all recipes (with ingredients and steps).
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
The recipe and ingredient resources are clearly separated, and list/add/edit/delete verbs are distinct. Minor overlap exists because add_ingredient and add_recipe are described as 'add or update' (upsert), which slightly blurs the boundary with edit_ingredient and edit_recipe.
Every tool follows the identical weekplan_<verb>_<noun> pattern (list_recipes, add_ingredient, edit_recipe, delete_ingredient, etc.). The convention is predictable and readable throughout with no deviations.
Eight tools cleanly cover two related resources (recipes and ingredients) with full CRUD each. This is a well-scoped, minimal-but-sufficient set with no redundant tools.
Both recipes and ingredients have complete lifecycle coverage: list, add/create, edit, and delete. There is no obvious missing operation, and list_recipes with ingredients/steps covers read needs without a separate get tool.
Maintenance
Related MCP Connectors
MCP server that lets AI assistants use all OneSchema features exposed via the public API.
Hosted MCP server connecting AI assistants to 9,000+ apps and 40,000+ actions via Zapier.
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
MCP server that lets your AI assistant build and deploy apps, hosting each one at a live URL.
Related MCP Servers
- AlicenseAqualityDmaintenanceAn MCP server that transforms AI assistants into personal chefs by providing recipe recommendations and meal planning features based on the HowToCook repository.56,244 npm800ISC
- AlicenseBqualityDmaintenanceAn MCP server that enables AI-powered recipe generation and transformation using natural language, supporting dietary restrictions, allergies, and nutritional goals.213 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for MealMastery AI meal planning that enables users to manage meal plans, recipes, and grocery lists through natural language conversation with AI agents like Claude.52 npmMIT
- AlicenseNot gradedqualityBmaintenanceMCP server for Cookidoo, enabling AI tools to search recipes, manage shopping lists, and retrieve account and subscription information.2GPL 3.0