For AI agents

Connecting to The Meal Plan Vault

If you are an AI agent acting for a Meal Plan Vault user, don't drive the web app or scrape its pages. Use the API. It has 19 tools that cover recipes, the weekly meal plan, grocery lists, and the pantry, and every call is scoped to your user's household and role.

Choose a way in

You can add an MCP server

Connect over streamable HTTP. OAuth 2.1 with PKCE and dynamic client registration is discovered automatically; a personal access token in an Authorization: Bearer header also works.

https://www.mealplanvault.com/mcp

You build clients from OpenAPI

Read the spec and call the REST API with a personal access token. Same tools, same results. This is the path for Meta Muse custom connectors.

https://www.mealplanvault.com/api/agent/v1/openapi.json

Get a token from your user

You can't create a token yourself. Ask your user to create one:

Sign in at https://www.mealplanvault.com/dashboard/settings?tab=connections.
Under API access, name the token after you, choose Read only or Read & write, and click Create token.
Copy the token, which starts with mpv_pat_. It is shown once.

Store the token in your credential store. Don't ask the user to paste it into the conversation, and don't repeat it back. Only ask for write access if the user wants you to change their plan, recipes, lists, or pantry.

REST API

Base URL: https://www.mealplanvault.com/api/agent/v1
Spec: https://www.mealplanvault.com/api/agent/v1/openapi.json (OpenAPI 3.1, public)
Every tool is POST /tools/{tool_name} with its arguments as a JSON body. Send {} when there are none. The response body is the tool's JSON result.
GET /me checks the token and lists the tools it can call.

curl -s https://www.mealplanvault.com/api/agent/v1/me \
  -H "Authorization: Bearer $MEAL_PLAN_VAULT_TOKEN"

curl -s -X POST https://www.mealplanvault.com/api/agent/v1/tools/get_meal_plan_week \
  -H "Authorization: Bearer $MEAL_PLAN_VAULT_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"week_start_date": "2026-09-21"}'

Status	Meaning
200	The tool's result
400	Invalid JSON or arguments. `details` lists each problem
401	Missing, unknown, expired, or revoked token. Ask the user for a new one
403	Read-only token used on a write tool
404	No tool by that name
422	Refused. The item isn't in the household, the user's role can't edit, or a plan limit was reached. `error` says which

Meta Muse

Muse doesn't add MCP servers, so it uses the REST API above as a custom connector. The user sends Muse this message, then pastes their token when Muse asks for credentials:

Create a custom connector for The Meal Plan Vault using the OpenAPI spec at https://www.mealplanvault.com/api/agent/v1/openapi.json. It uses a Bearer token — I'll add it to the credential store.

If you are Muse: build the connector from the spec, authenticate with a Bearer token from the Secure Credentials Store, and call GET /me to confirm the connection before doing anything else.

Tools (19)

The same names work as MCP tools and as REST operations. Full input schemas are in the OpenAPI spec.

Recipes

list_recipesreadSearch recipes by title or tag
get_recipereadRead a recipe in full — ingredients, steps, tags
create_recipewriteWrite a new recipe into the vault
import_recipe_from_urlwriteImport a recipe from any link
update_recipe_noteswriteAdd or update the notes on a saved recipe

Meal plans

get_meal_plan_weekreadRead any week of the plan
set_meal_plan_entrywriteSchedule a meal into a day and slot
remove_meal_plan_entrywriteClear a slot in the plan

Grocery lists

list_grocery_listsreadList grocery lists
get_grocery_listreadRead a list and everything on it
create_grocery_listwriteBuild a new list, sorted by aisle
add_grocery_list_itemwriteAdd an item to a list
check_grocery_list_itemwriteCheck an item off while shopping
remove_grocery_list_itemwriteRemove an item from a list
delete_grocery_listwriteDelete a list and its items

Pantry

list_pantry_itemsreadSee what's on hand, by shelf or by what expires soonest
add_pantry_itemwriteAdd something you just bought
update_pantry_itemwriteDraw an item down after cooking with it
remove_pantry_itemwriteRemove an item once it's gone

Rules

Everything is scoped to your user's household. You can't see other households.
You inherit your user's household role. A viewer's agent can read but not change anything.
Every call, read or write, is logged with your connection's name in an activity log the user can review.
Confirm with the user before deleting a grocery list or replacing a planned meal.
Recipe creation counts toward the plan's recipe limit; a 422 says when it's reached.

More: llms.txt · Setup guide for people · Security