Batchdata vs Realestateapi
A side-by-side look at the Batchdata and Realestateapi MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Batchdata for real estate work as a local process; choose Realestateapi for real estate as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Batchdata when
- You need dedicated capabilities in the Real Estate domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You want tools like
batchdata_property_lookup, batchdata_property_search, batchdata_skip_trace.
Choose Realestateapi when
- You need dedicated capabilities in the Real Estate domain.
- You prefer a local stdio subprocess transport.
- You want tools like
realestateapi_property_search, realestateapi_property_detail, realestateapi_skip_trace.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Real Estate | Real Estate |
| Quality signal | 61/100 · Good | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 3 | 3 |
| Full listing | View Batchdata | View Realestateapi |
Tools & capabilities
Batchdata tools 3
batchdata_property_lookupLook up full property attributes (owner, building characteristics, valuation, sale/tax history) for one or more known addresses. Requires a BatchData API token via _apiKey. Example: batchdata_property_lookup({ street: "1011 Rosegold St", city: "Franklin Square", state: "NY", zip: "11010", _apiKey: "your-token" })batchdata_property_searchSearch BatchData's 155M+ property database by location and attribute filters (e.g. "Phoenix, AZ"), with skip/take pagination. Returns matching property records plus a meta count of total matches. Requires a BatchData API token via _apiKey. Example: batchdata_property_search({ query: "Phoenix, AZ", take: 25, _apiKey: "your-token" })batchdata_skip_traceSkip-trace an address (optionally with an owner name) to resolve owner contact info — phone numbers and emails. WARNING: skip-trace results carry DPPA/GLBA permissible-use obligations; the caller is solely responsible for lawful use of the returned contact data. Requires a BatchData API token via _apiKey. Example: batchdata_skip_trace({ street: "1011 Rosegold St", city: "Franklin Square", state: "NY", zip: "11010", _apiKey: "your-token" })
Realestateapi tools 3
realestateapi_property_searchSearch properties by city/state/filters (off-market, absentee-owner, value range) — returns matching properties with address, owner, beds/baths, and estimated value. Example: realestateapi_property_search({ city: "Austin", state: "TX", absentee_owner: true, value_max: 400000, size: 25, _apiKey: "your-key" })realestateapi_property_detailGet full property detail by id or address — returns owner, estimated value, last sale, characteristics (beds/baths/sqft/year/lot), and mortgage. Example: realestateapi_property_detail({ address: "123 Main St, Austin, TX 78701", _apiKey: "your-key" })realestateapi_skip_traceSkip-trace owner contact info for an address — returns the owner name plus phone numbers and emails. Regulated PII: pure passthrough, nothing is stored. Example: realestateapi_skip_trace({ address: "123 Main St, Austin, TX 78701", _apiKey: "your-key" })
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Batchdata
{
"mcpServers": {
"batchdata": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-batchdata"
]
}
}
}
Realestateapi
{
"mcpServers": {
"realestateapi": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-realestateapi"
]
}
}
}
Frequently asked questions
Batchdata is categorized under Real Estate and uses a local stdio subprocess. Realestateapi belongs to Real Estate and uses a local stdio subprocess. Pick Batchdata for real estate work and Realestateapi for real estate.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Batchdata is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Realestateapi has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add batchdata and realestateapi as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Batchdata has a quality signal of 61/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Realestateapi has 59/100 (Good) with 1 views, 0 installs and 0 GitHub stars.