Why MCP on etg24

The Model Context Protocol (MCP) enables AI agents to discover and invoke tools over a standardized, authenticated protocol. etg24 exposes its property management capabilities directly as MCP tools — not as an experimental prototype, but as production-grade infrastructure.

1. We run on it ourselves

etg24 operates an internal MCP server in production with hundreds of tools spanning the entire property management domain. The same tool registry, authentication pipeline, and CQRS architecture that power the public MCP tool reference run daily inside our own operations. This provides the strongest possible validation: the MCP interface is foundational infrastructure we rely on continuously.

2. Proven in customer workflows

Property managers and their teams connect AI agents to the etg24 MCP server daily — automating inbox triage, generating custom reporting summaries, and drafting communications grounded in real estate data. The use cases documented on this portal reflect actual production workflows.

3. Trusted by software partners

Commercial product partners integrate their solutions through the same MCP interface. The public tool catalogue expands continuously as additional domain endpoints are published for integrators.

How the tool catalogue is structured

The MCP server organizes tools into three functional tiers:

• Meta-tools: meta.tools.search, meta.tool.describe, meta.tool.execute, and meta.docs.search. They empower agents to dynamically discover domain tools, inspect input/output schemas at runtime, execute operations safely, and ground answers in property documents and user documentation.
• Query tools: Safe, idempotent data retrieval operations mapped to read-only capability scopes.
• Command tools: Audited, state-changing operations subject to strict business validation and permission gating. See CQRS.

Explore the generated specification: MCP tool reference.