Dillr for Claude
Use Dillr inside Claude as a Model Context Protocol (MCP) connector.
Dillr is a personal cooking assistant that remembers your kitchen, tastes, family, and cooking history. The Claude connector lets you bring that context into any Claude conversation — plan meals, manage your pantry, save recipes, and build shopping lists without leaving Claude.
What the connector does
The Dillr connector turns Claude into a cooking assistant that actually knows your kitchen. Instead of answering every “what should I cook?” question from scratch, Claude can load your pantry, dietary restrictions, household size, upcoming occasions, and cooking history in a single tool call — and then reason about meals the way a friend who’s eaten at your table would.
Concretely, once connected you can have conversations like:
- “What can I make in 60 minutes with what I have?” — Claude reads your pantry and leftovers, filters by your household’s dietary restrictions, and suggests dishes from your saved recipe library or proposes new ones that fit what’s on the shelf.
- “Plan dinners for the week. My in-laws are coming Saturday and Friday has to be vegetarian.” — Claude pulls upcoming occasions, checks who’s eating, balances cuisines across the week, and saves the plan as a menu you can open in the Dillr app. Shopping list included.
- “I just got back from the market with salmon, asparagus, lemons, and a bunch of basil.” — Claude updates your pantry and crosses those items off any active shopping list in one step.
- “Save this recipe my grandmother sent me.” — Claude authors a restaurant-quality version using Dillr’s recipe-creation guide — proper mise en place, timer metadata, sensory cues — and files it into your library in its original language.
- “What have I cooked twice this month that I rated highly?” — Claude queries your cooking history with ratings and notes, so you can build a rotation of proven favorites instead of guessing.
- “I’m cooking the miso-glazed cod tonight — walk me through it.” — Claude fetches the full recipe and acts as a sous-chef, answering substitution questions, adjusting for servings, and logging how it turned out when you’re done.
What makes the connector useful
- Shared kitchen memory. Dillr stores a durable model of your kitchen in Firestore — pantry, leftovers, equipment, household members, dietary restrictions, cooking history, profile notes, upcoming occasions. Every Claude conversation starts with that context, so you never have to re-explain that your partner is vegetarian or that you already have three jars of harissa.
- Household-aware, not just user-aware. Kitchens can be shared. If you and your partner both use Dillr, a meal Claude plans with you is visible to them on their phone, and vice versa. The connector follows the same permission model.
- Pantry-grounded suggestions. Claude is nudged (via the server’s instructions and the
get_kitchen_contexttool) to look up what you actually have before suggesting anything. Less “here’s a generic stir-fry recipe”, more “you’ve got half a head of cabbage from Tuesday — here’s how to finish it.” - Cooking history as signal. Every cooked meal can be logged with a rating and notes. Over time Claude learns which recipes in your library are winners, which ones you tweak, and which ones you quietly never make again.
- Multi-kitchen support. If you keep a separate pantry at a vacation place, a shared student flat, or a second home, Claude can switch between kitchens mid-conversation with
switch_kitchen— each one has its own inventory, history, and menus. - Occasion-aware planning. Dillr knows about birthdays, dinner parties, school lunches, fasting periods, and other upcoming dates that should bend a weekly menu. Claude factors them in automatically.
- Original-language recipes. Dillr never translates saved recipes. If you cook in Swedish, German, Spanish, Italian, or Turkish, your library stays in that language even if you chat with Claude in English.
- Specialist guides, loaded on demand. Dillr ships with expert system prompts that Claude can pull before a tricky task. This is how we get consistent, high-quality recipe authoring and search results without bloating every conversation.
- Everything syncs to your devices. Whatever Claude saves — a new recipe, a weekly menu, an updated pantry, a shopping list — shows up instantly in the Dillr iOS app and the Dillr web app at dillr.ai. Plan with Claude at your desk, then pull out the phone at the store to tick items off a tap-friendly shopping list, or open the hands-free cooking view at the stove with the recipe Claude just wrote. The connector is the authoring surface; the apps are where you actually live with the data.
Claude never sees your Firebase password, payment details, or anything outside the tools listed in the Tool reference below. Every tool call is scoped to your account only.
Before you start
You need:
Connecting Dillr to Claude
- Open Claude.ai → Settings → Connectors
- Find Dillr in the directory and click Connect
- Claude redirects you to Dillr’s sign-in page
- Sign in with the same account you use on the Dillr iOS app
- Claude redirects back and the connector becomes active
That’s it. Ask Claude anything cooking-related — it’ll use your Dillr kitchen automatically.
To disconnect, open Claude’s connector settings and revoke access, or sign out of Dillr from the connector settings page.
How authentication works
Dillr’s connector uses standard OAuth 2.1 with PKCE (S256) and Dynamic Client Registration (RFC 7591). When you click Connect:
- Claude registers itself dynamically with Dillr’s authorization server
- Claude redirects you to Dillr’s sign-in page with a PKCE challenge
- You sign in with Firebase Auth (same flow as the iOS app)
- Dillr issues Claude a short-lived access token (1 hour) and a refresh token stored server-side and revocable at any time
- Claude uses the access token to call Dillr tools; when it expires, it uses the refresh token to get a new one
No password is ever shared with Claude. Revoking the connector invalidates the refresh token immediately — any subsequent refresh attempt is rejected.
Access tokens are scoped to your account only: Claude can never see another user’s kitchen.
Tool reference
The connector exposes 23 tools. They fall into five groups:
Kitchen context (read)
| Tool | What it does |
|---|---|
get_kitchen_context | Snapshot of your active kitchen: pantry, dietary preferences, household, recent cooking, profile notes. Claude usually loads this first. |
get_inventory | Full pantry listing. |
get_cooking_history | Recent cooking log entries with ratings and notes. |
get_occasions | Upcoming occasions (birthdays, guests, holidays) that should influence meal planning. |
get_guide | Fetch an internal authoring guide (e.g. recipe_creation, library_discovery). |
list_kitchens | List kitchens you belong to (personal + shared), plus which one is active. |
Recipes (read)
| Tool | What it does |
|---|---|
search_recipes | Search your saved recipe library by title, cuisine, ingredient, and more. |
get_recipe | Fetch the full markdown content of a recipe by its link (personal library, menu snapshot, or cooking history). |
get_recipe_stats | Aggregate stats across your library: cuisines, ingredients, time buckets. |
Menus & shopping (read)
| Tool | What it does |
|---|---|
get_menu | Fetch a specific menu or list all menus in the active kitchen. |
get_shopping_list | Fetch a specific shopping list or list all lists. |
Additive writes
These tools only append or flip a pointer — they never overwrite or delete existing data.
| Tool | What it does |
|---|---|
log_meal | Append an entry to cooking history with optional rating and notes. |
switch_kitchen | Change the active kitchen for subsequent tool calls. |
Destructive writes
These tools can overwrite existing data. Claude will usually propose the change and wait for your approval before calling them.
| Tool | What it does |
|---|---|
update_profile | Update your profile notes and preferences. |
update_kitchen | Update kitchen-wide settings (household, equipment, etc.). |
update_inventory | Update the pantry. Supports full-replace mode. |
update_leftovers | Update the leftovers list. |
update_occasions | Update upcoming occasions. |
save_recipe | Create a new recipe or edit an existing one (by recipe_id). |
save_menu | Create or update a menu. |
save_shopping_list | Create or update a shopping list. |
complete_shopping_list | Mark a shopping list as completed, optionally carrying forward unchecked items. |
delete_recipe | Permanently delete a recipe from your library. |
All tools are annotated with MCP readOnlyHint / destructiveHint metadata so Claude can warn you before any destructive call.
Example prompts
Try these to see the connector in action:
- “What should I cook tonight? Something quick with what I have.”
- “Plan dinners for the week. We have guests Saturday and Friday needs to be vegetarian.”
- “I just bought salmon, asparagus, and lemons. Update my pantry and remove them from the shopping list.”
- “Save this recipe I just made — it was delicious, 4 servings, rate it great.”
- “What have I cooked twice in the last month that I rated highly?”
Languages
Dillr preserves recipe content in its original language. If you speak to Claude in Swedish, German, or Spanish, Dillr will keep your recipes in the language they were saved in.
Privacy
The connector is covered by Dillr’s main Privacy Policy — specifically the Using Dillr with Claude (MCP connector) section, which details what flows through the connector, how long we retain OAuth credentials, and what happens when you disconnect.
Short version: Claude only sees what the tools above expose. No conversation content is stored outside what a tool call explicitly writes to your kitchen. Refresh tokens live in Firestore and are revocable.
Support
Something broken? Got a feature request? Questions about the connector?
Email: hello@dillr.ai
We try to reply within a business day.