SKU & GTIN Doctor MCP server

Connect Claude, ChatGPT, Gemini, Grok, Cursor, VS Code, and other AI assistants to SKU & GTIN Doctor over MCP. Daily catalog checks for Shopify stores: missing SKUs, invalid or duplicate GTINs, missing prices, weights, and images, in one list with the evidence.

• Server URL: https://skudoctor.agntwrk.com/mcp
• Transport: Streamable HTTP
• Sign-in: OAuth 2.1 in your browser on first use; no API key

Connect your assistant

claude mcp add --transport http skudoctor https://skudoctor.agntwrk.com/mcp

{
  "type": "mcp",
  "server_label": "skudoctor",
  "server_url": "https://skudoctor.agntwrk.com/mcp",
  "authorization": "<access token>"
}

[mcp_servers.skudoctor]
url = "https://skudoctor.agntwrk.com/mcp"

codex mcp login skudoctor

gemini mcp add --transport http skudoctor https://skudoctor.agntwrk.com/mcp

{
  "type": "mcp",
  "server_label": "skudoctor",
  "server_url": "https://skudoctor.agntwrk.com/mcp",
  "authorization": "<access token>"
}

{
  "mcpServers": {
    "skudoctor": {
      "url": "https://skudoctor.agntwrk.com/mcp"
    }
  }
}

{
  "servers": {
    "skudoctor": {
      "type": "http",
      "url": "https://skudoctor.agntwrk.com/mcp"
    }
  }
}

code --add-mcp '{"name":"skudoctor","type":"http","url":"https://skudoctor.agntwrk.com/mcp"}'

npx @modelcontextprotocol/inspector --server-url https://skudoctor.agntwrk.com/mcp --transport http

Tools

• health read-only

  Report that the app is up, its name, and the enabled features.

• whoami read-only

  Return the signed-in user (id, email, name) and the scope (store or tenant) every other tool acts on. Use it to confirm which account an answer is about.

• sync_status read-only

  For each resource this app mirrors from the store (products, inventory, ...): how many objects are mirrored and when the mirror last changed. Use to judge how fresh the data behind findings and product lookups is.

• search_products read-only

  Search the store's mirrored products by a substring of the title, a variant SKU, or a variant barcode (case-insensitive). Returns compact rows, sorted by title, paged with offset. Use get_product for the full record of one.

• get_product read-only

  One mirrored product with all its variants (SKU, barcode, price, weight). Takes the id from search_products, a numeric Shopify id, or a product GID. Reads the mirror, not live store data.

• validate_gtin read-only

  Check a barcode offline: whether it is a valid GTIN (8, 12, 13, or 14 digits with the right check digit), its type, the check digit it should have, and its GTIN-14 form. Spaces and hyphens are ignored. Does not look anything up.

• list_findings read-only

  List the findings (problems the checks found) for this store, newest first. Filter by status, severity, or check id; page with offset. Use findings_summary first for the big picture and get_finding for one finding's evidence.

• get_finding read-only

  Get one finding in full: its evidence, dates, what its check looks for and why it matters, and links to where it can be fixed. Use after list_findings when you need detail.

• findings_summary read-only

  Counts of this store's findings: all by status, and the open ones by severity and by check. Start here to see how bad things are before listing anything.

• list_checks read-only

  List the checks this app can run: id, what each looks for, the plan that unlocks it, and whether it is enabled for this store (a check turned off in the store's settings is not). Use to find a valid check id for run_check or list_findings.

• run_check changes data

  Run one check now for this store and update its findings: new problems are created, fixed ones resolved. Returns how many findings were created, seen again, and resolved. Use run_scan to run every enabled check; do not call this repeatedly.

• run_scan changes data

  Run every enabled check now for this store (as the dashboard's Run checks now button does) and return how many findings were created, how many are reported in total, and how many checks failed. Can take a while; use run_check for one check.

• resolve_finding changes data

  Mark a finding resolved. It reopens by itself if a later scan sees the problem again. Use after the problem is fixed or accepted.

• snooze_finding changes data

  Hide an open finding for a number of days (1 to 365); it reopens after that. Use for problems that will be dealt with later. A resolved finding cannot be snoozed.

• reopen_finding changes data

  Set a snoozed or resolved finding back to open. Use when a problem was closed by mistake or is back.

Prompts

• triage_findings

  Summarize the open findings by severity and propose an order of work.

• explain_finding (id)

  Explain one finding in plain words and say how to fix it.

Things to ask

• Who am I signed in as, and which store are you looking at?
• Find the product with SKU ABC-123 and show its variants.
• Is barcode 4006381333931 a valid GTIN?
• How many open findings do I have, and which are the most severe?
• Show me the evidence for the highest-severity open finding and tell me how to fix it.
• Run all checks and tell me what is new.
• Snooze the low-severity findings for two weeks.