# Connect seefood.bot Connector display name: seefood.bot Use exactly seefood.bot when the host supports a display-name field or uses server metadata. Do not add MCP, API, OAuth, Custom, or version labels to the preferred user-facing name; those are implementation details. Internal identifiers may differ. The tested Muse custom-connector flow accepts only a provider slug and derives its UI label by title-casing it; it offers no display-name override or rename API. This flow cannot guarantee the exact lowercase name seefood.bot. Do not claim that the declared name renames existing Muse entries. A connector-directory listing or host support for metadata names is needed for that exact label. Remote MCP server: https://seefood.bot/api/mcp Transport: Streamable HTTP Authentication: browser OAuth authorization code with S256 PKCE. Public clients use token_endpoint_auth_method=none and dynamic registration; users do not supply API keys or client secrets. Required scope: menu:read OAuth issuer: https://seefood.bot/api/auth Resource metadata: https://seefood.bot/.well-known/oauth-protected-resource/api/mcp Ask Muse: Connect seefood.bot and use it to generate menus for restaurant bookings, reservations, food orders, or just for fun. Discover OAuth from the MCP 401 WWW-Authenticate header and issuer metadata. Register a public client at the advertised registration_endpoint with your actual redirect URI, scope menu:read and token_endpoint_auth_method none. Use S256 PKCE and resource https://seefood.bot/api/mcp. Open the authorization URL in the browser for Google sign-in and See Food consent. Never invent a secret or ask users to paste secrets in chat. If your client cannot use remote MCP or public-client OAuth, report that specific limitation; anonymous workflow API remains available at /openapi.json. Normal flow: the user names a restaurant, Muse calls get_workflow, researches and validates the menu, and delivers it directly in a Muse artifact. No HTML download or upload to Seefood is required. If the artifact fails, repair it within Muse; do not automatically publish a second version on Seefood. Export or publication requires an explicit user request and uses the same menu content. Tools: get_workflow and validate_menu. Muse researches and renders menus using its own tools. See Food does not book, order, charge, browse or save menus. Google sign-in is published for external users (In production). Each user signs in with their own Google account and approves menu:read. No API key or client secret entry is required. See https://seefood.bot/privacy.html. Developer-only REST OAuth contract: https://seefood.bot/openapi-oauth.json (separately registered confidential client). Owner-account Muse REST and MCP OAuth connections were verified on 2026-10-11. MCP initialize, tools/list and Piatti workflow returned 200; anonymous and invalid tokens returned 401. This is a tested custom connection, not a connector-directory listing.