Connect MCP to your AI agent

Every MCP-capable app connects the same two things: an etg24 MCP endpoint and your API key. This page walks through the setup for the most common agents.

Which MCP endpoint should you use?

Two MCP endpoints are available to your agents. Both speak the same protocol and expose the same meta-tool workflow — what differs is who the agent acts for, and that decides which key it must use:

In one line: company agent → Property Management API, user agent → Internal API. The key binding also decides how every action shows up in the change log. See Identity & delegation for how the two bindings differ.

The general pattern

Whatever the app, the configuration looks like this — an MCP server entry with the endpoint URL and an authorization header carrying your key:

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

The client examples below use the Property Management API endpoint. For an agent acting on behalf of a user, use https://api.etg24.de/api/internal/v1/mcp and your user-bound key instead — everything else stays the same.

Most apps hide this behind a form: server name, URL, API key. The menu names vary by app and version — look for MCP, Connections, or Integrations in the settings.

Claude

Claude Desktop — open the MCP servers section in Settings and add a server, or edit claude_desktop_config.json directly (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\):

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

Claude Code — register the server from the CLI:

claude mcp add --transport http etg24 https://api.etg24.de/propertymanagement/v2/mcp \
  --header "Authorization: Bearer $ETG24_API_KEY"

Cursor

Open Settings → MCP, add a new server, and select the HTTP transport:

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

Cursor saves this to ~/.cursor/mcp.json — edit that file directly if you prefer.

VS Code

Open the Command Palette (Ctrl+Shift+P / Cmd+Shift+P) and run MCP: Add Server, choose HTTP, enter the endpoint and the authorization header — or edit .vscode/mcp.json (project) / your user mcp.json:

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

ChatGPT

In ChatGPT, open Settings → Apps (the location of the MCP section varies by app version) and connect a new MCP server. Enter the etg24 endpoint URL and your API key when the form asks for credentials. If your app version only offers OAuth connectors, an MCP gateway that adds the Authorization header works as a bridge.

Mistral

Mistral supports MCP connections for agents and assistants. Add the etg24 endpoint as an MCP server (URL plus the Authorization: Bearer <API_KEY> header) in the workspace or agent settings.

Perplexity

Open Settings → MCP servers and add a custom server: give it a name, enter the etg24 endpoint URL, and provide your API key as the bearer token. After saving, the etg24 tools are available to your prompts.

opencode

Add the server to opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "etg24": {
      "type": "remote",
      "url": "https://api.etg24.de/propertymanagement/v2/mcp",
      "headers": { "Authorization": "Bearer ${env:ETG24_API_KEY}" }
    }
  }
}

Clients without remote MCP support

If your client only launches local MCP processes, bridge it with mcp-remote:

{
  "mcpServers": {
    "etg24": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://api.etg24.de/propertymanagement/v2/mcp",
        "--header",
        "Authorization: Bearer <API_KEY>"
      ]
    }
  }
}

Other agents

Any app that can connect a remote MCP server over HTTP with custom headers works the same way. Provide the endpoint URL and the authorization header, and you are connected.

Verify the connection

Ask the agent to list its tools — or look at the tool list in the app’s MCP section. The etg24 server advertises its meta-tools (meta.tools.search, meta.tool.describe, meta.tool.execute, meta.docs.search and more); domain tools are discovered at runtime through them. See the meta-tool workflow.

A good first prompt: “Use meta.tools.search to find tools for listing contacts, then list a few contacts.”

Example prompts

• “Find all units of the building ‘Schillerstraße 12’ and tell me which ones are vacant.”
• “Use meta.docs.search to look up how the tenant change workflow works, then summarize it.”
• “List the documents of unit X and check whether the latest statement is filed.”
• “Create a contact for Ada Lovelace and log a follow-up note.”

Before you let an agent change data, read the MCP security best practices.