Skip to main content
Glama
649,985 tools. Updated 2026-10-10 06:12

"BigCommerce" matching MCP tools:

  • List verified UCP storefronts across every platform, best-evidenced first. Use when the user wants to browse stores — e.g., "what stores can I shop at?" or "show me Wix stores". To find stores that sell something, prefer search-all. Each store carries what we have actually observed about it, not what it claims: - `transactable` — declares checkout and we have read its catalogue - `catalogued` — we have read its catalogue - `resolvable` — its endpoint resolves, we have not probed it yet - `declared` — a valid manifest, nothing observed beyond it Filter by `platform` (shopify, wix, woocommerce, bigcommerce, shopware…). `category` narrows to the smaller set of deeply audited stores (see list-categories), so leave it out unless the user asks for a category. Developer previews and staging hosts are not listed.
    ConnectorNo auth
  • Pushes the current content of a published (or published-in-draft) article to every connected CMS, clearing its Out of Sync state. Synchronous: returns once the CMS accepted the update (a few seconds; Shopware, Umbraco and BigCommerce finish in the background). Fails for articles that are not on a CMS yet: publish those with publish_article. Framer and webhook connections are never synced. Pass website_id when the account has several websites (see get_account).
    ConnectorOAuth
  • Explain ONE mined opportunity: return its support, confidence, lift, and order sample count plus a short plain-language narrative of why the pair is a good cross-sell. Use this when a merchant asks 'why is this a good cross-sell?', 'explain this opportunity', or 'why should I bundle these?' after seeing it in get_opportunities. Different from get_opportunities: that lists the ranked set, this drills into a single opportunity_id with the stats spelled out in a sentence. Different from get_rationale: rationale is a generic pair 'why', this is the specific mined opportunity's own numbers. BigCommerce only today.
    ConnectorNo auth
  • Explain ONE drift alert: return its prior and current confidence (plus support, lift, and order sample count when the rule is still live) and a short plain-language narrative of how the pair moved versus the prior mining run. Use this when a merchant asks 'why did this pair drift?', 'explain this alert', or 'what changed for these two products?' after seeing it in get_drift_alerts. Different from get_drift_alerts: that lists the feed, this drills into a single alert_id with the change spelled out in a sentence. Handles a disappeared pair gracefully (only the prior confidence is available). BigCommerce only today.
    ConnectorNo auth
  • Returns one page or Insights article from projectthunder.com as Markdown: title, URL, summary and the full content. Accepts a full URL (https://www.projectthunder.com/bigcommerce-sap-integration.html) or a path (/bigcommerce-sap-integration.html). A URL on projectthunder.mx, pt.projectthunder.com or projectthunder.asia returns that language's page.
    ConnectorNo auth
  • For a sales-rep or inventory / account-management agent: predict when a B2B customer / account is due to reorder. Returns predicted next-order dates for every SKU the customer has ordered >=2 times, with confidence based on the regularity of their cadence (reorder prediction / replenishment forecasting). Bucketed into 'overdue' / 'due_soon' / 'on_track' / 'not_predictable'. Use this when the agent asks 'what's Acme Corp due to reorder?', 'when will customer X need more of Y?', 'show me stockout risks for my B2B accounts', or for proactive replenishment workflows. Works on the Shopify, BigCommerce, WooCommerce, and Magento backends. Not available on OroCommerce.
    ConnectorNo auth

Matching MCP Servers

  • Returns normalized product detail from a public BigCommerce storefront product page. url must be the full public product-page URL for a BigCommerce Stencil storefront. Use bigcommerce_search to search a BigCommerce storefront.
    ConnectorNo auth
  • Returns one normalized product-search page from a public BigCommerce storefront. url must be the public storefront origin; an optional caller path or query is ignored. q is required search text. page is 1-indexed and defaults to 1. Use bigcommerce_category to browse a BigCommerce storefront category.
    ConnectorNo auth
  • Returns normalized product detail from a public BigCommerce storefront product page. url must be the full public product-page URL for a BigCommerce Stencil storefront. Use bigcommerce_search to search a BigCommerce storefront.
    ConnectorNo auth
  • Returns one normalized product-search page from a public BigCommerce storefront. url must be the public storefront origin; an optional caller path or query is ignored. q is required search text. page is 1-indexed and defaults to 1. Use bigcommerce_category to browse a BigCommerce storefront category.
    ConnectorNo auth
  • For an ERP (and optionally a version and an e-commerce platform), returns how it integrates with Sana Commerce Cloud, BigCommerce, DynamicWeb or Wardenclyffe, version notes such as end-of-support dates, what to settle first, the guides that cover it, and implementation partners in ProjectThunder's ERP partner directory. Every point carries the URL of the page it comes from. Examples: "Business Central", "Dynamics GP 2018", "SAP Business One", "NAV 2009 R2".
    ConnectorNo auth
  • Search the pages on projectthunder.com: services, platform guides (BigCommerce, Sana Commerce, DynamicWeb), ERP integration guides (SAP, Business Central, Dynamics GP, NAV, AX, Epicor), comparisons, Insights articles, the ERP partner directory and partner profiles. Returns the best matches with a snippet. Use get_page to read a result in full. English by default; set language for the Spanish, Portuguese or Chinese site.
    ConnectorNo auth
  • Creates B2B audiences based on technology stack, software usage, and firmographic attributes. ESTIMATE-ONLY MODE: Pass estimate_only=true to preview audience size (companies + contacts) WITHOUT creating the audience. In this mode the tool returns expectedNumberOfCompanies, expectedNumberOfContacts, and cappedContactCount. Default is false (audience is created). WHEN TO USE: - Target companies using specific technologies or software - Create audiences based on technology adoption patterns - Target by technology categories (CRM, Marketing Automation, Analytics, etc.) - Combine technology targeting with firmographic filters - Build tech-savvy audience segments for B2B campaigns - User wants to target companies and contacts that are familiar/using some specific software like hubspot, g2, etc. TECHNOLOGY CATEGORIES: - CRM: Salesforce, HubSpot, Microsoft Dynamics, Zoho, Pipedrive - Marketing Automation: Marketo, Pardot, Eloqua, HubSpot, Mailchimp - Analytics: Google Analytics, Adobe Analytics, Mixpanel, Amplitude - E-commerce: Shopify, Magento, WooCommerce, BigCommerce - Content Management: WordPress, Drupal, Joomla, Adobe Experience Manager - Collaboration: Slack, Microsoft Teams, Zoom, Asana, Monday.com - Cloud Infrastructure: AWS, Azure, Google Cloud, Oracle Cloud - Database: MySQL, PostgreSQL, MongoDB, Oracle, SQL Server - And many more technology categories available FIRMOGRAPHIC FILTERS (OPTIONAL): - Industries: Use industry IDs (1-148, same as firmographic audiences) - Employees: "LESS_THAN_10", "FROM_10_TO_50", "FROM_50_TO_200", "FROM_200_TO_500", "FROM_500_TO_1000", "FROM_1000_TO_5000", "FROM_5000_TO_10000", "OVER_10000" - Revenue: "LESS_THAN_1M", "FROM_1M_TO_10M", "FROM_10M_TO_50M", "FROM_50M_TO_100M", "FROM_100M_TO_200M", "FROM_200M_TO_500M", "FROM_500M_TO_1000M", "OVER_1000M" CONTACTS CRITERIA: Use the following parameters to filter and target specific contacts within accounts: GEOGRAPHIC TARGETING: - location_country_ids: Array of country IDs (e.g., [29] for Brazil, [229] for United States) - location_state_ids: Array of state IDs (e.g., [5] for California, [32] for New York) JOB TITLES: - job_title_includes: Array of free text strings to include (e.g., ["Software Engineer", "Manager"]) - job_title_excludes: Array of free text strings to exclude (e.g., ["Senior", "Lead"]) JOB FUNCTIONS: Valid job function IDs and their labels: - 1: Marketing, 2: Sales, 3: Customer Service, 4: Finance, 5: Human Resources, 6: Public Relations - 7: Media, 8: Design, 9: Engineering, 10: Operations, 11: Legal, 12: Education - 13: Health, 14: Real Estate, 15: Accounting, 16: Administrative, 17: Business Development - 18: Community and Social Services, 19: Consulting, 20: Entrepreneurship, 21: Information Technology - 22: Military and Protective Services, 23: Product Management, 24: Program and Project Management - 25: Purchasing, 26: Quality Assurance, 27: Research, 28: Trades - job_function_include_ids: Array of job function IDs to include (e.g., [9] for Engineering) - job_function_exclude_ids: Array of job function IDs to exclude SENIORITY LEVELS: Valid seniority IDs and their labels: - 2: Manager, 3: Director, 4: VP, 5: CXO, 6: Unpaid, 7: Training - 8: Senior, 9: Owner, 10: Entry, 11: Partner - seniority_include_ids: Array of seniority level IDs to include (e.g., [10, 7] for Entry and Training) - seniority_exclude_ids: Array of seniority level IDs to exclude CONTACT LIMITS: - contacts_per_company_limit: Maximum number of contacts to target per company (optional). Example: 20 USAGE NOTES: - All ID fields (countries, states, job functions, seniorities) use numeric IDs from the platform - Job titles are free text strings, not IDs - Use include parameters to specify which criteria to target - Use exclude parameters to filter out contacts matching specific criteria - Combine multiple criteria for precise targeting (e.g., Senior Engineers in California) - Criteria are combined with AND logic, so all conditions must be met CONTACTS CRITERIA PARAMETERS(Usually after other initial audience parameters to be described next): - location_country_ids: Array of country IDs (optional) - location_state_ids: Array of state IDs (optional) - job_title_includes: Array of job title keywords to include (optional) - job_title_excludes: Array of job title keywords to exclude (optional) - job_function_include_ids: Array of job function IDs (optional) - job_function_exclude_ids: Array of job function IDs (optional) - seniority_include_ids: Array of seniority level IDs (optional) - seniority_exclude_ids: Array of seniority level IDs (optional) - contacts_per_company_limit: Maximum contacts per company (optional) PARAMETERS: - name: Audience name (required) - **IMPORTANT: Name MUST NOT exceed 50 characters. This is a mandatory requirement.** - technologies: Array of technology names (required) - industries: Array of industry IDs (optional) - employees: Array of employee count ranges (optional) - revenue: Array of revenue ranges (optional) RETURNS: Audience details with ID, size estimation, and creation status, plus `technologies_requested`, `technologies_targeted` (the indexed names actually sent) and `technology_resolution`. COMMON USE CASES: - Target companies using Salesforce and HubSpot - Find AWS users in the software industry - Build audiences of companies using specific MarTech stacks - Combine technology and firmographic targeting for precise B2B campaigns IMPORTANT NOTES: - **CRITICAL: Audience name MUST NOT exceed 50 characters - this is mandatory and will cause creation to fail if exceeded** - name and technologies are required parameters - All other parameters are optional for flexible audience creation - Technology names are resolved against the platform's indexed product catalog: an exact name is used as given; otherwise the closest indexed match is used and reported back in `technology_resolution` (requested, used, exact_match, alternatives) plus a plain-words `technology_note`. A name with no catalog match fails the call with an error; nothing is dropped silently. - When the call fails as too small and the error names a substituted technology, retry with one of the listed alternatives or a broader technology name. Do NOT loosen industries, seniority, employee bands or countries first: the substituted product is the cause. - Contact criteria fields work the same as in other audience types - Audience size depends on technology filters and applied criteria
    ConnectorAPI key
  • List one product page from a public BigCommerce storefront category URL. url must be the full category-page URL; page is one-based and defaults to 1. Use bigcommerce_product to retrieve details for a selected product URL.
    ConnectorNo auth
  • List one product page from a public BigCommerce storefront category URL. url must be the full category-page URL; page is one-based and defaults to 1. Use bigcommerce_product to retrieve details for a selected product URL.
    ConnectorNo auth
  • Projects from ProjectThunder's portfolio: the client, the platform (Sana Commerce, BigCommerce, DynamicWeb, mobile, AI), the industry, the ERP where the site names it, and what was built. Optionally filter by platform or by a word such as an industry.
    ConnectorNo auth
  • Call the API of a connected e-shop (Shoptet, Upgates, Shopify, WPJ Shop, WooCommerce, PrestaShop, Shoper, Shopware, Magento, BigCommerce, IdoSell) — ecomdly adds the owner's API access, you never see or need the key. Follow the platform's skill (shop_list names it) for paths and limits. `path` is relative to the API (Shoptet: /api/orders?page=1, Upgates: /orders?page=1, Shopify: /graphql.json and WPJ Shop: /admin/graphql/ with a POST body {"query": …}, WooCommerce: /orders?per_page=50, PrestaShop: /orders?display=full, Shoper: /orders?limit=50, Shopware: /search/order with a POST body of criteria, Magento: /V1/orders?searchCriteria[pageSize]=50, BigCommerce: /v2/orders?limit=50 or /v3/catalog/products, IdoSell: /orders/orders/search with a POST body {"params": {…}}). Reading always works (GET, GraphQL queries, Shopify bulk queries, Shopware and IdoSell searches, a Shoper bulk of GETs); changes (other POST/PUT/PATCH/DELETE, GraphQL mutations) only where the owner allowed them on ecomdly, and only what the owner confirmed in this conversation. For a custom API you sign in yourself as its docs say, writing {{secret}} where the key goes (headers, path or body). Returns the status, the limit headers and the body (long bodies are cut — page through, or use a snapshot / bulk query).
    ConnectorNo auth