On this page

MCP

Quick connect

Connect any MCP client to the etg24 MCP server that matches your agent’s role and key:

	Property Management API	Internal API
Endpoint	`https://api.etg24.de/propertymanagement/v2/mcp`	`https://api.etg24.de/api/internal/v1/mcp`
Use when	the agent acts on behalf of the company	the agent acts on behalf of a user
Required key	a tenant-bound (company) API key	a user-bound API key
Tool catalogue	the Property Management v2 tools, as in the tool reference	the Internal API tools, including internal-only domains such as notes

Both speak the same protocol and use the same meta-tool loop (meta.tools.search → meta.tool.describe → meta.tool.execute), but each serves the tools of its own API layer — the catalogues differ between the two.

{
  "mcpServers": {
    "etg24": {
      "url": "https://api.etg24.de/propertymanagement/v2/mcp",
      "headers": { "Authorization": "Bearer <COMPANY_API_KEY>" }
    }
  }
}

Swap the URL for https://api.etg24.de/api/internal/v1/mcp and use a user-bound key when the agent acts for a person. Step-by-step setup for Claude, ChatGPT, Mistral, Perplexity, opencode, Cursor and VS Code lives in the MCP setup guide.

What agents can do

Read anything your portal stores — query tools over objects, units, contacts, contracts, documents.
Change data deliberately — command tools follow the same CQRS split as the REST API, with scopes and an audit trail.
Find tools by meaning — meta.tools.search discovers the right tool, meta.tool.describe inspects its schema, meta.tool.execute runs it.
Ground answers in documents — meta.docs.search retrieves documents and user-manual content semantically.
Stay attributable — every agent key is its own actor in the change log; unintended deletions are soft-deleted and restorable via Soft delete & rollback.

New to MCP on etg24? Start with Why MCP on etg24, then follow the meta-tool workflow, and read the security best practices before you let an agent write data.

Authentication & transport


Endpoints	`https://api.etg24.de/propertymanagement/v2/mcp` (company agents) · `https://api.etg24.de/api/internal/v1/mcp` (user agents)
Authentication	API key in the `Authorization: Bearer` header — a tenant-bound (company) key on the Property Management API, a user-bound key on the Internal API
Protocol	JSON-RPC 2.0 over HTTP `POST`. Responses come back as JSON, or as SSE (`text/event-stream`) when the client sends that Accept header
Tool listing	`tools/list` advertises the meta-tools. Domain tools are discovered at runtime via `meta.tools.search` and invoked via `meta.tool.execute` — see the meta-tool workflow

Stability

A capability that has landed on the MCP surface stays there until the functionality itself is removed from the product — we do not retire MCP capabilities on their own. The technical contracts behind the tools (endpoint paths, input and output schemas) can change without further notice, because discovering them at runtime is the intended way to use MCP. See MCP stability & versioning.

Tool reference

The integrator catalogue — meta-tools plus the Property Management v2 and Platform domain tools, generated from the backend’s mcp:exportTools — is browsable on one page. Internal API tools are not part of this public reference:

→ Browse the MCP tool reference