Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Zillow Working API MCP Server show me property listings in Seattle under $500k"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
用于访问 Zillow Working Api API 的 MCP 服务器。
EMCP 是一个强大的 MCP 服务器管理平台，让您无需手动配置即可快速使用各种 MCP 服务器！
🌐 访问 EMCP 平台
📝 注册并登录账号
🎯 进入 MCP 广场，浏览所有可用的 MCP 服务器
🔍 搜索或找到本服务器（bach-zillow_working_api）
🎉 点击 "安装 MCP" 按钮
✅ 完成！即可在您的应用中使用
✨ 零配置：无需手动编辑配置文件
🎨 可视化管理：图形界面轻松管理所有 MCP 服务器
🔐 安全可靠：统一管理 API 密钥和认证信息
🚀 一键安装：MCP 广场提供丰富的服务器选择
📊 使用统计：实时查看服务调用情况
立即访问 EMCP 平台 开始您的 MCP 之旅！
Related MCP server: Zillow MCP Server
这是一个 MCP 服务器，用于访问 Zillow Working Api API。
PyPI 包名: bach-zillow_working_api
版本: 1.0.0
传输协议: stdio
pip install bach-zillow_working_apipip install -e .# 运行（uvx 会自动安装并运行）
uvx --from bach-zillow_working_api bach_zillow_working_api
# 或指定版本
uvx --from bach-zillow_working_api@latest bach_zillow_working_apipython server.py# 安装
pip install bach-zillow_working_api
# 运行（命令名使用下划线）
bach_zillow_working_api此 API 需要认证。请设置环境变量:
export API_KEY="your_api_key_here"变量名 | 说明 | 必需 |
| API 密钥 | 是 |
| 不适用 | 否 |
| 不适用 | 否 |
编辑 Cursor MCP 配置文件 ~/.cursor/mcp.json:
{
"mcpServers": {
"bach-zillow_working_api": {
"command": "uvx",
"args": ["--from", "bach-zillow_working_api", "bach_zillow_working_api"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}编辑 Claude Desktop 配置文件 claude_desktop_config.json:
{
"mcpServers": {
"bach-zillow_working_api": {
"command": "uvx",
"args": ["--from", "bach-zillow_working_api", "bach_zillow_working_api"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}此服务器提供以下工具:
api_moved_to_httpsrapidapicomoneapiprojectapizllw_working_api❗️API moved. Check the params tab. New URL: https://rapidapi.com/oneapiproject/api/zllw-working-api
端点: GET /api_moved
参数:
new_url (string) 必需: ➡️ This API is moved to a new URL: https://rapidapi.com/oneapiproject/api/zllw-working-api Subscribe to the new API to keep the service uninterrupted. Change to the new API's base URL and headers. Get 25% more requests on the new API. For any queries, feel free to contact: oneapi.project@gmail.com We will be happy to help.
传输协议: stdio
HTTP 客户端: httpx
MIT License - 详见 LICENSE 文件。
此服务器由 API-to-MCP 工具生成。
版本: 1.0.0
❗️API moved. Check the params tab. New URL: https://rapidapi.com/oneapiproject/api/zllw-working-api
| Name | Required | Description | Default |
|---|---|---|---|
| new_url | Yes | ➡️ This API is moved to a new URL: https://rapidapi.com/oneapiproject/api/zllw-working-api Subscribe to the new API to keep the service uninterrupted. Change to the new API's base URL and headers. Get 25% more requests on the new API. For any queries, feel free to contact: oneapi.project@gmail.com We will be happy to help. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. However, it only mentions an API move and subscription details, with no information on what the tool does (e.g., read/write operations, side effects, rate limits, or authentication needs). This leaves the agent with no understanding of the tool's behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is brief but not appropriately structured for a tool definition; it is front-loaded with a warning emoji and administrative text, but lacks functional content. Every sentence fails to earn its place as it does not describe the tool's purpose or usage, making it inefficient and under-specified rather than concise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of annotations, no output schema, and a description that omits functional details, the description is incomplete. It does not explain what the tool does, its inputs/outputs, or behavioral traits, leaving the agent unable to use it effectively. This is inadequate even for a simple tool with one parameter.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage, with the single parameter 'new_url' well-documented in the schema. The description adds no additional meaning beyond the schema, as it repeats the URL and subscription details. With high schema coverage, the baseline is 3, but the description does not compensate or enhance parameter understanding.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description fails to state what the tool does; it only provides a migration notice about an API move. The tool's name suggests it might be related to an API, but the description gives no functional purpose (e.g., what operations it performs). This is misleading as it implies the tool is for migration rather than its actual function, which is unclear.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There are no guidelines on when to use this tool vs. alternatives. The description mentions checking the params tab and a new URL, but this is administrative information, not usage guidance. It does not specify the tool's intended context, prerequisites, or exclusions, making it unhelpful for an AI agent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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.
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.
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.
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.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Zillow for-sale, for-rent and sold listings, and full property details, as structured JSON.
Zillow MCP for AI agents: property data, Zestimates & listings — 300+ fields per home. Free tier.
Zillow homes and agent contacts for AI agents — search by ZIP, by URL, or look up a zpid.
Redfin listings, sale-comps, and neighborhood market data via natural-language queries.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/BACH-AI-Tools/bachai-zillow-working-api'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
