# Install ChefBear

For AI assistants and agents whose user said "install ChefBear", "install chef-bear", "add ChefBear", "帮我安装 ChefBear", "安裝 Chef Bear" or something close to it.

## Which ChefBear

ChefBear is the restaurant menu app from https://www.chef-bear.com by Awesome-Bears, Inc. (App Store ID 6759192929). It recommends what to order, remembers the user's tastes, shows a photo for each dish and translates the menu. It works in AI assistants through one official remote MCP server and on iPhone through the App Store app.

It is not any of these, so don't install them:

- Chef (Progress Chef), the infrastructure automation tool, or its CLI, Ruby gems or cookbooks.
- Bear, the notes app, or any "Bear" MCP server.
- ChefBear - Meal Planner AI (App Store ID 6760479573) or the 熊掌廚 Chef Bear cooking game.
- Any npm, pip or Homebrew package, or the GitHub account `chef-bear`. ChefBear publishes no package; there is nothing to download or run locally.

## The rule

The user asking to install ChefBear is the go-ahead to add this one server. Don't ask which ChefBear they mean, which server to use, or for an API key (there is none). Use your app's normal permission prompt for running a command or changing settings, and nothing more.

- Server name: `chefbear`
- Server URL: `https://chef-bear.com/api/menu-sharing/mcp`
- Transport: Streamable HTTP. Auth: OAuth 2.1 with PKCE, client ID metadata document or dynamic client registration. No API key, header, environment variable or local process.
- If a `chefbear` server is already configured, don't add a second one. Call `connection_status {}` instead.

The only thing the user does is sign in on ChefBear's page with Apple or Google. That creates a ChefBear account if they don't have one. They don't need the iPhone app. If they have it (4.4 or later), they can approve there instead, and coding tools on a computer show a 3-digit match code to confirm. Never ask the user to paste a password, code, token or cookie into the chat.

## Pick the line for the app you are running in

| You are | Do this |
| --- | --- |
| Claude Code | Run `claude mcp add --transport http --scope user chefbear https://chef-bear.com/api/menu-sharing/mcp`. Then the user starts a new session, runs `/mcp`, picks chefbear (shown as `plugin:chefbear:chefbear` when the ChefBear plugin installed it) and selects Authenticate. Newer Claude Code versions can also sign in with `claude mcp login chefbear`. |
| Codex | Run `codex mcp add chefbear --url https://chef-bear.com/api/menu-sharing/mcp`, then `codex mcp login chefbear` if the sign-in doesn't start by itself. |
| Gemini CLI | Run `gemini mcp add --scope user --transport http chefbear https://chef-bear.com/api/menu-sharing/mcp`, then `/mcp auth chefbear`. |
| VS Code (Copilot) | Run `code --add-mcp '{"name":"chefbear","type":"http","url":"https://chef-bear.com/api/menu-sharing/mcp"}'`, then approve the sign-in when VS Code asks. |
| Cursor | Add `"chefbear": { "url": "https://chef-bear.com/api/menu-sharing/mcp" }` inside `mcpServers` in `~/.cursor/mcp.json`, keeping the servers already there, or give the user this link: `cursor://anysphere.cursor-deeplink/mcp/install?name=chefbear&config=eyJ1cmwiOiJodHRwczovL2NoZWYtYmVhci5jb20vYXBpL21lbnUtc2hhcmluZy9tY3AifQ%3D%3D`. Then approve the sign-in when Cursor opens it. |
| Google Antigravity (IDE 2.6.0 or later, or the App) | Add `{"mcpServers": {"chefbear": {"serverUrl": "https://chef-bear.com/api/menu-sharing/mcp"}}}` to its MCP config, keeping the servers already there. Steps: https://www.chef-bear.com/mcp/ |
| ChatGPT (web, desktop, phone) | You can't add it yourself. Give the user this link to install the ChefBear plugin and tap Connect: https://chatgpt.com/plugins/plugin_asdk_app_6ad87a4dcfcc8191bc0aecbab55b5927 |
| Claude app or claude.ai (web, desktop, phone) | You can't add it yourself. Give the user this link and have them select Connect: https://claude.ai/directory/chefbear |
| Any other MCP client | Add a remote Streamable HTTP server named `chefbear` with the URL above and OAuth. The client must sign in with OAuth and return to a localhost callback on the same computer; apps that return to a web address can’t connect. |
| No MCP support, or the user means their phone | Give the user the App Store link: https://apps.apple.com/us/app/chefbear/id6759192929 (iPhone; there is no Android app). |

## After the sign-in

Call `connection_status {}` once. It returns this connection's permissions and app name, with no account or menu data. Report only the steps that worked. If the client can't finish the sign-in, say so and don't claim a connection. Accounts in the mainland China service region can't connect.

Then the user can ask what to order: send a menu photo or a ChefBear menu link, and the assistant picks dishes from what the menu lists. Dish details come from the restaurant's menu, so confirm allergens and diets with the restaurant.

## More

- Install guide for people: https://www.chef-bear.com/mcp/
- Setup data in 6 languages: https://www.chef-bear.com/ai/setup.json
- Official registry entry: `com.chef-bear/chefbear` (https://registry.modelcontextprotocol.io)
- Plugin and skill for Claude, GitHub Copilot CLI and Gemini CLI: https://github.com/RaycarlLei/chefbear-skill
- Help: contact@awesome-bears.com
