MCP.so
Sign In

ATTOM MCP Server

@jmclaughlin724

About ATTOM MCP Server

No overview available yet

Basic information

Category

Other

License

MIT

Runtime

node

Transports

stdio

Publisher

jmclaughlin724

Config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is ATTOM MCP Server?

The ATTOM MCP Server is a Model Context Protocol server that surfaces the ATTOM Data property dataset to AI agents and traditional applications. It is written in TypeScript with ES modules and supports both HTTP and stdio transports, fallback strategies, automatic retries, and development tooling.

How to use ATTOM MCP Server?

Install via git clone and npm ci, configure environment variables (ATTOM_API_KEY required), then launch using npm run mcp:http or npm run mcp:stdio. Interact via the attom_query MCP tool, specifying a kind endpoint key and params object.

Key features of ATTOM MCP Server

  • Dual transport: HTTP and stdio.
  • Smart fallback logic for address-to-ID and geoId derivation.
  • Auto-retry algorithm for sales comparables (widens search ranges).
  • Advanced filters (include0SalesAmounts, includeFullSalesOnly, onlyPropertiesWithPool).
  • Strict TypeScript type safety with Zod validation.
  • OpenAPI YAML generation for client SDKs.

Use cases of ATTOM MCP Server

  • Providing property data to AI agents via MCP.
  • Querying property basic profiles by address.
  • Retrieving sales comparables by address or property ID.
  • Integrating real estate data into automated workflows.

FAQ from ATTOM MCP Server

What is required to run the server?

Node.js 18+ and an ATTOM API key. Optionally, a Google Maps API key for address normalization.

Does the server support both HTTP and stdio?

Yes. Use npm run mcp:http for HTTP transport and npm run mcp:stdio for stdio transport. Both expose the same MCP interface.

How does the comparables auto-retry work?

If ATTOM returns "Unable to locate a property record" on the first attempt, the server widens the sqFeetRange by 30% and sets yearBuiltRange to 40 years, then retries once.

Where is data cached?

Data is cached in an in-memory TTL map (default 3600 seconds). The cache adapter can be swapped for Redis or Memcached.

What authentication is used?

Authentication uses an ATTOM API key set in the ATTOM_API_KEY environment variable. No OAuth or other auth is described.

Comments

More Other MCP servers