What the Realestateapi MCP server does
The Realestateapi MCP server connects an MCP client to realestateapi.com for three real estate data operations. Property search finds matching records by city, state, and filters including off-market status, absentee ownership, and value ranges. Results can include the property address, owner, bedroom and bathroom counts, and estimated value.
Property detail retrieves a fuller record using a property ID or street address. Returned information can include ownership, estimated value, last sale, property characteristics, and mortgage data. Characteristics cover beds, baths, square footage, year built, and lot information.
The third operation is skip-trace lookup. Given an address, it returns the owner name and available phone numbers and email addresses. The README describes this information as regulated PII and says the service passes it through without storing it.
How it works
The Realestateapi MCP server can be reached in two ways. The hosted option uses the Pipeworx gateway at https://gateway.pipeworx.io/realestateapi/mcp. A client connected to this endpoint sees the three Realestateapi tools along with shared Pipeworx meta-tools. Those shared tools include routing and discovery functions such as ask_pipeworx, so the scoped endpoint can also route questions to other catalog data sources.
The full Pipeworx gateway is available at https://gateway.pipeworx.io/mcp when an agent needs every pack exposed directly. Both hosted URLs use the same gateway and data-source network; their direct tool listings differ.
A local stdio mode is also available through the npm package @pipeworx/mcp-realestateapi. In that mode, MCP messages use standard input and output, and the server exposes only the Realestateapi tools rather than the gateway’s shared meta-tools.
Setup and configuration
Add the hosted endpoint to an MCP client’s server configuration, or run the package with npx -y @pipeworx/mcp-realestateapi and configure the client to launch it as a stdio process. The hosted connection does not require installing the package locally. The standalone mode is documented as requiring no Pipeworx account or gateway round trip.
Each tool example supplies an _apiKey argument. The pack does not provide an API key on the user’s behalf, so callers must supply their own realestateapi.com key when invoking tools. The available material does not specify a required environment variable.
Tools and capabilities
realestateapi_property_search: Search by location and supported property filters, with a configurable result size.
realestateapi_property_detail: Look up full property information by ID or address.
realestateapi_skip_trace: Retrieve owner contact details for an address.
ask_pipeworx: On the hosted gateway connection, ask a natural-language question that the gateway routes to an appropriate tool.
Limitations and notes
The gateway pack endpoint includes shared Pipeworx tools in addition to the three pack-specific tools, so its tool count is larger than the pack’s documented list. The standalone Realestateapi MCP server does not include those shared tools. Skip-trace output contains regulated personal information and is described as passthrough data; users remain responsible for using it appropriately. The documentation does not define data coverage, result freshness, rate limits, or field availability beyond the listed outputs.