Claude Code

Claude Code connects over HTTP with a header, so no bridge and no Node.js setup is needed.

Add the server

Open a terminal on the machine where Claude Code is installed and run:

claude mcp add --transport http aov-bundle \
  https://avada-bundle-upsell.firebaseapp.com/mcp \
  --header "Authorization: Bearer aovmcp_YOUR_TOKEN"

Copy the snippet generated in Settings → Developer Tools instead of typing this by hand: it already carries the right URL and token.

Restart Claude Code afterwards.

Running more than one store? Change aov-bundle to a name of your own, one per store. Two entries with the same name overwrite each other silently.

The command puts the token in your shell history. If that matters on this machine, clear the entry afterwards, or paste the snippet rather than typing it.

Check it worked

Run /mcp inside Claude Code. The server should be listed as connected, with 14 tools if the token is Read-only, or 26 if it is Read and write.

Then ask:

Are my bundles showing on the storefront right now?

If the server is listed but the question comes back refused, the URL is right and the token is not, see Troubleshooting.

Asking it to create or change an offer only works on a token created with Read and write access. A Read-only token refuses with "This connection is read-only."

Scope

By default the server is added for the current project. To use it from any directory, add --scope user:

claude mcp add --transport http aov-bundle --scope user \
  https://avada-bundle-upsell.firebaseapp.com/mcp \
  --header "Authorization: Bearer aovmcp_YOUR_TOKEN"

A project-scoped entry lives in that project's config, which is often under version control. User scope keeps the token out of it.

Remove or replace

claude mcp remove aov-bundle

Then add it again. Editing the entry in place can leave the old credential attached.

Removing the server locally does not revoke the token: do that in Settings → Developer Tools.

Claude web & desktop Cursor