Get started

Build and Manage Your Store with Sellavi MCP

Sellavi MCP lets an AI assistant help set up and manage your store through a secure connection. It can inspect your current progress, prepare branding, create categories and products, customize your storefront, preview changes, and help you continue to payment setup.

The MCP server is hosted by Sellavi. You do not need to install a server, create an API token, or tell the AI your company ID.

MCP URL: https://api.sellavi.com/mcp

Sellavi uses OAuth. During connection, you sign in to Sellavi and approve access. The connection then identifies the correct store automatically.

Quick Start with Claude

1. Add Sellavi as a custom connector

For an individual Claude account:

Open Claude.
Go to Customize → Connectors.
Select + → Add custom connector.
Enter a name such as Sellavi.
Enter this remote MCP URL:

Code(text)
 
https://api.sellavi.com/mcp

Save the connector.
Select Connect next to Sellavi.
Sign in to your Sellavi account.
Review the requested permissions and approve only if they match what you want Claude to do.

For Claude Team or Enterprise, an Owner or Primary Owner must first add the connector under Organization settings → Connectors. Each team member can then connect their own Sellavi account.

Do not paste a Sellavi password, API token, access token, or OAuth code into a Claude message. Authentication happens in the Sellavi sign-in and consent pages.

2. Enable Sellavi in the conversation

In a new Claude chat:

Select the + button beside the message box.
Open Connectors.
Enable Sellavi for this conversation.

A connector may be installed but disabled in a particular chat. If Claude says it cannot find Sellavi tools, check this toggle first.

3. Start store setup

From your Sellavi dashboard, select Build your store with Claude. Claude opens with a prepared onboarding request. Review it and send it.

You can also paste this example:

Code(text)
 
Start my Sellavi store setup.
Inspect my current onboarding progress and existing brand information first.
Continue from the next incomplete step.
Ask only for information that is missing, and ask before live changes or AI credit usage.

The dashboard button starts the chat; it does not install the connector. Complete steps 1 and 2 once before using the button.

What Happens Next

For a full store launch, Claude should work in this order:

Inspect existing onboarding progress and store details.
Check whether a real logo already exists.
Keep, upload, generate, or skip the logo based on your choice.
Check existing banners before offering to replace them.
Prepare categories and products.
Show a temporary storefront preview link.
Hand off payment setup to the Sellavi dashboard.

Claude should use existing business name and selling information from Sellavi when available. It should not ask you to repeat known details.

Approvals that remain yours

Claude must ask before actions such as:

Replacing or deleting existing banners.
Generating Sellavi AI images that consume credits.
Creating a large product catalog.
Publishing live theme changes.
Deleting products, categories, or options.
Rolling back a storefront version.

Read every approval request before allowing it.

Useful Prompt Examples

Continue onboarding

Code(text)
 
Continue setting up my Sellavi store.
Check what is already complete and take me to the next unfinished step.
Do not replace existing brand assets without asking me.

Create a small catalog

Code(text)
 
Help me create a catalog for handmade candles.
First show me the proposed categories and five products with names, descriptions, prices, and image requirements.
Wait for my approval before creating anything in Sellavi.

Import from a file

Code(text)
 
I will upload a CSV containing my products.
Validate the rows, show missing required fields, and propose category mapping.
Wait for approval before creating categories or products.

Redesign the storefront

Code(text)
 
Give my storefront a clean, premium look using my existing logo and brand colors.
Inspect the current theme first, create a rollback snapshot, explain the planned changes, and wait for approval before publishing.
Check both desktop and mobile after publishing.

Undo a theme change

Code(text)
 
List my recent storefront snapshots.
Explain which version was created before the last design change, then ask for confirmation before rolling back.

Claude Code Setup

Add the hosted server for your user account:

Code(bash)
 
claude mcp add --transport http --scope user sellavi https://api.sellavi.com/mcp

Verify it was added:

Code(bash)
 
claude mcp list

Start Claude Code and enter:

Code(text)
 
/mcp

Choose Sellavi and follow the browser sign-in flow. After authentication, use any prompt from this page.

Do not add a manual Authorization header. The OAuth client obtains and refreshes the connection token.

Other MCP Clients

Use these values in any client that supports remote Streamable HTTP MCP and OAuth:

Field	Value
Name	`Sellavi`
Transport	Streamable HTTP / HTTP
URL	`https://api.sellavi.com/mcp`
Authentication	OAuth

The client must support OAuth discovery, dynamic client registration, and PKCE. Normally you enter only the MCP URL; the client discovers the Sellavi authorization endpoints.

If a client supports only static API keys or custom headers, use Claude or another OAuth-capable MCP client instead. Do not copy browser cookies or OAuth tokens into a client configuration.

Troubleshooting

Problem	Fix
Connector is installed, but Claude cannot use Sellavi	Enable Sellavi from + → Connectors in the current chat, then retry.
Sign-in page keeps appearing	Sign in with the Sellavi user that owns the store, then return to the OAuth flow.
`401 Unauthorized`, `Invalid token`, or `Token expired`	Disconnect Sellavi in Claude, reconnect it, and complete sign-in again.
Claude shows an old or incomplete tool list	Disable and re-enable the connector, reconnect it, then start a new chat.
Wrong store is connected	Disconnect Sellavi and reconnect while signed in to the correct Sellavi account.
Team member cannot add a connector	Ask a Claude organization Owner or Primary Owner to add it first.
Claude asks for `companyId`	Tell it to use the authenticated Sellavi connection and call `create_launch_plan` first.
Claude asks for an API token	Stop. Tokens belong in the OAuth flow, never in chat. Reconnect the connector.
AI generation is still processing	Wait. Logo generation may take several minutes; banner generation can take longer. Do not start another paid generation while one is running.
A live theme change looks wrong	Ask Claude to list snapshots and request confirmation before rollback.

When reporting a server error to Sellavi support, include the displayed request_id, but never include credentials.

Security and Safe Use

Connect only to https://api.sellavi.com/mcp.
Review OAuth permissions before approving access.
Keep passwords, tokens, and authorization codes out of chat and screenshots.
Review tool approval details, especially for writes and deletions.
Require a rollback snapshot before storefront code changes.
Disconnect Sellavi from Claude when you no longer want it available.

For current Claude connector UI details, see the official Claude custom connector guide.

Expected Agent Behavior

An AI agent using Sellavi MCP should:

Last modified on 16 August 2026

Modules API