Skip to main content
Glama
510,486 tools. Updated 2026-09-04 04:33

"A server for finding information about Shopify" matching MCP tools:

  • No arguments. Returns how many MCP servers have been read at source level, and the share of them with each category of finding (credential access, network egress, install-time execution, prompt-injection surface). Use this to judge whether checking a specific server is worth it before you look one up. It reports aggregate counts only - no per-server findings, and no verdict about any individual server.
    Connector
  • Hiring velocity across tracked Bitcoin and crypto-infrastructure employers, counted from their live ATS boards. Returns { as_of, companies[], note, why, disclaimer }; each company carries company, ticker, category, ats, careers_url, open_roles, open_roles_30d_ago, open_roles_90d_ago and the derived delta_30d, delta_90d and pct_30d. Example: {"company": "coinbase"} for one employer, or {} for every employer tracked. When a company filter matches no tracked employer the response adds coverage_note and tracked_count, saying that the name is outside the tracked set — a limit of coverage, not a finding about whether that company is hiring. Information, not financial advice.
    Connector
  • List upcoming seller-facing deadlines on Amazon, Shopify and/or TikTok Shop, soonest first. Use for "any Amazon deadlines coming up", "what do TikTok Shop sellers need to do before month end". Deadlines come from curated official announcements (API sunsets, policy compliance dates, fee effective dates); past deadlines are excluded server-side. Free-form deadlines ("rolling") sort after dated ones. Args: platform: Optional platform slug — amazon, shopify or tiktok-shop. Empty = all platforms. Returns {generated_at, as_of, platforms, total, deadlines:[{id, platform, deadline, title, summary, effectiveAt, originalUrl, ...}]}. `as_of` is the server-side cutoff date used. Cite each record's originalUrl.
    Connector
  • Search the web for any topic and get clean, ready-to-use content. Best for: Finding current information, news, facts, people, companies, or answering questions about any topic. Returns: Clean text content from top search results. Query tips: describe the ideal page, not keywords. "blog post comparing React and Vue performance" not "React vs Vue". Use category:people / category:company to search through Linkedin profiles / companies respectively. If highlights are insufficient, follow up with web_fetch_exa on the best URLs.
    Connector
  • Hiring velocity across tracked Bitcoin and crypto-infrastructure employers, counted from their live ATS boards. Returns { as_of, companies[], note, why, disclaimer }; each company carries company, ticker, category, ats, careers_url, open_roles, open_roles_30d_ago, open_roles_90d_ago and the derived delta_30d, delta_90d and pct_30d. Example: {"company": "coinbase"} for one employer, or {} for every employer tracked. When a company filter matches no tracked employer the response adds coverage_note and tracked_count, saying that the name is outside the tracked set — a limit of coverage, not a finding about whether that company is hiring. Information, not financial advice.
    Connector
  • Get detailed information about a specific ad request, including pool selections if targeting mode is manual.
    Connector

Matching MCP Servers

  • F
    license
    A
    quality
    C
    maintenance
    An MCP server that provides information about Utkarsh, including bio, skills, work experience, and portfolio projects, accessible via local stdio or remote HTTP with OAuth.
    6
  • A
    license
    A
    quality
    C
    maintenance
    Enables AI agents to read and write Shopify store data including products, orders, customers, inventory, and more via the Admin GraphQL API.
    28
    82
    MIT

Matching MCP Connectors

  • Shopify MCP Pack — wraps the Shopify Admin REST API (2024-01)

  • Check a product CSV, handles, variant matrices and metafield keys. 4 of 6 free.

  • Create a Shopify-owned cart for selected variant line items through the configured Shopify Cart/Storefront MCP endpoint. Commonlands MCP is a stateless proxy: cart state is stored and mutated by Shopify, not in the Worker. The response includes a cart_access_token that binds the cart to this session; retain it, because get_cart and update_cart refuse to act on the cart without it.
    Connector
  • Get an AGGREGATE Shopify customer count only — a single number, optionally filtered by `query` (Shopify customer search syntax, e.g. "accepts_marketing:true"). Returns NO customer names, emails, addresses, or any other personal data — this tool is aggregate-only by design (PCD Level 2 personal-data reads are deferred). Use when a person or agent needs how many customers exist, never who they are. Routing: Shopify customer count (aggregate only — no PII) from the live store
    Connector
  • List media files (images and generic files) uploaded to the connected Shopify store's file library — alt text and URL. Use to find an existing uploaded asset before uploading a duplicate or referencing one in content. Routing: Shopify file library: uploaded images/files (alt/url) from the live store
    Connector
  • Edit a LIVE Shopify product's title, description, or tags — changes buyers see immediately. Approval-tier with expected_updated_at lock: refuses if the product changed since the edit was reviewed. Use when the operator approves a change to live catalog. Routing: Shopify: edit a LIVE product — approval-tier, lock-checked [outbound-tier — EVERY call needs a manager's approval (per-send human rail): each request queues its own approval card and sends exactly once on approve. There is no standing grant for this tool.]
    Connector
  • Answer one question: can this specific product actually be returned? BEST RESULTS: send the product page you already have as page_text (or page_html) along with product_url — your browser renders JavaScript and is not blocked by retailers, so this works on any store and is faster. Without it we fetch the page ourselves and reach the policy for about 1 in 3 US retailers (17 of 50 measured 2026-08-28; mostly Shopify and direct-to-consumer brands — large retailers and marketplaces block server-side reads). You get a verified verdict — YES / YES_WITH_CONDITIONS / NO / UNKNOWN — with the exact policy clause quoted verbatim, source URL, return window/deadline, fees and a confidence score. Never invents: returns UNKNOWN instead of guessing, and UNKNOWN is free.
    Connector
  • Use this when the question is about the widget itself rather than about accessibility findings: 'is the widget working', 'is it installed', 'why can't I see it', 'did the install work', 'how do I add it', 'is it live for visitors'. Answers with two separate facts that are commonly mistaken for one — whether widget serving is enabled on the Inclusify account (a setting that defaults to ON for every account before anything is installed, so on its own it proves nothing), and whether anything has EVER been reported from the site by the embed itself, which is the only evidence that it is really there. Never report the enabled flag as installation. When nothing has ever reported in, it returns the exact script tag to paste — or, on a Shopify store, says that the widget is a theme app embed which can only be switched on from the Shopify admin, and that no assistant can do that step. What it does NOT do: it does not fetch the customer's site or check the page for the script, so it cannot see an embed that has been installed but not yet visited by anyone. It does not switch the widget on or off, and it reports no accessibility findings — site_overview and the finding tools own those. Works on every plan including Free. Read-only: three indexed reads, no page load.
    Connector
  • Use this when the accessibility problem is in the WORDS a merchant wrote rather than in the theme's code — 'click here' links, unlabelled fields, headings that describe nothing — and a writer or merchandiser will be the one editing it, in the Shopify admin rather than a repo. Problems found in the text of a Shopify store's own content — product descriptions, pages, articles, collections: link text that does not say where it goes, controls with no label, headings that do not describe what follows, tables used for layout, and the structural markup rules that can be decided from the authored HTML. Each finding carries the item it is in, the current text, why it was flagged, a suggested replacement where there is one, how confident the judgement is, and an admin link to the exact place to edit. Do not use it for images or alt text — that is list_alt_findings, and the two never overlap. Only Shopify-connected stores have this data; a site with no store connection returns nothing. Read-only: costs one read and loads no page. An empty result is reported together with whether a content review has ever run, because 'never reviewed' and 'reviewed and clean' are different answers and must not be conflated.
    Connector
  • Get full details for a single business (listing) by its slug. Call this when the user asks for more information about a specific business. Use the slug from search_businesses results.
    Connector
  • Get a ranked list of all detectable platforms and technologies with their domain counts, useful for comparing platform adoption (e.g. how many sites run WordPress vs Shopify)
    Connector
  • Get descriptive project information about a coin: description, links, team and tags. Use for 'tell me about Uniswap', 'what is this project'. Does NOT include price; for price and market cap use getTickersById. Read-only; coinId is a canonical id (resolve with resolveId). No API key required.
    Connector
  • List recent seller-facing changes on Amazon, Shopify and/or TikTok Shop, newest first. Use for "what changed on TikTok Shop recently", "any new Amazon fees", "Shopify API updates this month". Each change is curated from the platform's official changelog/announcement and includes a summary, change type, impact types, effective date and the original source URL. Args: platform: Optional platform slug — amazon, shopify or tiktok-shop. Empty = all platforms. limit: Max changes to return, 1-100 (default 10). Returns {generated_at, source, platforms, total, changes:[{id, platform, publishedAt, title, summary, changeType, topics, impactTypes, effectiveAt, deadline, originalUrl}]}. Cite each record's originalUrl when presenting; mention generated_at if freshness matters.
    Connector