Installing the Connector
Beta. The Website Assistant is in open beta and available to every ShopStable business — no invitation needed. We'd love your feedback.
The Website Assistant lets an AI assistant build and edit your ShopStable website with you — importing your current site, composing pages, and making changes you can watch land live in your editor. It works with any MCP-capable assistant through one connector.
The connector address is:
https://shopstable.com/mcp/website-assistant
What it can — and deliberately can't — do
- It composes Website Builder features only: pages, sections, and the builder's elements. It never writes code into your site, so everything it builds stays fully editable by you.
- It can never publish. You review a draft preview and click Publish yourself, in your own editor.
- It only works on businesses you grant during connection — and you can revoke access at any time from Connected apps.
Claude (claude.ai, desktop, and mobile)
- Open Settings → Connectors and choose Add custom connector.
- Paste the connector address above and save.
- Claude will send you to ShopStable to sign in and choose which of your businesses the assistant may work on — see Connecting Your Businesses.
- Back in Claude, start a conversation and ask it to work on your website.
Claude Code (terminal)
The command below makes ShopStable available in every Claude Code project on this computer. It stays private to your user account — it does not share the connection with your team.
claude mcp add --transport http shopstable --scope user https://shopstable.com/mcp/website-assistant
To limit ShopStable to the project you are currently in, replace --scope user with --scope local. Local is Claude Code's default if you leave out the scope entirely.
Next, open Claude Code, type /mcp, and follow the ShopStable sign-in action. Your browser opens the ShopStable consent screen. On newer Claude Code releases, you can start the same sign-in flow from a terminal instead:
claude mcp login shopstable
If that command is not available, use /mcp inside Claude Code.
To check the setup, run:
claude mcp list
You should see shopstable. In Claude Code, /mcp should show it as connected after you finish signing in below.
Cowork
Add the connector from Cowork's connector settings with the same address. The sign-in and business-selection flow is identical to claude.ai.
Codex (ChatGPT desktop app, CLI, and IDE)
Start with the quick terminal setup unless you prefer a settings screen. The former Codex desktop app is now part of the ChatGPT desktop app.
Quickest: Codex CLI
Open Terminal (or Codex's integrated terminal) and paste this command:
codex mcp add shopstable --url https://shopstable.com/mcp/website-assistant
This adds ShopStable to your user-level Codex configuration, so it is available in your other Codex projects on this computer. Then start the sign-in step:
codex mcp login shopstable
Prefer the ChatGPT desktop app or Codex IDE settings?
-
In the ChatGPT desktop app, open Settings → Plugins → MCP servers, then select Add server. In a Codex IDE extension, open Settings → MCP servers and select Add server.
-
Name the server ShopStable and choose Streamable HTTP.
-
Paste this address:
https://shopstable.com/mcp/website-assistant -
Save the server. You do not need to restart the ChatGPT desktop app, and the current interface does not have a separate Authenticate button.
-
Start a new ChatGPT or Codex conversation. Add ShopStable from + → More or mention it with
@. If ShopStable still needs access, ChatGPT opens the ShopStable sign-in screen then.
Use ShopStable in one trusted project only
Instead of the CLI command above, add the following block to .codex/config.toml in that project. Codex reads project configuration only after you trust the project.
[mcp_servers.shopstable]
url = "https://shopstable.com/mcp/website-assistant"
Save the file, then run:
codex mcp login shopstable
Finish signing in to ShopStable
Codex CLI and Claude Code open the same secure ShopStable browser screen. In the ChatGPT desktop app, the screen opens when you first add ShopStable to a conversation. If a browser does not open automatically, use the address printed by your client. Then:
- Sign in to your ShopStable account.
- Select the businesses this connection may work on. You can select one, several, or all eligible businesses.
- Choose when access should expire: 30 days, 90 days, or 1 year.
- Review the access and click Connect.
Your client returns to the app or terminal when the connection is complete. You do not need to copy an API key or access token.
Check Codex
In a terminal, run:
codex mcp list
You should see shopstable in the list. In the Codex terminal interface, type /mcp to see active servers.
Start your first session
Before sending a message, make sure ShopStable is added to this conversation. If you use Codex with a local project open, that project is not the website this connector manages. The Website Assistant works on the draft stored in your ShopStable account; it does not need your website's files or code.
Copy this whole message into a new conversation, replacing the name in brackets:
Use the ShopStable Website Assistant connector for this request. Do not inspect, search, or modify local files, code, or websites on my computer.
Call the ShopStable list_businesses tool first. I want to work on the [business name] website stored in ShopStable. List every page, tell me which one is the home page, and show me which pages are in the navigation. Do not make any changes yet.
When it is working correctly, the assistant names your business, reads its ShopStable draft, lists the pages, and gives you a link to open the Website Builder. You do not need to know page IDs, builder terms, or where anything is stored.
If it starts looking through a local project instead, send this correction:
Stop. This is not a request to inspect local files or website code. Use only the ShopStable Website Assistant connector. Call list_businesses, then show me the pages for [business name] in ShopStable. Do not make changes.
If it still cannot list your ShopStable pages, ShopStable was not added to the conversation. Add it from + → More or @, then send the first message again. Continue with Your First Build.
Having trouble?
If a command such as codex mcp or claude mcp is not recognized, update that client and try again. If a configured server does not appear, start a new conversation (or reopen the CLI or IDE) and check its MCP server list. See Troubleshooting for connection and access issues. During the open beta, you don't need an invitation: a business is available when your role includes website-edit access.