France Dvf vs Planwire MCP
A side-by-side look at the France Dvf and Planwire MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose France Dvf for real estate work as a local process; choose Planwire MCP 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 France Dvf when
- You need dedicated capabilities in the Real Estate domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Choose Planwire 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:
PLANWIRE_API_KEY. - You want tools like
search_planning_applications, nearby_planning_applications, get_planning_application.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Real Estate | Real Estate |
| Quality signal | 37/100 · Fair | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Free | Freemium |
| Required env vars | None listed | PLANWIRE_API_KEY |
Tools & capabilities
France Dvf tools
No tool names declared yet. Check the project README from the listing page.
Planwire MCP tools 4
search_planning_applicationsSearch by keyword, council, postcode, status, type, or date range.nearby_planning_applicationsFind applications near a latitude/longitude point.get_planning_applicationFetch one application by PlanWire application id.list_councilsList covered councils and their IDs.
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.
France Dvf
{
"mcpServers": {
"france-dvf": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-france-dvf"
]
}
}
}
Planwire MCP
{
"mcpServers": {
"beshogun-planwire-mcp": {
"command": "npx",
"args": [
"-y",
"planwire-mcp"
],
"env": {
"PLANWIRE_API_KEY": "YOUR_PLANWIRE_API_KEY_HERE"
}
}
}
}
Frequently asked questions
France Dvf is categorized under Real Estate and uses a local stdio subprocess. Planwire MCP belongs to Real Estate and uses a local stdio subprocess. Pick France Dvf for real estate work and Planwire MCP 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.
France Dvf is listed as free. Auth: no auth required. Planwire MCP is listed as freemium — a free tier with paid plans. Auth: api key required. 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 france-dvf and beshogun-planwire-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, France Dvf has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Planwire MCP has 55/100 (Good) with 3 views, 0 installs and 0 GitHub stars.