Casa Property MCP server
{
"mcpServers": {
"casaintelligence-casa-property": {
"type": "http",
"url": "https://api.casaintelligence.com.au/mcp/public/v1/messages"
}
}
}{
"mcpServers": {
"casaintelligence-casa-property": {
"type": "http",
"url": "https://api.casaintelligence.com.au/mcp/public/v1/messages"
}
}
}{
"mcpServers": {
"casaintelligence-casa-property": {
"type": "http",
"url": "https://api.casaintelligence.com.au/mcp/public/v1/messages"
}
}
}{
"servers": {
"casaintelligence-casa-property": {
"type": "http",
"url": "https://api.casaintelligence.com.au/mcp/public/v1/messages"
}
}
}{
"mcpServers": {
"casaintelligence-casa-property": {
"type": "http",
"url": "https://api.casaintelligence.com.au/mcp/public/v1/messages"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.0.0
Indicative SEQ Australia property planning intelligence: zones, overlays, subdivision, DA stats.
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.
This server has not seen a commit in unknown. It may still work, but nobody is currently fixing it — check the alternatives before you build on it.