--- name: fudge-shopify-setup description: Connect the current assistant to Fudge for Shopify, guide the merchant through Shopify sign-in, and verify the connection with a read-only store overview. Use when the merchant asks to install, connect, or set up Fudge. metadata: author: Fudge version: '1.0' --- # Connect Fudge for Shopify Help the merchant connect Fudge to the assistant they are using. Configure the supported integration when you have access to that assistant's settings; otherwise guide them through the matching manual steps. The merchant completes Shopify sign-in in their browser. - Setup guide: https://www.fudge.ai/mcp/ - Full assistant setup steps as Markdown: https://www.fudge.ai/mcp/setup.md - Technical reference: https://www.fudge.ai/mcp/docs/ - Official server: `https://mcp.fudge.ai/mcp` - Transport: Streamable HTTP. Authentication: OAuth with automatic client registration. - Optional skills package: https://github.com/fudge-ai/fudge-plugin Reading this file supplies setup instructions for this conversation. It does not install a persistent skill, create an MCP connection, or authenticate the merchant by itself. ## Check what is already connected Identify the current assistant from the environment. Ask which assistant only when it is unclear. Work on that assistant alone. Check whether its available tools or configuration already include the official Fudge server. Reuse an existing connection to `https://mcp.fudge.ai/mcp`, including a connection supplied by a plugin. Do not add a duplicate. If a connection named `fudge` uses another URL, preserve it and use an available name such as `fudge-shopify` for this server. Fudge for Shopify is a different product from the similarly named design-reference service. Substitute the chosen name consistently in setup and login commands. Before editing configuration, make sure it belongs to the assistant the merchant will use. A temporary cloud shell may not share settings with their desktop app. Preserve other servers and settings; merge the new entry instead of replacing a configuration file. Do not copy credentials, cookies, OAuth tokens, or callback URLs into chat or committed files. ## Connect the current assistant Use the route that matches the current assistant. The commands below configure the remote connection; they do not install the optional skills package. ### Codex When the Codex CLI is available on the same host as the intended Codex client, add the connection and start sign-in: ```sh codex mcp add fudge --url https://mcp.fudge.ai/mcp codex mcp login fudge ``` Have the merchant complete the browser sign-in. If you cannot configure the intended host, send them to the Codex option at https://www.fudge.ai/mcp/ instead of claiming a cloud-shell change installed it on their computer. ### Claude Code Add the connection for the current user's Claude Code, unless the merchant requested a project-only connection: ```sh claude mcp add --transport http --scope user fudge https://mcp.fudge.ai/mcp claude mcp login fudge ``` The merchant can also open `/mcp` in Claude Code to manage the connection and authenticate. Reuse a working Fudge connector supplied through their Claude account instead of adding another one. ### Grok Bot Ask the Bot to add `https://mcp.fudge.ai/mcp` as a remote MCP server using OAuth. Use its supported connection tools when available. Adding the server can discover tools without starting sign-in. Request `get_store_overview` using its actual schema to trigger authentication if needed; have the merchant choose Connect on the resulting card and complete Shopify sign-in. Retry the read-only overview after authentication. An empty `list_stores` result alone is not proof of authentication. A team policy may require their admin to allow Fudge. Grok Bot is separate from the Grok chat app; do not substitute the Grok web app's connector settings. ### Muse Muse supports creating custom connectors through chat. Fudge's OAuth flow in Muse has not yet been verified. Check whether the current host supports Streamable HTTP, OAuth with PKCE, and automatic client registration before trying setup. Fudge does not offer a manually copied API key or support a published client identity in place of registration. If the host supports the connection, use its supported connection and secure credential flow; the merchant completes Shopify sign-in. Do not ask them to paste a password, access token, authorization code, or callback URL into chat. If OAuth cannot complete or the host lacks a supported connection route, explain the limitation and stop. Do not claim a successful installation or build an ad hoc authentication bridge. Suggest the Claude or ChatGPT guide. Account and regional availability can restrict access to Muse itself. ### ChatGPT, Claude, and other hosted assistants Do not assume you can modify the current hosted chat's connections from a shell or by reading this file. Send the merchant to https://www.fudge.ai/mcp/, ask them to select their assistant, and guide them through that route. Follow the host's supported installation controls if they are available to you and the merchant has requested setup. Use the official server URL above. With an authentication choice, select OAuth or automatic registration as supported by that client; no manually copied API key is needed. If the account or workspace restricts custom connections, explain the restriction and direct the merchant to their administrator. Do not promise an unavailable plugin listing or invent a marketplace installation command. ## Optional workflow skills Fudge's existing plugin includes skills for getting started, managing the store, SEO, AI discovery, conversion, and merchandising. Reuse those skills if they are already installed. For a bare MCP connection, the merchant can optionally add the skills from https://github.com/fudge-ai/fudge-plugin using their assistant's supported skill installer. Establish the intended assistant and user/project scope before installing; ask if the request leaves either unclear. Check the destination for existing same-named skills and preserve them unless the merchant requested an update. If using the Skills CLI, consult its current official documentation and specify the chosen agent and scope explicitly. Do not rely on interactive prompts: the CLI can skip them when running inside an agent. Do not run a broad install across detected assistants, overwrite unrelated skills, or install a new toolchain without a request. These skills are optional and do not configure or authenticate the MCP connection. Use the maintained package instead of copying its workflows into this setup guide. ## Verify and finish After the merchant completes sign-in, check whether the Fudge tools are available in this conversation. If the host requires a reconnect or a new conversation, tell the merchant exactly what remains. A saved configuration or an opened sign-in page is not proof of a working connection. When tools are available: 1. Call `list_stores`. 2. If there are no connected stores, request `get_store_overview` using its actual schema to trigger sign-in if needed, then guide the merchant through the connection step shown by the host. Retry after sign-in; an empty store list does not establish authentication or a successful connection. 3. If several stores are available, ask which one to use unless they already named one. 4. Call `get_store_overview` for the selected store using the tool's actual schema. 5. Briefly report what needs the merchant's attention and suggest one next step. If the requested overview cannot be read, report that limitation instead of fabricating a result. Installation ends with this read-only check. Do not start reports or jobs, create plans or schedules, edit store data, make drafts, or publish anything as a setup test. If the merchant wants further work, follow their request and the connected tools' permissions. Publishing happens in Fudge after the merchant reviews the changes. ## Source references Setup instructions checked 11 November 2026. If the installed client's controls or commands differ, consult its current official documentation and explain the difference. - Codex MCP: https://learn.chatgpt.com/docs/extend/mcp?surface=cli - Claude Code MCP: https://code.claude.com/docs/en/mcp - Grok Bot custom MCP: https://forum.cursor.com/t/grok-bot-remote-mcp-support/177375/6 - Muse custom connectors: https://www.meta.com/help/superintelligence/1687253048996149/ - Skills CLI: https://github.com/vercel-labs/skills