MCP (Model Context Protocol) lets a compatible AI assistant, such as Claude, read and change data in your MogDock workspace on your behalf.

MCP works only when your workspace has MCP access and you have permission for the data and the action. It never goes around workspace boundaries or role permissions.

Who has MCP access

  • During a trial: if Include MCP access in my free trial was ticked on the signup page. Accounts created from inside Shopify do not have this option.
  • On a card-billed paid plan: if you added the paid MCP add-on when you started the plan. Using MCP during the trial does not add it. If you do not add it, your trial MCP access ends when the paid plan becomes active.
  • On a plan billed through Shopify: the MCP add-on is not available yet.

This article does not list prices. The current MCP price is shown when you start your paid plan.

Find the setup page

  1. In the menu, under Help & account, select Profile.
  2. In Connected apps, select MCP setup.

The MCP Setup page shows your MCP server URL, setup steps for common clients, and the tools and resources available to your workspace.

Connect an app

Use this for Claude and other clients that support OAuth.

  1. Copy the Remote MCP server URL from MCP Setup.
  2. Add it in your client's remote MCP or custom connector settings.
  3. Your client opens MogDock in the browser. Sign in, then check the app name, the workspace, and the access it asks for.
  4. Select Allow access.

You do not create or paste a token for this.

To remove an app, open Profile, find it under Connected apps, and select Disconnect. The app loses access to the workspace.

Developer tokens

Developer tokens are the older, manual way to connect. Use one only for a client that cannot complete the sign-in flow above.

  1. Open Profile and go to Developer tokens.
  2. Give the token a name, choose Read, Write, or both, and optionally set Expires at.
  3. Select Generate developer token.
  4. Copy the token straight away. It is shown once and cannot be shown again.

To stop a token, select Revoke token next to it.

Keep tokens safe:

  • Store a token only in the client's secret storage or a protected environment variable.
  • Never paste a token into a support ticket, a chat, a screenshot, or a file that is shared or committed to version control.
  • Choose only the access the client needs.
  • Revoke a token when a device or client is no longer trusted.

What MCP can and cannot do

  • Changes made through MCP still follow your own role permissions.
  • Sensitive values, such as tokens and secrets, are hidden from general reads.
  • Deleting a record needs an exact confirmation.
  • Orders and order lines can be changed only while the order is a draft.

If access is denied, check three things before you create another token: that your workspace has MCP access, that the app or token was given the access it needs, and that your role allows the action. The Access diagnostics section of MCP Setup explains the messages a client can receive.