Why MCP on etg24
The Model Context Protocol (MCP) lets AI agents use tools through a standard, authenticated interface. etg24 exposes its complete integration surface as MCP tools — and this is not a thin experimental wrapper.
1. We use it ourselves
etg24 runs an internal MCP server in production with hundreds of tools covering the entire platform. The same tool registry, the same authentication, the same CQRS split that powers the external tool reference has been running inside our own operations. That is the strongest possible validation: the MCP surface is not something we built for you — it is something we already run on.
2. Customers use it
Customers run agents against the etg24 MCP server every day — for internal workflows, automations, and their own products. The use cases on this portal are the patterns they build.
3. External partners have built on it
Product partners integrate their offerings through the same MCP surface. The external MCP tool catalogue is growing steadily as more endpoints graduate to the integrator surface.
How the surface is structured
The MCP server exposes three kinds of tools:
- Meta-tools —
meta.tools.search,meta.tool.describe,meta.tool.execute,meta.docs.search, and thesaurus tools. They let agents discover, inspect, and invoke domain tools, and ground answers in documents and the user manual. - Query tools — read data. Safe, retryable, mapped to read-only scopes.
- Command tools — change data. Explicit, audited, gated. See CQRS.
Browse the generated reference: MCP tool reference.