Connect Claude to weReci

weReci is a personal recipe collection — the recipes you save, the shelves an agent curates for you, and the web of connections between ingredients, techniques, and entries that grows as you cook. This connector lets Claude read that collection directly, so you can ask it things like “what should I make with what's already in my pantry shelf” or “how are my grandmother's bread recipes related to the sourdough one I just saved” without leaving your conversation with Claude.

It runs over the Model Context Protocol's Streamable HTTP transport, with standard OAuth 2.1 (dynamic client registration, PKCE) — the same kind of connection Claude uses for any other remote MCP server. You sign in with your existing weReci account; there's nothing new to set up on our side.

The one-click way — Claude's connector directory

weReci is listed in Claude's connector directory, so the fastest path is one button: open the listing and choose Connect. Claude walks you through the same weReci sign-in and consent screen described below.

Add weReci to Claude

Claude.ai (web) and Claude Desktop — manually

1. 1Open Settings → Connectors and choose Add custom connector.
2. 2Paste the server URL: https://wereci.xyz/api/mcp
3. 3Claude opens weReci's sign-in page. Sign in with your existing weReci account (or create one) and approve the permissions on the consent screen.
4. 4You're connected — ask Claude anything about your collection.

Claude Code

Add the server from the command line:

claude mcp add --transport http wereci https://wereci.xyz/api/mcp

Claude Code will prompt you to authorize in the browser the first time you use a weReci tool — same sign-in and consent screen as above.

weReci's consent screen grants three scopes, and you only ever see what your account already has access to.

• recipes:read (granted by default) — read-only browsing and search across your collection: recipes, curated shelves, and the connections graph. Nothing is created, edited, or deleted.
• email:send (optional) — lets Claude email a recipe to you. There is no recipient field anywhere in this tool: it can only ever send to the verified email address on your own signed-in account, so a misbehaving or prompt-injected agent has no way to mail anyone else. It's also rate-limited.
• grocery:cart (optional) — lets Claude add a grocery list you've approved to your own linked Kroger-family cart (Fred Meyer, Mariano's, Ralphs…). Linking your Kroger account is a separate one-time sign-in at Kroger, and items only ever land in that cart — you review everything at checkout, on Kroger's site or app.

One tool, reshuffle_conceits, regenerates your curated shelves with a fresh theme. It only rearranges your own shelves — no recipe, letter, or photo is ever modified or lost — and its instructions tell Claude to confirm with you before running it.

In plain language, here's what Claude can call once you've connected:

• ✦get_recipe_collection_overview — a facet map of your collection — recipe count, cuisines, dietary classes, source types.
• ✦search_recipes — search your saved recipes by keyword, ingredient, or idea.
• ✦get_recipe — fetch one recipe's full detail — ingredients, instructions, notes, photo — by id.
• ✦list_conceits — list your current curated shelves (themed groups of recipes) with their titles and member recipes.
• ✦reshuffle_conceits — regenerate your curated shelves with a fresh theme, optionally steered by a creative direction you give it. Confirms with you first; touches only shelf arrangement, never your data.
• ✦get_graph_overview — a summary of your connections graph — how many entries, ingredients, authors, sources, and how densely they interlink.
• ✦get_graph_node — everything directly connected to one node in the graph, grouped by relationship type.
• ✦traverse_graph — walk the connections graph outward from a starting point.
• ✦find_graph_connection — find how two things in your collection are related — e.g. the path between two recipes or ingredients.
• ✦send_recipe_email — email one recipe to your own verified address, with an optional note. Never to anyone else — see Permissions above.
• ✦build_shopping_list — turn a few recipes into one consolidated grocery list — proposed to you first, and only sent after you approve: into your own linked Kroger-family cart (with the grocery:cart permission), or emailed to you to forward to whoever shops. weReci stores no grocery lists.
• ✦add_to_shopping_list — put recipes you ask for — or one-off items like “paper towels” — on your own shopping list in the app. Only when you ask, only your own list (or your shared list if you have one), labeled with which assistant added them; entries expire on their own after 14 days if you never open them.

weReci also exposes a handful of MCP resources Claude can pull in directly — the collection's data-model schema, a collection overview, a graph overview, your curated shelves, an individual recipe or graph node by id, and a personal memory surface (“what this cookbook knows about you”: your durable preferences, stats, and facts by category).

The connector sees exactly what your account sees in the app — tenant-scoped to you, including a joint cookbook if you share one with someone. It cannot reach another account's collection under any circumstance.

You can revoke access at any time from weReci settings → Connected apps. Revoking immediately invalidates the connection — nothing further is readable until you reconnect.

For the full picture of what weReci collects and how it's used, see the privacy policy and the terms of service.