Zoopla MCP Server and API by Cotlet

dev.cotletPublished by cotlet.devOfficial publisherv1.0.2Updated Nov 11, 2026

Zoopla property listings portal MCP server: list my listings, update listing, reply to lead.

The publisher's own server: Cotlet

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that connects an assistant to Zoopla property listings so it can list, update listings and reply to leads.

What you can do
  • List the user's Zoopla property listings
  • Update an existing listing
  • Reply to incoming leads
  • No tool list is published, so the exact operations available are not documented beyond these three tasks.
When to use it
Useful for estate agents or property managers who already work with Zoopla and want an assistant to review their listings, make listing updates, or respond to leads without switching to the portal.
Requirements
A remote streamable HTTP endpoint at cotlet.dev; no local install. A Cotlet API key is required, sent as an Authorization header in the form Bearer followed by the key, obtained from the Cotlet API keys page.
Before you install
The server can change listing data and send replies to leads, so actions may be visible to customers. It requires a Cotlet API key in the Authorization header, which should be kept secret. Requests are routed through the third-party Cotlet service rather than Zoopla directly.

Installation

In SourceWeft

  1. Open Zoopla MCP Server and API by Cotlet in the dashboard and add it to a workspace.
  2. 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/dev.cotlet%2Fzoopla/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": {
    "zoopla-and-api-by-cotlet": {
      "type": "http",
      "url": "https://cotlet.dev/mcp/v1/zoopla/connect"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.2LatestNov 11, 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 listedRequired15 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.

Other Cotlet integrations