Skip to main content
Glama
BACH-AI-Tools

Zillow Working API MCP Server

README.md
# Zillow Working Api MCP Server

[English](./README_EN.md) | 简体中文 | [繁體中文](./README_ZH-TW.md)

用于访问 Zillow Working Api API 的 MCP 服务器。

## 🚀 使用 EMCP 平台快速体验

**[EMCP](https://sit-emcp.kaleido.guru)** 是一个强大的 MCP 服务器管理平台,让您无需手动配置即可快速使用各种 MCP 服务器!

### 快速开始:

1. 🌐 访问 **[EMCP 平台](https://sit-emcp.kaleido.guru)**
2. 📝 注册并登录账号
3. 🎯 进入 **MCP 广场**,浏览所有可用的 MCP 服务器
4. 🔍 搜索或找到本服务器(`bach-zillow_working_api`)
5. 🎉 点击 **"安装 MCP"** 按钮
6. ✅ 完成!即可在您的应用中使用

### EMCP 平台优势:

- ✨ **零配置**:无需手动编辑配置文件
- 🎨 **可视化管理**:图形界面轻松管理所有 MCP 服务器
- 🔐 **安全可靠**:统一管理 API 密钥和认证信息
- 🚀 **一键安装**:MCP 广场提供丰富的服务器选择
- 📊 **使用统计**:实时查看服务调用情况

立即访问 **[EMCP 平台](https://sit-emcp.kaleido.guru)** 开始您的 MCP 之旅!


---

## 简介

这是一个 MCP 服务器,用于访问 Zillow Working Api API。

- **PyPI 包名**: `bach-zillow_working_api`
- **版本**: 1.0.0
- **传输协议**: stdio


## 安装

### 从 PyPI 安装:

```bash
pip install bach-zillow_working_api
```

### 从源码安装:

```bash
pip install -e .
```

## 运行

### 方式 1: 使用 uvx(推荐,无需安装)

```bash
# 运行(uvx 会自动安装并运行)
uvx --from bach-zillow_working_api bach_zillow_working_api

# 或指定版本
uvx --from bach-zillow_working_api@latest bach_zillow_working_api
```

### 方式 2: 直接运行(开发模式)

```bash
python server.py
```

### 方式 3: 安装后作为命令运行

```bash
# 安装
pip install bach-zillow_working_api

# 运行(命令名使用下划线)
bach_zillow_working_api
```

## 配置

### API 认证

此 API 需要认证。请设置环境变量:

```bash
export API_KEY="your_api_key_here"
```

### 环境变量

| 变量名 | 说明 | 必需 |
|--------|------|------|
| `API_KEY` | API 密钥 | 是 |
| `PORT` | 不适用 | 否 |
| `HOST` | 不适用 | 否 |



### 在 Cursor 中使用

编辑 Cursor MCP 配置文件 `~/.cursor/mcp.json`:


```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 配置文件 `claude_desktop_config.json`:

```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](./LICENSE) 文件。

## 开发

此服务器由 [API-to-MCP](https://github.com/BACH-AI-Tools/api-to-mcp) 工具生成。

版本: 1.0.0

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