Property

You run a minimal Model Context Protocol (MCP) server that connects Claude AI to real estate data via the ATTOM Data API. This server lets you query property information and receive structured results, making it easier to integrate live property data into Claude-powered workflows.

How to use

To use the Property MCP Server with an MCP client, start the local server and point your client to it. The server exposes a property information tool that retrieves details from the ATTOM Data API using your API key. When you run the server, you can test queries locally to verify responses before connecting Claude to your data.

How to install

Prerequisites: you need Python and pip installed on your machine. You also need access to the ATTOM Data API key.

pip install -r requirements.txt

Create your environment file and add your ATTOM API key.

echo "ATTOM_API_KEY=your_key_here" > .env

Test the tool locally to ensure the integration works before starting the server.

python test_tool.py "1600 Amphitheatre Parkway, Mountain View, CA 94043"

Run the server locally for Claude Desktop usage.

python -m mcp_server.server

Additional setup notes

If you plan to integrate with Claude Desktop, you may configure Claude to launch the MCP server as a local process. You can specify the Python interpreter, the module to run, and the working directory along with any necessary environment variables.

Configuration and structure

Key components of the server include the entry point, the property tool interface, the HTTP client for ATTOM, environment configuration, and error handling. The typical project layout looks like this.

mcp_server/
├── server.py            # Entry point
├── tools/
│   └── property_info_tool.py  # tool interface
├── services/
│   └── attom_client.py  # HTTP client
├── config.py            # Environment config
└── utils/
    └── errors.py        # Exceptions

Error handling

Errors are returned as structured JSON responses to simplify downstream processing. Typical error payloads indicate whether an error occurred, provide a message, and include a status code.

{
  "error": True,
  "message": "ATTOM API error: 400 Bad Request",
  "status_code": 400
}

Notes on config and environment

The server relies on an API key stored in a local environment file. Ensure your environment includes the required variables when starting the server.

Troubleshooting tips

• Verify ATTOM_API_KEY is set in .env
• Check network access to ATTOM API endpoints
• Inspect error responses for HTTP status codes and messages

Available tools

property_info_tool

Tool interface that retrieves property information from ATTOM Data API via the MCP server