Skip to main content
Glama
BACH-AI-Tools

Zillow Working API MCP Server

by BACH-AI-Tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Zillow Working API MCP Server

No user-submitted related servers found.

    Related Servers

    • Zillow56 MCP Server

      BACH-AI-Tools
      A
      license
      C
      quality
      D
      maintenance
      Enables access to the Zillow56 API to search for real estate listings and rental market trends using locations, coordinates, or specific property filters. It also provides comprehensive housing market snapshots and historical data based on the Zillow Home Value Index (ZHVI).
      37
      MIT

    • Zillow MCP Server

      sap156
      A
      license
      Not graded
      quality
      F
      maintenance
      Provides real-time access to Zillow real estate data, enabling property search, details, Zestimates, market trends, and mortgage calculations via natural language.
      2 npm
      48
      MIT

    • Zillow MCP Server

      EmilyThaHuman
      A
      license
      Not graded
      quality
      D
      maintenance
      Integrates Zillow real estate data with AI assistants, enabling property search, neighborhood insights, and affordability calculations through natural language.
      2 npm
      1
      MIT

    • zillow-mcp

      chrischall
      A
      license
      A
      quality
      A
      maintenance
      Enables natural-language access to Zillow real-estate data, including property search, details, Zestimate history, saved searches/homes, and market reports, by routing requests through the user's authenticated browser session.
      1
      20
      555 npm
      MIT

    • Zillow MCP Server

      HasData
      A
      license
      A
      quality
      A
      maintenance
      Enables searching Zillow for-sale, for-rent, and sold listings with rich filters and retrieving complete property details as structured JSON, with no Zillow account required.
      2
      61 npm
      149 PyPI
      10
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as handling the API migration, making it distinct by default.

    Naming Consistency5/5

    A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name, while long and descriptive, does not conflict with any other naming patterns.

    Tool Count2/5

    A single tool is too few for a server labeled as an API server, as it suggests minimal functionality. Typically, an API server would offer multiple endpoints or operations, making this count insufficient for meaningful interaction.

    Completeness1/5

    The tool only provides a notification about an API move, lacking any actual API operations like data retrieval, updates, or queries. This is severely incomplete for an API server, as it offers no functional surface for agents to perform tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources