On this page

MCP

Quick connect

Connect any MCP client to the etg24 server with your API key — the same key you use for the REST API.

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

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; mistakes are soft-deleted and rollback-ready.

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


Endpoint	`https://api.etg24.de/propertymanagement/v2/mcp`
Authentication	API key in the `Authorization: Bearer` header — the same keys and scopes as the REST 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

Tool reference

The full catalogue — meta-tools plus every domain tool, generated from the backend’s mcp:exportTools — is browsable on one page:

→ Browse the MCP tool reference