Dashboard

Core Concepts

Understand the three separate trust layers behind SHOPMCP: your account, your Shopify store, and Claude access.

SHOPMCP is easier to understand when you do not think of it as one big login. It is three separate trust layers working together.

Each layer answers a different question:

  1. Who is the user?
  2. Which Shopify store is connected?
  3. Can Claude act for this user on this store?

This separation is what lets SHOPMCP support teams, audit logs, revocation, and confirmation before sensitive actions.

The core idea

Your dashboard login, Shopify connection, and Claude authorization are separate on purpose. One proves who you are, one connects the store, and one allows Claude to use the connector for a specific person.

The trust model

Your account

Who are you?

Email/password or Google login

Store connection

Which store?

Shopify OAuth approval

Claude access

Can this person act now?

Hydra login and consent

Claude can now act

Only for this person, this store, and the approved scope.

The flow looks like this:

  1. A merchant signs in to SHOPMCP.
  2. The merchant connects a Shopify store.
  3. Claude Desktop connects to the SHOPMCP MCP server.
  4. SHOPMCP checks whether the current user is allowed to use that store.
  5. Claude can then call Shopify tools through SHOPMCP.

Claude does not receive your Shopify password or raw store credentials. It talks to SHOPMCP, and SHOPMCP enforces the workspace rules.

Layer 1: Your SHOPMCP account

Your SHOPMCP account answers one question: who are you?

This is the login you use for the dashboard. Every owner and teammate should have their own account. Do not share one login across the team.

Separate accounts matter because every action can be tied back to a real person. If Claude prepares a refund, updates inventory, or reads customer data, the activity log can show which user initiated it.

Why not use one shared login?

Shared logins make audit trails weak. With separate accounts, access can be granted, reviewed, and removed per person.

Layer 2: Your Shopify store connection

The Shopify store connection answers: which store is SHOPMCP allowed to access?

This happens when the store owner connects Shopify from the dashboard. Shopify shows an authorization screen, and the owner approves the requested permissions.

After approval, SHOPMCP stores the store connection securely. Your team members do not need your Shopify password, and they do not need to reconnect Shopify when they join the workspace.

In practice:

  • Store connection usually happens once per store.
  • New teammates use the existing workspace connection.
  • Disconnecting the store stops Claude from using Shopify tools for that store.

Layer 3: Claude authorization

Claude authorization answers: can this person use Claude with this Shopify workspace right now?

This is separate from the Shopify connection. The first time Claude Desktop uses the connector, SHOPMCP checks the signed-in user and asks for approval.

That approval lets Claude call SHOPMCP tools for that user and workspace. If the user is removed from the team, future access is blocked. Any already-issued short-lived token may continue only until it expires.

Why the layers are separate

Clear identity

Every teammate has their own account, so activity can be tied to the person who asked Claude to act.

One store connection

The owner connects Shopify once. Teammates can be invited without sharing Shopify credentials.

Revocable Claude access

Claude access is checked per user, so removing someone from the team stops future connector access.

Example: teammate access

Imagine the store owner connects Shopify, then invites an operations teammate.

The teammate does not need Shopify admin credentials. They sign in to SHOPMCP with their own account, open Claude Desktop, approve connector access, and ask Claude for operational help.

If that teammate later leaves the company, the owner removes them from the team. Their dashboard access is removed, and future Claude authorization is blocked for that workspace.

Example: Claude prepares a change

When Claude needs to perform a sensitive action, such as adjusting inventory or preparing a refund, SHOPMCP can stage the action and ask for confirmation.

That gives you a safer pattern:

  1. Claude explains the action it wants to take.
  2. SHOPMCP shows what will change.
  3. A permitted user confirms or rejects it.
  4. The final action is logged.

This is the difference between giving Claude direct store control and giving Claude controlled operational access through a governed connector.

Use these pages based on what you want to understand next:

Was this page helpful?

Your feedback helps keep this documentation accurate and useful.

On this page