From one agent to a hundred, without rebuilding
The widget on your site, the conversation behind it and the route to the right flow.
What this is about
Widget Server is the infrastructure under the agents. The widget on your site — the window in which a visitor asks a question — talks to it. The server receives the message with the basics: which site, which language, which visitor and which product is on screen. It then determines which flow belongs to it and passes the conversation on.
So not every agent needs its own environment. Agents are managed centrally and one can be added without the setup changing, which is the difference between one agent and ten agents on ten brands. Language is recognised along the way and translated where needed, so a German visitor gets a German answer without a second agent.
Widget Server manages the deployment and configuration of chat widgets across all connected websites. Each widget gets its own branding, language settings and conversation flows.
Without Widget Server, each agent would need separate deployment. Widget Server manages all agents centrally.
Who we built this for
Companies with more than one site, brand or language that do not want to maintain a separate agent per environment. And companies that want an agent on a site that is not ours: the widget is a window you place in your own page.
What you get with it:
What actually happens
The value is in the context and in the management. An agent without context starts every conversation empty and asks for things that are on screen; an agent that knows which product is open can calculate straight away. And ten agents without central management are ten installations that age separately.
The widget on any site
A window you place in your own site, also when that site is not ours and runs on another platform.
Sending the basics along
Which environment, which language, which product is on screen and who is looking, so the agent has context instead of an empty conversation.
Routing to the right flow
Every widget hangs on a flow in Flowbuilder, so what happens is fixed and can be read back.
Managing several agents centrally
One overview of the active agents, instead of ten separate installations each with their own version.
Recognising and translating language
The visitor is helped in their own language without you setting up a second agent.
Spreading the load
Load is spread across the agents, so the conversation does not stall when ten people ask something at once.
Measuring per widget
How many conversations, how many hand-offs to a flow and how fast answers came.
From widget to action
Widget receives input, sends basic info, triggers Flowbuilder, action is executed. Everything automatic, everything scalable.
Agent Registry
All active AI agents in one place.
Widget to Flow
Each widget automatically triggers the right flow.
Info Routing
Basic information is sent to the right destination.
Scale Manager
Automatic scaling when more agents are added.
How it fits with the rest
Widget Server sits between the visitor and Magic Agent. Flowbuilder determines the steps, and the MCP servers in Magic Orb give access to the data the agent calculates with: the catalogue in the PIM, the prices, the stock and the quote module. For WhatsApp, Meta Server does exactly what this tool does for the website.
Because the widget fits in any site, you can start with it without the rest of Magic Studio. Anyone adding the PIM and the ERP module later keeps the same widget and the same flows; only the data the agent may reach gets richer.
What it delivers:
We will put a widget on a test version of your own site
You see the agent working on your own pages, with your own products on screen. That is more useful than a demo on our site, because the context the widget sends is yours.
If something stalls, you see that too — including the place in the flow where it happened. That is where the real conversation about what the agent may do starts.