Zestio

de.zestioPublished by zestio.deOfficial publisherv1.0.0Updated Oct 28, 2026

MCP server for real-estate agents: listings, CRM, German market data and AI media tools.

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Remote Zestio MCP server that gives an assistant access to real-estate listings, CRM, German market data and AI media tools.

What you can do
  • Work with property listings and real-estate records through the Zestio platform.
  • Manage CRM data such as contacts and related customer information.
  • Look up German real-estate market data.
  • Use AI media tools for property-related content.
  • No individual tools are documented, so exact actions depend on the connected account.
When to use it
Useful for real-estate agents and teams already on Zestio who want an assistant to work with their listings, CRM records and German market data without switching tools.
Requirements
A remote MCP endpoint at the Zestio domain over streamable HTTP. Requires a Zestio API key, sent as a bearer token in the Authorization header; keys start with zest_ and are created in the Zestio dashboard. Network access to Zestio is needed.
Before you install
The API key is a secret sent in the Authorization header and grants access to the account's listings and CRM data; keep it out of shared logs and revoke it if exposed. The server can likely read and change business records, so review write actions before approving them. Data is exchanged with the Zestio platform.

Installation

In SourceWeft

  1. Open Zestio in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/de.zestio%2Fzestio-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "zestio": {
      "type": "http",
      "url": "https://www.zestio.de/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestOct 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.