Agents and assistants reach your systems through it. Below: what that means in practice, how access rights work and when you do not need one.
MCP router
One point through which agents take data and hand back the result.
It is the connection point through which a program is given access to your systems data. MCP (Model Context Protocol) describes exactly how: one way instead of a separate link for every system-assistant pair.
The router is the part that sits between the agents and the systems: it takes the request, checks the rights, goes to the right system and returns the answer.
Because an integration links two particular systems, while a router links any program to any connected system. The next assistant, the next report and the next agent all work through a connection that is already described.
For a company without developers that is the whole point: a new task stops beginning with a new integration.
Systems connect to the router one at a time: till, stock, suppliers, accounting. For each one it is written down what it hands out and to whom. An agent or an assistant addresses the router rather than the system, and sees exactly the slice it is allowed.
RestoAudit runs a connector like this: the assistant answers from Syrve, stock, suppliers and accounting through one connection point.
A chatbot is a window for a conversation. The router is access to data, and it answers nothing by itself: it exists so that whoever answers speaks from your figures rather than from the model general knowledge.
So the router serves an assistant in a chat and an agent that runs on a schedule and delivers its result where the work happens equally well.
When the data sits in one system and that system can answer questions about it. A router appears where there are several systems and the answer is assembled from more than one source.
And when nothing reaches the data programmatically: for a one-off job, exporting by hand is cheaper.
Only the slice you allowed, and only when requested by someone the access was given to. The router keeps no copy: it reaches the system at the moment of the question.
You do. For every connection it is written down what is handed out and to whom, and that description changes in one place. Access can be revoked as easily as it was granted.
Yes, with any assistant able to connect over MCP. The RestoAudit connector works this way: the assistant asks a question and the answer is assembled from the connected systems.
No. An agent can run on a single source. The router is needed when an agent needs data from several systems, or when there is more than one agent.