Permisapi MCP vs Realestateapi
A side-by-side look at the Permisapi MCP 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 Permisapi MCP 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 Permisapi MCP 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 have the keys it needs:
PERMISAPI_KEY. - You want tools like
search_permits, get_permit_details, fuzzy_search_addresses.
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 | 56/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Freemium | Not declared |
| Required env vars | PERMISAPI_KEY |
Tools & capabilities
Permisapi MCP tools 18
search_permitsFreeget_permit_detailsFreefuzzy_search_addressesFreefind_dvf_neighborsProget_mdb_scoreProget_score_explanationProget_plu_zoningProget_risksProget_parcelle_geometryProget_existing_buildingsProget_parcelle_by_idProget_neighbor_parcelsPro- +6 more on the listing page
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: "yo…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_trace
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.
Permisapi MCP
{
"mcpServers": {
"evan-crx-permisapi-mcp": {
"command": "uvx",
"args": [
"--python",
"3.11",
"permisapi-mcp"
],
"env": {
"PERMISAPI_KEY": "YOUR_PERMISAPI_KEY_HERE"
}
}
}
}
Realestateapi
{
"mcpServers": {
"realestateapi": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-realestateapi"
]
}
}
}
Frequently asked questions
Permisapi MCP is categorized under Real Estate and uses a local stdio subprocess. Realestateapi belongs to Real Estate and uses a local stdio subprocess. Pick Permisapi MCP 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.
Permisapi MCP is listed as freemium — a free tier with paid plans. 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 evan-crx-permisapi-mcp and realestateapi as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Permisapi MCP has a quality signal of 56/100 (Good) with 3 views, 0 installs and 3 GitHub stars. Realestateapi has 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars.