Icecat Release Notes 231: Icecat MCP Server and Technical Enhancements

In release 231, our focus was two main areas: delivering the Icecat MCP server, a major step forward in enabling AI-driven product data integrations, and implementing a series of technical improvements to strengthen the Icecat platform. Together, these updates mark an important milestone in both innovation and infrastructure reliability. For additional details, please refer to the previous Icecat Release Notes.

MCP Server – Beta Version

In this sprint, our primary goal was to deliver the Icecat MCP Beta version server – a significant milestone in making Icecat data more accessible for AI-driven workflows.

What is MCP?

Think of the Model Context Protocol (MCP) as a bridge between AI agents and reliable product information. Let’s use a simple analogy:

Imagine you are preparing dinner. You, the cook, represent the AI agent. To cook, you need specific ingredients. Instead of going shopping yourself, you ask a family member — this is the HTTP request — to bring the ingredients. You already know which shop has what you need, so you send them there directly. That shop is the MCP.

Similarly, in Icecat, the MCP acts as the source of structured product data. AI agents can rely on it to fetch exactly the product information required to complete user tasks.

What is inside of the Beta?

The Icecat MCP server is now live in its Beta phase. Currently, it supports fetching product information when an AI agent provides Product code and Brand name.

In future releases, we will expand this functionality to support GTINs as identifiers. Beyond that, additional tools and features are planned to further strengthen the MCP ecosystem and enhance usability for AI applications.

Next Steps

For a complete walkthrough, please refer to the detailed MCP User Manual, which includes:

• Step-by-step instructions for connecting to the Icecat MCP server.
• An overview of the available tools.

This is just the beginning of the MCP journey, and we’re excited to see how it enables new AI-powered use cases.

Other Technical Developments

In parallel with delivering the MCP Beta server, our teams focused on several important technical improvements to strengthen the stability, performance, and maintainability of the Icecat platform.

Brand Cloud Front-End Technical Debt

We continued our ongoing effort to reduce technical debt in the Brand Cloud front-end. Key updates include:

• Modernized design framework to align with current standards.
• Improved API reliability for smoother communication between services.
• Streamlined interface components to ensure consistency and usability.
• Reduced unnecessary dependencies to simplify maintenance and improve performance.

Icecat.biz Technical Audit

A thorough icecat.biz technical audit was conducted to address performance and stability. As part of this work, we:

• Optimized the build process for faster and more efficient delivery.
• Removed unused code to reduce complexity and improve maintainability.
• Improved page stability to enhance the end-user experience.
• Explored fallback options to ensure smoother operation under edge cases.
• Started tracking MySQL usage to provide data-driven insights for future optimizations

Other Improvements

Beyond the Brand Cloud and icecat.biz developments, we also:

• Explored moving the image handler to PHP, paving the way for more efficient image delivery.
• Strengthened security for one private service, ensuring greater protection of user sensitive data.

With this release, we are advancing in two critical directions: empowering AI agents with smarter product data access through MCP and enhancing the robustness of our platform through technical refinements. These updates set a solid foundation for upcoming innovations, ensuring that Icecat continues to deliver reliable, scalable, and future-ready solutions.