Skip to main content

BatchData MCP Server Now Available - November 2025

Announcing the general availability (GA) release of the BatchData MCP server

Written by Charles Parra

Release Date: November 2025

We're excited to announce the launch of the BatchData MCP (Model Context Protocol) Server, a new way to access BatchData's real estate property intelligence capabilities through AI assistants and large language models.

What is the BatchData MCP Server?

The BatchData MCP Server exposes BatchData's powerful property data APIs through a standardized protocol that AI assistants can use to help you with property research, skip tracing, phone verification, and address validation tasks.

MCP Server Endpoint: https://mcp.batchdata.com

Key Features

9 Specialized Tools Across 5 Categories

Property Intelligence (2 tools)

  • Property Lookup: Get comprehensive property details including lot characteristics, sale history, valuations, liens, mortgages, tax assessments, and building permits

  • Comparable Property Analysis: Perform comparative market analysis (CMA) with automated valuation, average prices, and comparable property details

Skip Tracing (1 tool)

  • Property Skip Trace: Find contact information for property owners including phone numbers, email addresses, and mailing addresses with full TCPA and DNC compliance flags

    • Powered by V3 Skip Trace API: Returns up to 3 persons per property (vs. 1 person in V1)

    • Enhanced Data Coverage: Multiple household members and property owners

    • Flexible TCPA Handling: Phone numbers include a tcpa boolean flag for programmatic filtering

    • Compliance by Default: TCPA-restricted phones are included with clear indicators, allowing you to implement your own compliance logic

Phone Verification (3 tools)

  • Full Phone Verification: Complete verification details including carrier, type, reachability, DNC status, and TCPA status

  • DNC Status Check: Quick Do Not Call registry lookup

  • TCPA Status Check: Quick TCPA litigator list verification

Address Verification (3 tools)

  • Address Verification: Normalize and verify addresses to USPS standards with detailed address components

  • Geocoding: Convert addresses to geographic coordinates

  • Reverse Geocoding: Convert coordinates to street addresses

How to Get Started

Authentication

MCP tools require authentication. Supported AI assistants sign in with your BatchData account through OAuth, with no API token needed. See OAuth Authentication for MCP Server for setup steps. Custom MCP clients that do not support OAuth can use an API token. Include the token in the Authorization header:

Authorization: Bearer YOUR_API_KEY

Using the MCP Server

You can integrate it with:

  • AI assistant platforms that support the Model Context Protocol

  • Custom applications using the MCP protocol

  • LLM-powered workflows requiring property data access

Example Use Cases

  1. Property Research Lookup comprehensive property details for investment analysis by providing an address or parcel number. Get instant access to property characteristics, sale history, liens, and market data.

  2. Market Analysis Find comparable properties to support valuation and pricing decisions. The tool returns aggregated metrics including estimated value, average price per square foot, and detailed comparable property information.

  3. Owner Contact Discovery Skip trace properties to find owner contact information for marketing campaigns. Using our new V3 Skip Trace endpoint, results include up to 3 persons per property with multiple phone numbers and email addresses. Each phone number includes clear TCPA and DNC compliance flags, giving you complete visibility while maintaining regulatory compliance.

  4. Phone Verification Verify phone numbers before making calls to ensure compliance with regulations. Check for TCPA litigators and DNC registry status to avoid potential violations.

  5. Address Validation Normalize and verify addresses for accurate data processing and mail delivery. Get USPS-validated addresses with ZIP+4, county information, and geocoded coordinates.

Compliance Features

The MCP Server includes built-in compliance indicators to help you stay compliant with regulations:

  • TCPA Litigator Flags: Identify phone numbers belonging to known TCPA litigators

  • DNC Registry Status: Check if numbers are on the Do Not Call registry

  • Phone Reachability: Verify numbers are active before attempting contact

  • Address Validity: Ensure addresses meet USPS delivery standards

Technical Details

Authentication: OAuth sign-in, or a Bearer API token for MCP clients without OAuth support

Rate Limits: Subject to standard BatchData API rate limits

Transport: Streamable HTTP

Common Response Codes

  • 200: Success - request processed successfully

  • 401: Authentication failed - invalid or missing credentials

  • 429: Rate limit exceeded - retry after delay

  • 400/422: Invalid input - check request format

  • 500+: Service temporarily unavailable

Pricing

The MCP Server uses your existing BatchData API subscription. Each tool call counts as a standard API request based on the underlying endpoint being accessed. Refer to your BatchData pricing plan for details.

Resources

Getting Your API Token

Update — April 2026: OAuth-based MCP connections are now available and follow a separate account-level dataset configuration rather than the Server Token setup described below. See OAuth Authentication for MCP Server for details.

If you don't already have a BatchData API token:

  1. Log in to your BatchData account

  2. Navigate to API Tokens/Server side Token - https://app.batchdata.com/api-tokens/server-side-token

  3. Add new token and grant it the permissions for the API end-points you want to expose to the MCP server. The applicable permissions are:

    1. Address

      1. address-geocode

      2. address-reverse-geocode

      3. address-verify

    2. Phone

      1. phone-verification

    3. Property

      1. property-lookup-all-attributes

        1. Enable all the datasets that you want to make available

      2. property-search

      3. property-skip-trace-v3

        1. Contact your Account Manager to enable access to the V3 Skiptrace API end-point.

  4. Use the key with the Authorization: Bearer header

What's New Since Launch

Two features that were planned at launch are now available:

Account-Based Authentication (Released January 2026)

OAuth sign-in for the MCP Server shipped in January 2026. You provide the server URL, sign in with your BatchData account, and no API token configuration is needed. Access tokens refresh automatically.

For setup steps and the list of supported clients, see OAuth Authentication for MCP Server.

Property Search Tools (Released January 2026)

Property search tools for the MCP Server shipped in January 2026. Your AI assistant can search properties by location, price range, and property characteristics, apply Quick List filters, and page through large result sets.

See Property Search MCP Tools Release Notes for the tool list and examples.

Frequently Asked Questions

How is this different from your regular API?

API: Built for developers to integrate into software applications

MCP Server: Built for AI assistants to use on behalf of people

Both access the same BatchData intelligence, just different interfaces.

The regular API requires developers to write code that calls our endpoints, handles authentication, processes responses, and integrates the data into applications. The MCP Server allows AI assistants to directly access the same data through natural language conversations, handling all the technical details automatically.

What AI assistants work with MCP?

The BatchData MCP Server works with any client that supports the Model Context Protocol.

For the current list of supported AI assistants, with setup steps for each, see OAuth Authentication for MCP Server. That article is the one place where we maintain the client list.

Custom MCP clients that do not support OAuth can still connect with an API token. See the MCP Server Developer Integration Guide.

Is the data the same as your regular API?

Yes, 100%. The MCP Server uses the exact same BatchData intelligence that powers all our products. Same data quality, same coverage, same reliability. You're accessing the same 140+ million property records with the same comprehensive information.

How does API token authentication work?

The BatchData MCP Server supports two authentication methods: OAuth sign-in (see OAuth Authentication for MCP Server) and API token authentication. With an API token:

  • Use your existing BatchData API token to authenticate

  • Provide your API token when configuring your AI assistant

  • The same token used for our regular API works with the MCP Server

  • No additional credentials needed - if you have BatchData API access, you can use MCP

What security considerations should customers know about API tokens?

API tokens should be treated as sensitive credentials:

Important Security Notes:

  • Protect your token: Anyone with access to your API token can use the MCP Server

  • Manage access carefully: The token bypasses individual user access controls, so control who has access to it

  • Monitor usage: The account owner is responsible for all costs associated with token usage

  • Don't share publicly: Never commit tokens to code repositories or share them in unsecured channels

  • Think of it like a master key - secure it accordingly

Is account-based authentication available?

Yes. OAuth sign-in has been available since January 2026. You provide the server URL and sign in with your BatchData account. No API token or local configuration is needed.

See OAuth Authentication for MCP Server for setup steps, the supported client list, and how to migrate an existing API token setup.

How do I configure the Claude Desktop application to work with the BatchData MCP server?

Using an AI assistant such as Claude Desktop, Claude Code, ChatGPT, or Cursor? Those clients connect to https://mcp.batchdata.com directly with OAuth sign-in and do not need mcp-remote or an API token. See OAuth Authentication for MCP Server. Use mcp-remote only for a stdio-only client or for custom tooling that authenticates with an API token.

The steps below are the API token path for Claude Desktop through mcp-remote. Use them only if you prefer an API token over OAuth sign-in. They need Node.js 22 and a BatchData server-side API token.

Step 1: Provision a BatchData API Token

  1. Log into https://app.batchdata.com/ and go to the Server Side Token provisioning page, https://app.batchdata.com/api-tokens/server-side-token

  2. Click on + ADD NEW TOKEN and enable the following permissions:

    1. Address

      1. address-geocode

      2. address-reverse-geocode

      3. address-verify

    2. Phone

      1. phone-verification

    3. Property

      1. property-lookup-all-attributes

        1. Enable all the datasets that you want to make available

      2. property-search

      3. property-skip-trace-v3

        1. Contact your Account Manager to enable access to the V3 Skiptrace API end-point.

Step 2: Install Node.js 22

Claude Desktop's bundled Node.js version is outdated. The BatchData MCP Server requires Node.js 22.

For macOS/Linux:

  1. Open Terminal

  2. Install Volta (Node.js version manager):

    curl https://get.volta.sh | bash

  3. Close and reopen Terminal

  4. Install Node.js 22:

    volta install node@22

  5. Find your username by running

    whoami

    (you'll need this for Step 3)

For Windows:

  1. Download and install Node.js 22.x LTS from nodejs.org

  2. Note the installation path (typically C:\Program Files\nodejs)

  3. Restart your computer after installation

Step 3: Configure Claude Desktop

  1. Open Claude Desktop → Settings → Developer → Edit Config

  2. Add the following configuration to the JSON file:

For macOS:

{
  "mcpServers": {
    "BatchData": {
      "command": "/Users/YOUR_USERNAME/.volta/bin/npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.batchdata.com",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer YOUR_SERVER_SIDE_API_TOKEN_HERE"
      }
    }
  }
}

For Linux:

{
   "mcpServers":{
      "BatchData":{
         "command":"/home/YOUR_USERNAME/.volta/bin/npx",
         "args":[
            "-y",
            "mcp-remote",
            "https://mcp.batchdata.com",
            "--header",
            "Authorization:${AUTH_HEADER}"
         ],
         "env": {
           "AUTH_HEADER": "Bearer YOUR_SERVER_SIDE_API_TOKEN_HERE"
         }
      }
   }
}

For Windows:

{
   "mcpServers":{
      "BatchData":{
         "command":"C:\\Program Files\\nodejs\\npx.cmd",
         "args":[
            "-y",
            "mcp-remote",
            "https://mcp.batchdata.com",
            "--header",
            "Authorization:${AUTH_HEADER}"
         ],
         "env": {
            "AUTH_HEADER": "Bearer YOUR_SERVER_SIDE_API_TOKEN_HERE"
         }
      }
   }
}

Important:

  • Replace YOUR_USERNAME with your actual username

  • Replace YOUR_SERVER_SIDE_API_TOKEN_HERE with your BatchData API token

  • Adjust paths if you installed Node.js in a different location

  1. Save the file and restart Claude Desktop

  2. You should see "BatchData" in the extensions list

  3. Enable the server and select "Always Allow" when prompted for permissions

Verification: After setup, Claude will automatically detect and use BatchData tools when you ask real estate-related questions or request property data lookups.

You can confirm the installation by providing this prompt to Claude "What tools does the BatchData MCP server support?"

Questions? Contact our support team at support@batchdata.com or visit https://help.batchdata.io for more information.

Related Articles
Did this answer your question?