MCP

Let your AI assistant work directly against your store's live data through the Model Context Protocol (MCP) — no copy-pasting numbers into a prompt.

MCP is free for every Analify account — no plan or connected platform needed. Connect a platform to work with its data.

Analify exposes 5 MCP servers: one unified server covering every platform you've connected, and 4 single-platform servers if you'd rather scope a client to one connection at a time.

A server only returns data for platforms you've actually connected — the unified server doesn't require all four; it uses whichever you have.

Installation

Each entry is one URL. The unified server is https://analify-mcp.scalyax.ai/. For a single-platform server, add its name to the path: /shopify, /meta, /tiktok or /bosta.

Claude Code

claude mcp add --transport http analify https://analify-mcp.scalyax.ai/

Start a session, type /mcp, select the server, and authorize.

Cursor — add to .cursor/mcp.json:

{
  "mcpServers": {
    "analify": { "url": "https://analify-mcp.scalyax.ai/" }
  }
}

VS Code — add to .vscode/mcp.json:

{
  "servers": {
    "analify": { "type": "http", "url": "https://analify-mcp.scalyax.ai/" }
  }
}

Windsurf — add to ~/.windsurf/mcp.json:

{
  "mcpServers": {
    "analify": { "url": "https://analify-mcp.scalyax.ai/" }
  }
}

Claude Desktop — via mcp-remote, in claude_desktop_config.json:

{
  "mcpServers": {
    "analify": { "command": "npx", "args": ["mcp-remote", "https://analify-mcp.scalyax.ai/"] }
  }
}

ChatGPT — Settings → Apps & Connectors → Create connector, authentication OAuth, URL https://analify-mcp.scalyax.ai/. Requires a Pro, Plus, Business, Enterprise or Education account.

Gemini — in Gemini's connected apps settings, add a custom MCP server and paste https://analify-mcp.scalyax.ai/.

Grok — at grok.com/connectors choose New Connector → Custom and paste https://analify-mcp.scalyax.ai/. Custom connectors need a paid Grok plan.

Any other MCP client that speaks Streamable HTTP can point at the same URL — OAuth discovery is automatic.

Authorizing

Your client opens a browser window. There's no account picker — sign in, and it authorizes against the Shopify (or platform) account you've already connected in Settings → Integrations. If you're not signed in, it takes you to login first.

Access lasts 7 days, refreshed automatically for 30 days after that — most clients handle the refresh silently.

If you belong to more than one organization, MCP authorizes against the
first connected account it finds for that platform — keep one connection per
platform per login until an explicit account picker ships.

OAuth and permissions

Analify's MCP servers use standard OAuth for remote MCP clients.

Scopes

Read and write access

Every connection starts read-only.

1. Analify exposes reads and writes as two separate tools. The read tool refuses any mutation and the write tool refuses any read.
2. Write access is not granted by requesting a scope. The Analify consent screen has a write-access checkbox that is off by default. Your choice is sealed into the token, so a client cannot upgrade itself later.
3. Write tools are marked as destructive in the MCP tool metadata, so compliant clients ask you to confirm each action before it runs.
4. If you never tick the checkbox, your assistant can read your numbers and cannot change anything.

To change your choice, remove the connection and authorize again.

Requirements

• An Analify account. MCP is free for every account.
• The unified server works with nothing connected (Business Brain and product costs). Platform data appears once you connect Shopify, Meta Ads, TikTok Ads or Bosta in Settings → Integrations; a single-platform server needs its own platform connected.
• Data is read live from your connected platforms, so their rate limits apply (Meta's in particular).

Managing your connection

Re-authenticate — if a token expires or stops working, remove and re-add the
server:

claude mcp remove analify
claude mcp add --transport http analify https://analify-mcp.scalyax.ai/

Refreshing tools — clients cache the tool list on connect. Start a new
session to pick up anything added since.

What's in each server

The Meta server targets Marketing API v25.0 and mirrors the official
ads_* / ads_insights_* tool names as aliases — so an AI trained on Meta's
own docs finds our tools too — alongside 100+ Analify-only tools the official
server doesn't have (catalog management, split testing, WhatsApp ads, async
reports).

Your client fetches the live tool list on connect, so it always matches
what's actually available for your connected platforms — this table is a
summary, not a schema.

Response handling

• Errors come back as a tool result, not a broken connection. A failed
  call returns isError: true with the upstream message, so your assistant
  can read it and try something else rather than the session dying.
• A platform's tools say it is not connected? Connect it in Settings → Integrations — the rest of MCP keeps working meanwhile.
• A 401 means re-authenticate — your client should prompt you
  automatically.

Next

See it in action: MCP examples — real prompts you can paste in
once you're connected.