aimeos

Aimeos 2026.10: MCP tools for Laravel e-commerce Aimeos is an open-source e-commerce framework for Laravel applications. Version 2026.10 adds MCP tools that let AI agents search products, update orders and manage customers in your shop. An agent could retrieve selected products, draft improved descriptions and save the changes after your approval. Aimeos provides the tools for reading and updating shop data; your integration handles the agent workflow and approval step. What's new MCP tools for AI agents Model Context Protocol (MCP) gives AI applications a standard way to discover and call tools. The new ai-admin-mcp extension provides tools for more than 20 shop domains, including products, categories, orders, customers and stock. Depending on the domain, agents can search and aggregate records, save and delete items, and change category trees. composer require aimeos/ai-admin-mcp Each tool validates its arguments and checks permissions using the Aimeos context supplied by your integration. In admin/mcp/resource you configure which user groups may call which tool. The package doesn't include an MCP transport or SDK. Each tool exposes an input schema and returns its results as PHP arrays. Your integration registers the tool definitions with an MCP server and routes calls to their execution methods. Expose only the tools you need. The MCP package README shows how to retrieve the tool catalog, inspect definitions and execute calls. WebMCP in the storefront WebMCP is a proposed browser standard that lets websites describe actions for AI agents. The Aimeos storefront now uses it on the forms for addresses, saved baskets, coupons and product watch lists. Browser agents that support WebMCP can fill these forms for the customer. Few browsers support it yet, and for regular visitors the forms work as before. Choose an AI provider for each task In the admin backend, you can write and translate texts, generate images and remove image backgrounds with AI. In 2026.10, these features use Prisma (aimeos/prisma), our PHP library for AI providers. You can configure a different provider and model for each task. Switching providers later is a configuration change. Imports and exports Customer, product, category and supplier imports can combine file data with configured values. For example, set a fixed product.status in the import mapping and omit the repetitive status column from your CSV. Order, product and subscription exports can be extended with project-specific data before the files are written, for example fields your ERP or CRM system expects. Framework support Laravel 10 to 13 remain supported, Symfony 8 and TYPO3 14 are now supported too. Security hardening - Customer password hashes are excluded from loaded customer items and API responses. Admin APIs apply tighter checks to shared items and customer group assignments. - HTML sanitization and output encoding strengthen XSS protection. Remote image and CMS media fetching blocks internal addresses to protect against SSRF. - Checkout steps require POST requests. Guest orders can't be linked to existing accounts by e-mail, and site settings can't overwrite internal configuration keys. For published vulnerabilities and affected versions, see the core security advisories. How Aimeos fits into your application You can install Aimeos (LGPLv3) into an existing Laravel application as a Composer package. It uses your routes, middleware, authentication, queues and Blade views. Use the JSON:API for a custom frontend, or start with the server-rendered HTML components included with Aimeos. GraphQL and now MCP cover administration. Aimeos is multi-vendor, multi-language, and multi-currency capable so you can run several shops with their own catalogs, prices, languages and currencies. Aimeos is self-hosted, so you control your shop database and hosting, with no Aimeos fees per transaction. Data sent to external AI services depends on the provider and features you configure. Get started You can install different packages, depending on your needs: # Full shop system composer create-project aimeos/aimeos # Headless API composer create-project aimeos/aimeos-headless # Laravel package only composer require aimeos/aimeos-laravel - New to Aimeos? Follow the Laravel setup guide or explore the demo shop. - Upgrading an existing shop? Read the upgrade guidance before updating your dependencies. - Building an agent integration? Install aimeos/ai-admin-mcp and use the tool catalog example to connect the tools to your MCP server. You can find the application source on GitHub. If you like Aimeos, give it a star! :-)

PagibleAI CMS 0.13: Review with AI, publish with confidence PagibleAI is an MIT-licensed CMS for Laravel with visual editing, versioned content, and APIs for headless frontends and AI agents. It runs on PHP 8.2+ with Laravel 11, 12 or 13. PagibleAI 0.13 helps you review content before publishing and keep connected systems updated afterwards. Ask the AI assistant to check a page, inspect its changes in the history, and publish when you're ready. Optional webhook and CDN packages notify your integrations and purge affected URLs. !Image description Review a page before publishing Version 0.13 teaches the AI assistant built-in SEO rules for page reviews. Just click on the magic AI button and the assistant checks heading structure, meta description, canonical and robots settings, broken links and more. It explains what it found and you can then ask it in the chat to apply all suggestions or parts of it to the draft before you publish. Before publishing, open the redesigned history dialog. Large text diffs collapse to the changed passages, and unpublished versions are marked clearly, so you see exactly what the AI and your colleagues changed. To enable the chat, set its provider and API key with CMS_AI_WRITE and CMS_AI_WRITE_API_KEY, as described in the AI configuration guide. Edit without losing your place Visual editing now opens content fields in a sidebar next to the preview. Change a headline while its layout stays visible, then check desktop, tablet and phone sizes. The element picker adds search, group tabs and descriptions. Press Ctrl/Cmd+K to jump to a page, element, file or action with the new command palette. Ctrl/Cmd+S saves; Ctrl/Cmd+Shift+S opens the publishing menu. Trigger integrations with signed webhooks Publishing often starts another task: updating a search service, rebuilding a static frontend, or sending content to another channel. The optional aimeos/pagible-webhooks package sends tenant-scoped notifications through Laravel's queue when pages, elements or files are published, deleted, restored or purged, and when pages are moved (page.published, element.deleted, file.purged and so on). Each notification identifies what changed: { "event": "page.published", "tenant_id": "tenant", "timestamp": "2026-09-14T12:00:00.000+00:00", "data": { "id": "01995d6a-cb84-7218-9bb9-79063c4bf681", "version_id": "01995d6a-cb84-7218-9bb9-79063c4bf682", "path": "products/example", "domain": "example.com" } } Requests use Standard Webhooks signatures. The webhook verification guide provides a complete Laravel receiver covering signature and timestamp checks, duplicate deliveries and queued processing. For a search integration, your job fetches the current content to update the external index, or removes an entry when content is deleted. Manage and test subscriptions in the admin panel. Temporary failures trigger retries with increasing backoff, while terminal responses such as 404 stop delivery. Run this check during deployment to validate endpoint settings, deny-list entries, queue timing and cache configuration: php artisan cms:webhooks:check The command also warns about subscription secrets that can no longer be decrypted. Purge CDN caches when content changes When you correct a price or headline, your CDN needs to stop serving the old copy. The optional aimeos/pagible-cdn package purges Cloudflare, Fastly and Varnish automatically. With your provider configured and queue workers running, the package purges affected page URLs and public files removed from storage through queued jobs. Publishing a URL change queues purges for both the old and new address. For Cloudflare, configure your token and zone, then choose how long public pages may stay cached: CMS_CDN_CLOUDFLARE_TOKEN=... CMS_CDN_CLOUDFLARE_ZONE=... CMS_CDN_MAXAGE=86400 CMS_CDN_STALE=60 CMS_CDN_MAXAGE=86400 lets the CDN cache public pages for a day. CMS_CDN_STALE=60 allows a stale copy for up to a minute while refreshing it or if your server is unavailable. Pages that only show a changed navigation entry stay cached until they expire, so pick a lifetime your site can live with. PagibleAI also caches complete public pages in Laravel's cache, a separate layer from the CDN. The admin panel's "Clear cache" action clears a page and its subpages from the application cache and, with the CDN package configured, queues their CDN purges too. After a theme change, you can purge all CDN content: php artisan cms:cdn:purge --all Catch content errors before submitting updates The new content schema endpoint in 0.13 lets your frontend, form builder or AI agent read registered content, metadata and configuration definitions, including those added by themes and extensions: GET /cms/schema The endpoint returns a JSON Schema Draft 2020-12 document. This excerpt shows the required title field inside a hero element's data object: { "type": "object", "properties": { "title": { "type": "string", "minLength": 1 } }, "required": ["title"] } A missing title or an empty string fails validation before your integration submits the update. Use a Draft 2020-12 validator to check the full content, meta and config object, or select an individual element definition. Write changes through GraphQL or MCP. Import content from TYPO3 and WordPress A new TYPO3 importer brings pages, content and files over to Laravel, preserving the page tree. Re-importing the same domain and post slug with the WordPress importer now updates and republishes the existing article instead of creating a duplicate. Each run publishes the imported changes and preserves publication dates and cover images. Both importers are available through the optional aimeos/pagible-import package. They read directly from the source database, configured as a Laravel database connection: php artisan cms:t3-import --connection=typo3 --file-base=https://example.com/fileadmin php artisan cms:wp-import --connection=wordpress --domain=example.com More in this release - AI agents: Claude Code, Cursor and other MCP clients can manage pages through the built-in MCP server. Its tools now accept base64 file uploads, so your agent can attach a file without hosting it at a public URL first. - Themes: Taste and News add layouts for restaurants and publishers. - Content elements: New maps, call-to-action blocks and configurable contact forms. - Images: Smaller preview images for mobile devices, and php artisan cms:previews regenerates previews for existing images. Install or upgrade Add the CMS to your Laravel application with the PagibleAI installation guide. Already using PagibleAI? Review the PagibleAI upgrade guide before updating your application. The webhooks and CDN integrations are separate packages you add when you need them: composer require aimeos/pagible-webhooks aimeos/pagible-cdn When an editor publishes a change, which systems does your application need to update? If you like PagibleAI CMS, give it a star :-)