Skip to main content
Glama
728,188 tools. Updated 2026-10-31 09:47

"PrestaShop" matching MCP tools:

Matching MCP Servers

Matching MCP Connectors

  • prestashop-mcp-connector

    Connects an AI assistant to a PrestaShop store: orders, invoices, unpaid orders, customers, sales by region, stock, and optional quote generation with PDF. Runs as a module inside the store.

  • Fondouk (PrestaShop demo store)

    Query a live PrestaShop e-commerce store: search the catalog, get product details, real-time prices and stock. Fondouk is an open-source module (MIT) that makes any PrestaShop store speak MCP and UCP — this connector is its public demo store. Read-only, public data only.

  • import_templateA

    Storno CLIB

    Downloads a ready-to-fill CSV template for a chosen import type, with column headers and example rows. Use it to prepare data, then upload via import_upload; pass a platform source to match that export layout.
    Elastic 2.0

  • import_uploadA

    Storno CLIB

    Upload a CSV, XLSX, XML, or ZIP file with the required import type and source to create a Storno import job and receive preview data.
    Elastic 2.0

  • import_sourcesA

    Storno CLIB

    Retrieve supported import sources and import types for a company, so you can determine which data providers and record categories are available before starting an import.
    Elastic 2.0

  • advanced_searchA

    entyrix-mcpA

    Search European companies by geography, sector, size, financials, credit, sanctions, NIS2, cyber exposure, digital footprint, and public money. Returns paginated per-country results.
    MIT

  • detectProjectPlatformA

    TrackdolphinC

    Detect the e-commerce platform behind a website by checking its homepage and known paths, then return verified evidence or 'unknown' if unclear.
    MIT

  • connect_ecommerceB

    WAzion MCP ServerC

    Link an e-commerce platform (Shopify, WooCommerce, PrestaShop, or VTEX) to retrieve products, orders, and customer data. Ask the user which platform they use.
    MIT

  • apply_product_contentA

    Pridly — AI copilot for PrestaShopA

    Saves product names, descriptions, short descriptions and SEO text in one or more languages of the shop. Each item is one product with a `translations` object: language code → text (e.g. {"fr": {...}, "es": {...}}). ONLY the languages you list change; every other language keeps its text. Call get_brand_voice first and follow the user's saved style. Use translation_gaps to find what is missing. Preview first (shows before/after per language), then confirm. Always show the preview to the user and get their explicit approval before calling again with confirm=true and the preview_id. Paid plans only. To apply it later instead of now, call with confirm=true, the preview_id AND apply_at (the store's local time, YYYY-MM-DDTHH:MM).
    Connector
    Destructive
    OAuth

  • shop_requestA

    ecomdlyA

    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, and for the job itself (product titles, descriptions, translations, prices, stock, feeds) a skill from the ecomdly catalog — search_skills first, before you change products. `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

  • site_consoleA

    AskYourStackB

    Run a site's own command line tool as the site's owner, in the site's folder: bin/console for Shopware 6 and PrestaShop, artisan for Laravel, drush for Drupal, cli/joomla.php for Joomla, ghost (ghost-cli) for Ghost (list_sites shows each site's console; Magento 2 has the magento tool and WordPress the wp tool). Pass the command and its options as args, like ["cache:clear"] or ["plugin:list", "--json"]. For a site in a Docker container it runs inside the container. Listing and status commands run straight away; uninstalling or deleting, anything that drops or resets the database, generating new keys, an admin login link and commands that run arbitrary PHP (tinker, php:eval) need approval. Symfony's console and artisan are run with --no-interaction; drush asks nothing only when you pass -y. Set background true for slow commands.
    Connector
    Destructive
    OAuth

  • set_product_discountA

    Pridly — AI copilot for PrestaShopA

    Gives products a percentage (or fixed amount) discount for a limited time, e.g. "20% off these 5 wines until Sunday 23:59". It uses PrestaShop's own specific prices, so the shop shows the old and new price automatically and the discount ends by itself. Choose products with ids (best: ask top_products first) or a search word/category. Preview first, then confirm; undo removes it. Always show the preview to the user and get their explicit approval before calling again with confirm=true and the preview_id. Paid plans only. Max 100 products. To apply it later instead of now, call with confirm=true, the preview_id AND apply_at (the store's local time, YYYY-MM-DDTHH:MM).
    ConnectorOAuth