Shopify MCP server

AutoAdy uses Shopify as a revenue source for Meta ad attribution. It is not a Shopify MCP server, and nothing here can change a store.

Last updated: September 24, 2026

Meta reports the conversions it believes it caused. A store reports the orders that actually happened. When those two disagree, and they always do, the argument is settled by reading the store.

That is what AutoAdy's Shopify integration is for. It reads orders and customer events through Shopify's own app authorisation, attributes them to Meta ads, and answers reporting in revenue rather than in platform-reported conversions. Access is read plus the web pixel; AutoAdy never writes a product, a collection, a metafield or a price.

None of it is exposed as MCP tools. The connector serves Meta ads, Google Ads, website installation and conversion-tracking health. There is no Shopify tool to call and this page does not imply one.

Coverage

What AutoAdy does here, and where the line is

Capability	In the AutoAdy app	Through the MCP connector
Connect a Shopify store	Yes, per ad account, through Shopify's app authorisation.	No tool.
Read orders and revenue	Yes. Orders are synced and attributed to Meta ads.	No tool.
Customer events from the storefront	Yes, through a Shopify web pixel.	No tool.
Changing anything in the store	Not built, and deliberately out of scope. Read plus attribution only.	No tool.
GDPR and data-deletion webhooks	Yes. The three Shopify compliance topics are answered and HMAC-verified.	Not applicable.
Meta ads, in the same assistant	Yes.	Yes. 109 tools, listed on the Meta Ads connector page.

Point any MCP client at https://www.autoady.io/api/mcp and read the tools list. That is the whole set, and this table is what it means for this platform.

Connect

Two controls, then ask it something

Claude (claude.ai)

Signs in with OAuth

Opens Claude's add-custom-connector dialog with the name and URL already filled in. Claude still asks you to press Add, then signs you in to AutoAdy with OAuth.

Add AutoAdy to Claude (claude.ai)

If you would rather do it by hand: Settings, Connectors, Add custom connector, and paste this.

https://www.autoady.io/api/mcp

Claude Code

Needs an API key

Paste into your terminal, then run /mcp to confirm autoady is connected.

claude mcp add --transport http autoady https://www.autoady.io/api/mcp --header "Authorization: Bearer YOUR_KEY"

Replace YOUR_KEY with a key from Settings, API Keys. Keys are shown once and can be revoked at any time.

Everywhere else

Claude Desktop

Needs an API key

Open the downloaded file and Claude Desktop installs the extension, including the interactive views.

Download the extension

Or edit claude_desktop_config.json by hand and restart Claude Desktop.

{
  "mcpServers": {
    "autoady": {
      "type": "http",
      "url": "https://www.autoady.io/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_KEY"
      }
    }
  }
}

Replace YOUR_KEY with a key from Settings, API Keys. Keys are shown once and can be revoked at any time.

ChatGPT

Signs in with OAuth

Availability depends on your ChatGPT account and workspace policy. ChatGPT's custom MCP connections use OAuth and cannot present your manual API key. See Settings → Agents for current steps and the conditional OpenAI dot path.

Create a custom MCP connection in ChatGPT developer mode, paste this URL and sign in to AutoAdy through OAuth. Choose dynamic client registration (DCR) if prompted.

https://www.autoady.io/api/mcp

Grok

Signs in with OAuth

Grok web, Grok Build and Grok Bot have different setup flows. These artifacts cover web and Build. Settings → Agents documents the conditional Grok Bot path with official sources; live client sign-in has not been tested here.

On grok.com/connectors, choose New Connector → Custom, paste this URL and complete AutoAdy account sign-in.

https://www.autoady.io/api/mcp

For Grok Build: add the remote server, authenticate when prompted and check grok mcp doctor autoady.

grok mcp add --transport http autoady https://www.autoady.io/api/mcp

Muse Code

Signs in with OAuth

This configuration is for Meta's Muse Code. It does not establish custom connector support in the personal Muse app. Settings → Agents explains the distinction and links Meta's exact configuration and OAuth documentation.

Add this hosted endpoint to your Muse Code user settings, then run muse mcp login autoady.

https://www.autoady.io/api/mcp

Merge into ~/.config/muse/settings.json, preserving your settings. Keep one root MCP spelling and start a new Muse Code process after editing.

{
  "schema_version": 1,
  "mcpServers": {
    "autoady": {
      "type": "streamable-http",
      "url": "https://www.autoady.io/api/mcp"
    }
  }
}

Cursor

Needs an API key

Paste into Cursor's MCP settings, then reload the window.

{
  "mcpServers": {
    "autoady": {
      "type": "http",
      "url": "https://www.autoady.io/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_KEY"
      }
    }
  }
}

Replace YOUR_KEY with a key from Settings, API Keys. Keys are shown once and can be revoked at any time.

VS Code

Needs an API key

Paste into your MCP servers settings and reload the window.

{
  "servers": {
    "autoady": {
      "type": "http",
      "url": "https://www.autoady.io/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_KEY"
      }
    }
  }
}

Replace YOUR_KEY with a key from Settings, API Keys. Keys are shown once and can be revoked at any time.

Step by step

How to connect Claude to Shopify through AutoAdy

1
Know what you get
Connecting AutoAdy to your assistant gives it Meta ads tools. There are no Shopify tools. If you want a store in the chat, read the alternatives below.
2
Connect the store in AutoAdy
Open autoady.io, go to Settings, and link the Shopify store to the ad account it sells for. The app requests read access to orders and customer events, plus the web pixel scope.
3
Let the orders sync
AutoAdy reads orders and customer events and attributes them back to Meta ads, so revenue and blended return sit next to platform-reported conversions.
4
Add the connector for the Meta half
On claude.ai, Settings, Connectors, Add custom connector, and paste https://www.autoady.io/api/mcp. Your assistant gets the Meta account.

What it costs

Reading is free. Changing your account is not.

Read tools change nothing and work on the free plan, with these exceptions: diagnose_drop needs a Solo, Growth or Agency plan; run_gaql and run_graph_read are not available on the free plan; and a free key can call analyze_winning_ad 25 times a day, because it reaches a language model. Every other read is unmetered.
A free key is read-only: every write tool needs a paid plan (Solo, Growth or Agency), including tools that only change AutoAdy such as switch_account and prepare_website_installation. On a free key they refuse with a message naming the upgrade.
Clients with MCP account sign-in can use OAuth without creating a key. Other clients send an AutoAdy key in an Authorization header. Follow the client-specific steps in Settings → Agents.
New AutoAdy accounts start a seven-day trial with 50 credits for a $1 setup fee. A card is required for the trial, and cancelling before it ends means the subscription never starts. See pricing.
Advertising spend is paid to the ad platform directly and is separate.

The alternatives

What else you could use

Alternative	What it is	Where it beats AutoAdy	Where AutoAdy is the better choice
Shopify's own MCP server	Shopify publishes MCP endpoints for storefront and admin data, so an assistant can query and, with the right scopes, change a store.	It is the store, from the vendor, with the whole Admin API behind it. If you want to ask about inventory, edit a product, or read a customer record from the chat, this is the right tool and AutoAdy is not.	Nothing, on store data. AutoAdy's claim is narrower: it joins store revenue to Meta ad spend so the return number is real, which a store-only connector cannot do because it cannot see the ad account.
Shopify's own analytics and the Meta sales channel	Shopify reports on sessions and orders; the Meta sales channel pushes a pixel and a catalogue and reports attributed sales.	Free, already installed, and the numbers come straight from the two systems involved with nobody in the middle.	Each side reports its own version and neither reconciles them. AutoAdy holds both datasets and can say, per ad, what the store recorded against what Meta claimed.
A spreadsheet export from Shopify plus the Ads Manager export	Two CSVs, joined by hand or by an assistant reading both files.	It genuinely works, costs nothing, and every number is auditable because you are looking at the raw rows.	It is manual, it goes stale immediately, and the join key is whatever you improvise. It is also not a thing your assistant can refresh on its own.

We sell one of the options in that table, so the column that cost us something to write is the third one. If a row is wrong or out of date, tell us and we will correct it.

Where AutoAdy falls short here

Limits worth knowing before you connect anything.

−No Shopify tools over MCP. A tools/list call names no Shopify tool.
−No store writes of any kind. Products, collections, metafields, prices and inventory are out of scope by design.
−The store connects per ad account, not per workspace. An agency with one store across several ad accounts links it more than once.
−Attribution covers Shopify. Other commerce platforms are not read.
−Reporting is Meta-first. Store revenue is joined to Meta spend, not to Google Ads spend.

FAQ

Common questions

Does AutoAdy have a Shopify MCP server?

No. AutoAdy's MCP connector serves Meta ads and Google Ads tools plus web analytics installation and conversion-tracking health. Shopify is an attribution source inside the AutoAdy app. Point any MCP client at https://www.autoady.io/api/mcp and read the tools list to confirm it.

What Shopify access does AutoAdy ask for?

Read access to orders, permission to install a web pixel, and read access to customer events. That is the whole scope set. It cannot edit products, prices, inventory or collections, because it never asks for permission to.

Why connect a store at all?

So the return number is real. Meta reports the conversions it believes it caused; the store reports the orders that happened. Holding both is the only way to answer, per ad, which one to trust.

What should I use instead for store data in my assistant?

Shopify's own MCP server. It is the vendor's, it covers the Admin API, and it is the right tool for asking a store questions. AutoAdy is the right tool for asking which ads paid for the orders.

Try it on your own account

Connect the account, ask your assistant what is wrong with it, and read the evidence behind the answer before anything changes.

Start free See how it works

Shopify MCP server

What AutoAdy does here, and where the line is

Two controls, then ask it something

Claude (claude.ai)

Claude Code

Everywhere else

Claude Desktop

ChatGPT

Grok

Muse Code

Cursor

VS Code

How to connect Claude to Shopify through AutoAdy

Know what you get

Connect the store in AutoAdy

Let the orders sync

Add the connector for the Meta half

Reading is free. Changing your account is not.

What else you could use

Where AutoAdy falls short here

Common questions

Does AutoAdy have a Shopify MCP server?

What Shopify access does AutoAdy ask for?

Why connect a store at all?

What should I use instead for store data in my assistant?

The full tool catalogue

Meta Ads MCP server

Web analytics MCP server

Google Ads MCP server

Try it on your own account