Use JTL-Wawi with AI via MCP
For many online retailers, JTL-Wawi is the merchandise system behind shop and marketplaces. No MCP server exists for it yet, so we build the CompanyGPT integration on the JTL-Wawi REST API, which runs locally in your environment.
What is JTL-Wawi?
JTL-Wawi is the merchandise management system from JTL-Software GmbH in Hückelhoven, Germany, aimed at retailers with multichannel sales. It connects the retailer’s own shop with marketplaces such as Amazon and eBay and manages item master data, stock, orders, shipping and returns. Technically it is a Windows application with a Microsoft SQL Server backend, run either at the retailer’s own site or in a hosted instance.
For retail teams the real bottleneck is operational volume: thousands of orders, constantly shifting stock and recurring customer questions. An AI agent with read access to this data can answer enquiries and produce analyses without anyone setting filters or building exports – which mainly relieves customer service and purchasing.
Connection at a Glance
- MCP server
- None available – custom integration
- Interface
- JTL-Wawi REST API (local service, OpenAPI-documented)
- Cloud variant
- JTL cloud ERP API (api.jtl-cloud.com) forwards requests to the Wawi instance
- Authentication
- API key after app registration/onboarding; OAuth 2.0 via the partner portal for the cloud API
- Operating model
- On-premises (Windows/SQL Server) or hosted instance
- Network
- Local API not publicly reachable – network access required; not needed via the cloud API
- Alternative route
- Automation platform n8n as an intermediate layer
How to Connect JTL-Wawi to CompanyGPT
There is currently no MCP server available for JTL-Wawi – neither from the vendor nor from the community. The connection is therefore built individually on the JTL-Wawi REST API, which runs as a local Windows service and is documented via OpenAPI. We translate the required endpoints into MCP tools and provide them inside your CompanyGPT environment; that is our standard approach for any API with an OpenAPI specification.
Authentication uses an API key issued as part of an app registration and JTL’s onboarding process. Access is thus tied to a named registered application and can be revoked at any time. Which endpoints the agent may use – read-only order and item queries, for example – is defined together with you.
Because the REST API runs as a local service and is not publicly exposed, CompanyGPT needs a connection into your environment; we agree the implementation with your IT team or hosting partner.
In addition, JTL offers the cloud ERP API at api.jtl-cloud.com, authorized via OAuth 2.0 with an application registered in the JTL partner portal, which forwards requests to your Wawi instance. Taking that route removes the need for a direct network link or VPN into your network – calls run through JTL’s cloud endpoint. Which of the two variants fits depends on your JTL version, your operating model and your internal requirements; we clarify that at the start of the project. An alternative route runs through an automation platform: n8n ships building blocks for JTL and is operated by innFactory as a separate managed service on request.
Note for on-premises operation: CompanyGPT runs in your own Azure tenant – so your on-premises network can be connected directly: via a site-to-site VPN (Azure VPN Gateway) or ExpressRoute between your corporate network and the virtual network of your CompanyGPT environment. The system does not need to be publicly reachable; we set up the connection together with your IT team.
Typical Use Cases
How AI agents in CompanyGPT work with JTL-Wawi
Answer customer enquiries faster
Customer service asks for status, shipment and line items of an order and gets the details straight from JTL-Wawi – without searching order numbers in the UI.
Review stock and reorder needs
Purchasing lists items with low stock and high sell-through rates in order to trigger reorders earlier.
Understand returns
Quality management groups return reasons over a period and has anomalies per item group summarized.
Frequently Asked Questions
JTL-Wawi and AI – the most important answers
Is there an MCP server for JTL-Wawi?
No, neither from JTL nor from the community. Connecting an AI assistant is therefore done individually through the documented JTL-Wawi REST API.
Is an AI connection still possible?
Yes. The REST API is described via OpenAPI, and those are exactly the interfaces we expose as MCP integrations. The agent only receives the endpoints released for your use cases.
How does CompanyGPT reach our local installation?
Through a secured network connection into your environment. Since the local JTL REST API runs as a Windows service and is not publicly reachable, we set this up with your IT team or hosting partner.
Is it possible without a VPN into our network?
Yes, via the JTL cloud ERP API at api.jtl-cloud.com. It is authorized with OAuth 2.0 using an application registered in the JTL partner portal and forwards the requests to your Wawi instance – no direct network link is required. Which variant fits depends on your JTL version and operating model.
How is access authorized?
For the local REST API through an API key created during app registration with JTL; for the cloud ERP API through OAuth 2.0 with an application registered in the partner portal. In both cases access is tied to a named application and can be revoked at any time.
Can the AI change orders in JTL-Wawi?
Only if you explicitly release write endpoints. In practice most retailers start with read-only access for enquiries and analysis.
Related Integrations
ERP & Merchandise Management
JTL-Wawi and Your AI – GDPR-Compliant with CompanyGPT
CompanyGPT is the enterprise AI assistant in your own cloud tenant: all relevant AI models, your company data and integrations like JTL-Wawi – centrally managed, with roles and permissions. We set up the connection together with you.
JTL-Wawi is a trademark of its respective owner (JTL-Software GmbH). Its mention describes compatibility and does not imply any partnership or endorsement. Availability and scope of the connection depend on the respective vendor.