MCP servers: the tools agents act through,
and what each sends outside.
An MCP server gives an agent tools to call: a web search, a database query, a dashboard. Most are published by someone other than Katonic. Each row says who publishes the server, what it needs and whether it sends data outside your environment.
How the calls are governed
Tool calls go through the platform's tool gateway. It manages the connection to each MCP server, passes calls from the agent runtime, and applies the allowlists, rate limits and data-classification rules an administrator sets. Tool usage is recorded. A server can be deployed in your cluster or reached as a remote hosted server.
Who publishes a server
Most servers are published by someone other than Katonic, and some by someone other than the company whose product they connect to. Each row names the publisher.
Katonic's own MCP server
Katonic also offers an MCP server of its own. That is a different thing from the servers listed here, and it has its own page.
What is an MCP server?
A program that offers tools to an agent through the Model Context Protocol. The agent calls a tool, such as a search or a query, and gets the result back.
Which of these send data outside our environment?
The web search servers send the query to their service, and Handwriting OCR sends the documents it is given. The servers for databases and monitoring talk to the system at the address you give them.
Are these servers Katonic's software?
No. Each row names the publisher. Katonic runs the server and governs the calls an agent makes to it.
Is this the whole list?
No. These are the servers the use case pages name. The product's Catalog lists more, and you can add your own.