Connect Wen Dinner to ChatGPT and Other AI Assistants
Connect an AI assistant to Wen Dinner to find recipes, see what food you have, and manage your shopping lists from a conversation. Wen Dinner uses MCP (Model Context Protocol), a standard for connecting assistants to external tools.
You do not need to wait for Wen Dinner to appear in an assistant's public directory. Compatible assistants can connect directly using this server URL:
https://wendinner.com/mcp
Choose OAuth authentication and, if asked, Streamable HTTP transport. Sign in with your own Wen Dinner account and passkey, then review the requested permissions. You do not need an API key.
What Can My Assistant Do?
With the appropriate permissions, your assistant can:
- Identify the Wen Dinner account you connected.
- Search recipes you can access and read their ingredients and cooking steps.
- Compare cooking times, physical yields, and recorded serving counts directly in recipe search results.
- Read your food inventories and find ingredients you have on hand.
- Read meal calendars and create, move, or remove planned meals and their recipes.
- List shopping lists you own or can edit and read their items.
- Add, edit, remove, and check off shopping-list items.
Try asking:
What could I cook with the ingredients in my fridge?
Find a chicken recipe that takes less than 30 minutes.
What have I planned for dinner this week?
Plan this soup for Tuesday at 6 p.m. on my family calendar.
Show my Wen Dinner shopping lists.
Add milk to my weekly shopping list.
Check off the onions on my weekly shopping list.
For shopping requests, create a shopping list in Wen Dinner first. If you have several lists, name the one you want. Recipe and food-inventory access is read-only: your assistant cannot change the stored recipes or update food on hand. Separate meal-plan permissions let it read or edit calendars you can access.
For meal planning, set up a calendar with an explicit timezone, default food inventory, and shopping list in Wen Dinner. Missing ingredients from future planned meals appear automatically on the linked shopping list after accounting for usable stock; your assistant does not need to add them separately. Planning does not mark food cooked or put groceries away. Recipes are planned at their recorded yield—serving adjustments are not supported yet. Meals with cooking history must be managed in Wen Dinner rather than changed through the external connection.
When choosing a meal, check that you have enough ingredients for everyone and remember any food you're saving for another meal.
The external connection is separate from Wen Dinner's built-in chat agent. The two offer different tools; connecting your preferred assistant does not give it every feature of the built-in chat.
Before You Connect
- Make sure you can sign in to Wen Dinner in your browser. See Accounts and Passkeys if needed.
- Check that your assistant's plan supports custom remote MCP connections. Organization administrators may need to approve the connection.
- Wen Dinner is not affiliated with ChatGPT, Claude, OpenCode, or the other assistants mentioned here. When you connect one, data shared with it is subject to that provider's privacy policy. Only connect assistants you trust.
- Read-only shopping access and permission to change items are separate permissions. Grant only what you need. Your assistant may also ask for approval before individual actions.
Choose Permissions
Permissions are requested by your AI assistant when you set up the connection. Wen Dinner's sign-in screen lets you review and approve that request; it does not let you add permissions the assistant did not request.
If your assistant provides a Scopes or OAuth scopes field, enter the permissions you want, separated by spaces:
| Permission | Scope |
|---|---|
| Identify your account | profile:read |
| Search and read recipes | recipes:read |
| Read food on hand | inventory:read |
| Read meal calendars and planned meals | mealplan:read |
| Create, change, and remove planned meals | mealplan:write |
| Read shopping lists | shopping:read |
| Add, edit, remove, and check off shopping items | shopping:write |
To enable all the features described above, use:
openid offline_access profile:read recipes:read inventory:read mealplan:read mealplan:write shopping:read shopping:write
Leave out shopping:write and mealplan:write for a read-only connection. openid supports sign-in and offline_access lets the assistant stay connected without asking you to sign in each time.
For recipe suggestions based on food you have, include both recipes:read and inventory:read.
Some assistants choose scopes automatically rather than showing a field. If a tool needs more access, follow the assistant's request to reconnect. When changing scopes yourself, save the connection settings and authorize again; approving an older request will not add the new permissions.
ChatGPT
Use ChatGPT on the web to add the connection:
- Open Plugins.
- Select +, then Add custom MCP server.
- Name it Wen Dinner and enter
https://wendinner.com/mcpas the server URL. - Choose OAuth authentication. Use discovery or the published client identity (CIMD) option if offered; you should not need to enter a client secret.
- Review the custom-server warning, acknowledge it, and select Create as a plugin.
- Complete Wen Dinner's sign-in and permission approval when prompted, then install or enable the resulting plugin.
- In a new conversation, type
@, select Wen Dinner, and ask it to show your shopping lists.
If your interface instead offers Settings → Apps → Create, use that custom-app flow with the same URL and OAuth authentication.
Custom MCP availability depends on your ChatGPT plan and workspace permissions. See OpenAI's custom MCP setup and availability guide for current requirements and instructions.
Claude, Including Claude Desktop and Cowork
These steps follow Claude's guide; the Wen Dinner connection has not yet been verified in Claude. Use a remote/web connector, not a local desktop extension:
- Open Customize → Connectors.
- Select Add custom connector, or Add → Custom → Web, depending on your interface.
- Name the connector Wen Dinner and enter
https://wendinner.com/mcp. - If authentication choices appear, choose Sign in now and Use Claude's published identity. Leave client ID, client secret, and request headers blank.
- Add the connector, follow the Wen Dinner sign-in and consent flow, and confirm that Claude shows it as connected.
- Enable Wen Dinner for your conversation using the connector controls, then ask to see your shopping lists.
See Claude's custom connector guide for current plan requirements, organization permissions, and setup options.
OpenCode
For OpenCode V2, add the remote server from your terminal:
opencode mcp add wendinner --global --url https://wendinner.com/mcp
opencode mcp list
--global makes the connection available across projects. Omit it if you only want the connection in the current project.
In OpenCode, run /mcps, choose wendinner, and complete the browser sign-in and consent flow. Once connected, ask the assistant to identify your Wen Dinner account or show your shopping lists.
Set oauth.scope in the server's configuration to request the permissions listed under Choose Permissions, then authorize through /mcps. For example, shopping-list access uses openid offline_access profile:read shopping:read shopping:write.
See OpenCode's MCP documentation.
Other MCP Assistants
For other assistants, such as Cursor, VS Code-based assistants, or Codex, use https://wendinner.com/mcp with OAuth and Streamable HTTP. Follow the assistant's official MCP instructions. If it cannot register or sign in, contact Wen Dinner to ask about OAuth client setup.
A Note About Shopping Changes
Checking off groceries marks them as bought; it does not put them in your pantry. See Shopping Lists for the details.
Manage or Revoke Access
Open Connected Apps in Wen Dinner to review connections and revoke access. Removing a connection in your assistant is useful too, but revoke it in Wen Dinner when you want to ensure its authorization is withdrawn. Revocation does not undo shopping-list changes already made or remove data already received by the assistant.
Never paste your passkey, access tokens, refresh tokens, or private credentials into a conversation or support request.
Troubleshooting
- There is no option to add a custom server: Check your assistant's plan, web interface, and workspace policies. Ask an administrator if necessary.
- A browser visit to
/mcpshows an authorization error: This is a tool endpoint, not a normal web page. Configure it in your assistant and complete OAuth sign-in. - Sign-in or client registration fails: Confirm the URL and use a supported published client identity. Some clients require prior operator setup; Wen Dinner does not support automatic dynamic registration.
- The connection works, but shopping actions do not: Check the scopes requested in your assistant's connection settings, then authorize again. See Choose Permissions above. Your assistant's plan or action settings may also restrict writes.
- No shopping lists appear: Confirm which Wen Dinner account is connected and create a list, or check that you have permission to edit the shared list.
- New tools do not appear: Refresh the assistant's tool list or ask a workspace administrator to review the updated connection. Some clients retain an approved snapshot.
- The assistant reports an uncertain result after a write: Check the shopping list in Wen Dinner before repeating the request, to avoid duplicate changes.