Skip to content

O'So MCP Server 1.2.1

Choose a tag to compare

@github-actions github-actions released this 04 Nov 21:21
cc1d7d7

Added

A security and compatibility report with every release. Each version is now published only after the full test suite has passed on the exact code in the zip, and the release page carries a report of what was checked: every PrestaShop and PHP combination the module was installed and run on, each attack tried against a live shop and refused, the permissions of every tool, the code and dependency scans, and the SHA-256 of the zip, so you can check that the file you downloaded is the one that was tested. The report sits next to the zip on the release page, not inside the module.

Listing the customer groups. The new tool somcp_list_customer_groups lists the customer groups of the shop as Shop Parameters > Customer Settings > Groups shows them: name, discount, price display method, whether prices are shown, number of members and creation date, plus the groups used by default for visitors, guests and registered customers. The assistant now takes the group of a customer, of a category or of a specific price from this list instead of guessing it. It needs the view right on the Groups page and is part of the Find a customer and Manage products prompts.

Checking the shop's links. The new tool somcp_check_links walks the public pages of your shop from a starting page, as a visitor sees them, and lists the links that lead to an error page with the pages that contain them, the addresses that go through several redirects and the pages that take more than 2 seconds to arrive. Only your shop's own addresses are opened, at most 200 pages and one minute per check; links to other sites are counted, never followed. It needs the view right on Shop Parameters > Traffic & SEO and is part of the Audit and improve SEO prompt.

Checking the sitemap. The new tool somcp_audit_sitemap reads the sitemaps the Google sitemap module generated for your shop and tells you how many addresses each one holds, when it was last generated, which pages are left out on the module's screen and whether your robots.txt points search engines to it. It lists the active products missing from the sitemap and the disabled products still in it, and opens a sample of its addresses as a visitor to find those that answer an error. Only your shop's own addresses are opened, and the sitemap is never generated by the tool. It needs the view right on Shop Parameters > Traffic & SEO and is part of the Audit and improve SEO prompt.

Checking what a product page tells search and answer engines. The new tool somcp_audit_product_schema opens the public page of a product, or of one of its combinations, as a visitor sees it, and compares the structured data the theme prints there with the product page of your back office: name, brand, reference, MPN, barcodes, condition, price with tax, currency and stock. It lists each difference with the label of the field in your back office, and what your shop holds that the page does not print. When the theme prints no structured data at all, it says so: that comes from the theme, not from your products. Only your shop's own addresses are opened, and nothing is changed. It needs the view right on Catalog > Products and is part of the new Get recommended by AI assistants prompt, which guides the assistant through these checks and never promises that an assistant will cite your shop.

Changed

Each tool and prompt can be switched for the connected assistants and for the built-in assistant apart. On the Tools and prompts tab, the box in front of each tool and prompt is replaced by two switches on the right: one for the assistants connected over MCP, such as Claude or ChatGPT, and one for the assistant built into your back office. You can keep a tool for the built-in assistant, which asks before every change, and hide it from the assistants that connect from outside, or the other way round. Each list also has a search field, which finds a tool or a prompt by its name, its title, its publisher or the permission it needs. Nothing changes when you update: a tool or prompt you had switched off stays off in both columns, and the built-in assistant can switch either column when you ask it to.

The server address shows the shop's "page not found" in a browser. The address you give to an assistant used to answer a browser with a blank error page. It now shows the shop's usual page not found, like any other address that leads nowhere for a visitor. Assistants are not affected: they keep being answered as before.

Catalogue tools point plainly to the tool to use next. Seven category, feature and attribute tools still told the assistant to use a tool to read or add a value "when the shop offers it", although every one of those tools is there. The assistant could take it as a tool that may be missing and skip the step. They now name the tool plainly.

Shorter customer tools. The four tools of Customers > Customers - search, read, create and change a customer - and the list of customer groups now describe themselves in a few sentences, lighter for the assistant on every step. What matters is kept: which tool gives the customer and the group identifiers, that every value comes from you and is never invented, that no password goes through the conversation and no email is sent to the customer, and which read checks a change.

Shorter supplier tools. The five tools of Catalog > Brands & Suppliers > Suppliers - list, read, create, change, enable or disable a supplier - now describe themselves in a few sentences, lighter for the assistant on every step. What matters is kept: that the supplier identifier comes from the list and is never guessed, that a supplier name can exist twice so the list is read before a creation, who fills each field, that disabling is not a deletion, and which read checks a change.

Shorter brand tools. The six tools of Catalog > Brands & Suppliers > Brands - list, read, create, change, enable or disable a brand, and the SEO audit of brands - now describe themselves in a few sentences, lighter for the assistant on every step. What matters is kept: that the brand identifier comes from the list and is never guessed, that a brand name can exist twice so the list is read before a creation, who fills each field, that disabling a brand keeps its products on sale, and which read checks a change.

Shorter brand address tools. The five tools of the Brand addresses list of Catalog > Brands & Suppliers > Brands - list, read, add, change and delete an address - now describe themselves in a few sentences, lighter for the assistant on every step. What matters is kept: that the brand and the address identifiers come from the lists and are never guessed, that the same address can be added twice so the list is read first, that every field comes from you and is never invented, that customer and supplier addresses are refused, and which read checks a change.

Shorter theme, cache, tax, carrier and file tools. The two tools of Design > Theme & Logo - read the theme and change the layout of a page - and the lists of tax rules, carriers and Catalog > Files, with the Clear cache button of Advanced Parameters > Performance, now describe themselves in a few sentences, lighter for the assistant on every step. What matters is kept: that a page, a layout, a tax rule, a carrier or a file is taken from its list and never guessed, that a layout is confirmed with you before it changes, that clearing the cache clears it for every shop of the installation and slows the next pages, that a file's download link is public and stays with you, and which read checks a change.

Fixed

Inactive products that follow the shop's default behaviour are judged correctly. On PrestaShop 9, an inactive product left on the shop default in somcp_audit_product_seo was always reported as having no redirection, even when Shop Parameters > Product Settings > Default behavior for disabled products keeps its page shown with a 200 response. The audit now reads that setting: such a product is no longer reported, and when it is, the entry names both the product's choice and what the shop default applies, so you know which setting to change. Nothing changes on PrestaShop 8.

The module passes the PrestaShop Addons validator again. The check somcp_update_theme_setting makes before changing the theme, which refuses to change it on a shop in demo mode, was reported by the validator as a condition that can never be true. It now reads the shop's demo mode the way the other tools read the core's settings, and behaves as before.

The faceted search fields of attributes and features follow the module's state. With the faceted search module installed but disabled, the back office form no longer shows the URL and Meta title fields, yet somcp_get_attribute_group, somcp_get_attribute_value, somcp_get_feature and somcp_get_feature_value still returned them as empty texts, which the update tools then refused. They now return them as null whenever the module is not installed and enabled, as the create and update tools already did.

Attribute values with ; or # in their name are refused on PrestaShop 9. On PrestaShop 9, somcp_create_attribute_value and somcp_update_attribute_value accepted a name holding ; or #, which the back office form of an attribute value refuses there: the value was saved, then its edit page could not be saved again until it was renamed. Both tools now refuse these characters on PrestaShop 9 as the back office does, and say which characters the running version refuses. PrestaShop 8, whose form accepts them, is unchanged.


Install: download OSo-MCP-Server-1.2.1.zip and install it from Modules > Upload a module.