Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Zillow for-sale, for-rent and sold listings, and full property details, as structured JSON.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
HASDATA_API_KEY, x-api-key标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"zillow": {
"command": "npx",
"args": [
"-y",
"@hasdata/zillow-mcp"
],
"env": {
"HASDATA_API_KEY": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add --transport http zillow 'https://mcp.hasdata.com/mcp?apis=zillow' --header 'x-api-key: your-value'claude mcp add zillow --env HASDATA_API_KEY=your-value -- npx -y @hasdata/zillow-mcp运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"zillow": {
"url": "https://mcp.hasdata.com/mcp?apis=zillow",
"headers": {
"x-api-key": "your-value"
}
}
}
}粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"zillow": {
"command": "npx",
"args": [
"-y",
"@hasdata/zillow-mcp"
],
"env": {
"HASDATA_API_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"zillow": {
"type": "http",
"url": "https://mcp.hasdata.com/mcp?apis=zillow",
"headers": {
"x-api-key": "your-value"
}
}
}
}粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"zillow": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@hasdata/zillow-mcp"
],
"env": {
"HASDATA_API_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
你的选择通过 Cookie 保存在这台设备上,无需账户。
x-api-key 机密 必填 HTTP header这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过域名 hasdata.com 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:HASDATA_API_KEY, x-api-key
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于–,最新版本(1.0.8)于43天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Reelsaw
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Drive a self-hosted Reelsaw: turn long videos into vertical clips, edit, re-render and export them.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
A hosted Zillow MCP server that gives Claude, Cursor, Windsurf and any other MCP client two read-only Zillow tools. Search for-sale, for-rent and sold listings with rich filters, and read a single property in full, all as structured JSON, with nothing to host.
It reads public listing pages on Zillow.com that a signed-out visitor can see.
1,000 free credits every month, no card required, which is 100 Zillow calls at the base rate.
https://mcp.hasdata.com/mcp?apis=zillow
An MCP client and a HasData API key from the dashboard, free to create with no card, and the free tier covers about 100 calls a month at the 10-credit rate. This is a remote server, so the simplest path is a URL and an x-api-key header, with no container to run. A client that only speaks stdio reaches it through a thin launcher, published as @hasdata/zillow-mcp on npm and hasdata-zillow-mcp on PyPI, shown below.
The server URL is the same for every client. We run it hands-on in Claude Code and Claude Desktop. The other blocks follow each client's own documented format for a remote server.
| Field | Value |
|---|---|
| URL | https://mcp.hasdata.com/mcp?apis=zillow |
| Transport | HTTP, streamable |
| Auth header | x-api-key: HASDATA_API_KEY |
Clients with OAuth support can add the same URL as a connector and sign in without putting a key in a config file.
Claude Code
claude mcp add --transport http zillow "https://mcp.hasdata.com/mcp?apis=zillow" \
--header "x-api-key: HASDATA_API_KEY"
Claude Desktop
Settings, then Connectors, then Add custom connector, then paste https://mcp.hasdata.com/mcp?apis=zillow and sign in.
For the config-file route, Claude Desktop loads only local (stdio) servers, so it reaches a remote server through a stdio launcher. The @hasdata/zillow-mcp package is that launcher, and it reads the key from the environment. Add this to claude_desktop_config.json:
{
"mcpServers": { "zillow": { "command": "npx", "args": ["-y", "@hasdata/zillow-mcp"], "env": { "HASDATA_API_KEY": "YOUR_KEY" } } } }
For Python instead of Node, swap the launcher for the PyPI package, which uvx runs without a manual install:
{
"mcpServers": { "zillow": { "command": "uvx", "args": ["hasdata-zillow-mcp"], "env": { "HASDATA_API_KEY": "YOUR_KEY" } } } }
Cursor
~/.cursor/mcp.json for every project, or .cursor/mcp.json for one:
{
"mcpServers": { "zillow": { "url": "https://mcp.hasdata.com/mcp?apis=zillow", "headers": { "x-api-key": "HASDATA_API_KEY" } } } }
Windsurf
~/.codeium/windsurf/mcp_config.json. Windsurf calls the field serverUrl, not url:
{
"mcpServers": { "zillow": { "serverUrl": "https://mcp.hasdata.com/mcp?apis=zillow", "headers": { "x-api-key": "HASDATA_API_KEY" } } } }
VS Code
.vscode/mcp.json in the workspace:
{
"servers": { "zillow": { "type": "http", "url": "https://mcp.hasdata.com/mcp?apis=zillow", "headers": { "x-api-key": "HASDATA_API_KEY" } } } }
Prompts, not code. Paste one in and the agent picks the tool itself. Each is annotated with the calls it takes, because every successful call costs 10 credits.
Search for-sale homes in Austin, TX with at least three beds under $600k, sorted newest first, and give me the ten most recent with price and days on market.
*One call, 10 credits. Price, beds, area and days on market come back on the search result.*
Take the top result and pull its full detail: price history, tax history, the price estimate, and the assigned schools.
*One call, 10 credits. Those live on the property page, which the details tool reads by URL.*
Find for-rent condos in Austin that allow cats, then pull the rental estimate on the three cheapest.
*Four calls, 40 credits. One search, then one property call for each of the three.*
For this property URL, give me the list price, the price estimate, and the last three sales in its price history.
*One call, 10 credits.*
A search result is enough to rank and shortlist. Price history, tax history, the estimate, schools and the agent come from the property call, so a prompt that shortlists then inspects three homes is one search plus three property calls.
| Tool | What it returns |
|---|---|
hasdata_zillow_listing_getRealEstateListings | Each listing with address, Zillow URL/zpid, price, Zestimate, beds/baths, sqft, home type, status, days on Zillow, coordinates, thumbnail, and listing agent. 10 credits a call |
hasdata_zillow_property_getPropertyDetails | Address, list price, Zestimate and Rent Zestimate, price and tax history, beds/baths, living area, lot size, year built, home type, HOA, days on Zillow, listing…. 10 credits a call |
Two tools, read-only. Samples below are trimmed from real calls, and the numbers move as the market moves. Read them as shapes. Each tool name links to its endpoint reference, which carries the full field list.
The samples are the payload, not the whole response. A tools/call result carries one text block, and that text is itself JSON holding url, status, text and json, with the scraped data under json. From a raw JSON-RPC response the path is result.content[0].text, parsed, then .json. A chat client unwraps that for you and code talking to the endpoint directly does not.
hasdata_zillow_listing_getRealEstateListings
A page of listings by location keyword, filtered.
| Parameter | Type | Required | Notes |
|---|---|---|---|
keyword | string | yes | The location to search, such as Austin, TX |
type | string | yes | forSale, forRent or sold |
price_min_ / price_max_ | number | Price band | |
beds_min_ / beds_max_ / baths_min_ / baths_max_ | number | Bed and bath bands | |
homeTypes__ | array | house, condo, townhome, multiFamily, apartment, lot, manufactured | |
daysOnZillow | number/string | 1, 7, 14, 30, 90, 6m, 12m and up | |
sort | string | newest, priceLowToHigh, priceHighToLow, squareFeet and more | |
page | number | Result page |
The reference also documents square-footage, lot-size, year-built and HOA bands, plus otherAmenities__, views__, pets__, listingType, propertyStatus__, listingPublishOptions__ and more.
Returns searchInformation with totalResults, a properties array, and pagination whose nextPage is the URL of the following page. Each property carries id, url, homeType, status, price, currency, a rentZestimate rental estimate, daysOnZillow, area in square feet, addressRaw and a structured address, latitude, longitude, beds, baths, listingDetails, mediaDetails and photos.
{
"id": "60134551", "url": "https://www.zillow.com/homedetails/6116-Speyside-Dr-Austin-TX-78754/60134551_zpid/", "homeType": "SINGLE_FAMILY", "status": "FOR_SALE", "price": 320000, "currency": "$", "rentZestimate": 2286, "daysOnZillow": 0, "area": 2277, "address": { "street": "6116 Speyside Dr", "city": "Austin", "state": "TX", "zipcode": "78754" }, "beds": 4, "baths": 3 }
hasdata_zillow_property_getPropertyDetails
One property in full, by its URL.
| Parameter | Type | Required | Notes |
|---|---|---|---|
url | string | yes | A Zillow property URL, the url field from a listing result |
extractAgentEmails | boolean | Attempt to pull the listing agent's email. Adds 5 credits, so the property call costs 15 instead of 10 |
Returns the full page: price, currency, fees, beds, baths, area, yearBuilt, homeType, mlsId, a structured address and geo, the description and highlights, photos, schools, daysOnZillow, views, saves, an agentInfo block, and priceHistory, taxHistory and mortgage arrays. Zillow's own price estimate arrives in a zestimate object holding zestimate, an estimatedSaleRange and a rentZestimate. Read it as an estimate, not as a confirmed value.
areais an object here,{ livingArea, livingAreaUnits }, not the flat number the search tool returns. Readarea.livingAreafor the square footage on a property page, or a numeric comparison likearea > 2000silently fails against an object.
{
"id": 60134551, "status": "FOR_SALE", "price": 320000, "currency": "USD", "yearBuilt": 2002, "beds": 4, "baths": 3, "area": { "livingArea": 2277, "livingAreaUnits": "Square Feet" }, "fees": { "monthlyHoaFee": "$500 annually" }, "zestimate": { "zestimate": 318100, "estimatedSaleRange": "$302K - $334K", "rentZestimate": 2286 }, "address": { "street": "6116 Speyside Dr", "county": "Travis County" }, "agentInfo": { "agentName": "Marie Coleman", "brokerName": "eXp Realty" }, "priceHistory": [{ "date": "2026-08-24", "price": 320000, "event": "listedForSale" }], "schools": { "elementarySchool": { "name": "Bluebonnet Trail", "district": "Manor ISD" } } }
The server ships 2 prompts, ready-made workflows a client can offer instead of making the user compose a tool call.
| Prompt | What it does |
|---|---|
zillow_listings | Find homes for sale, for rent or sold in an area. |
zillow_property | Get the full details of one Zillow property. |
Alongside them the server exposes 11 resources, one per parameter whose accepted values are a fixed list. Reading one is cheaper than learning the vocabulary from a rejected call, and it costs no credits. Each URI is hasdata://zillow/ .
只显示了开头部分;其余内容请在仓库中阅读