April 20, 2026

BatchData account admins now have a single place to control which property datasets are returned by OAuth-provisioned MCP tokens. The new MCP Dataset Configuration page lets you fine-tune data access and per-record billing for every OAuth MCP connection in your account.

What's New

OAuth MCP tokens (used by Claude, Cursor, ChatGPT Developer Mode, and Claude Code) now honor an account-level dataset configuration. From one screen, admins can choose the property data tier and pick exactly which dataset add-ons are included on every OAuth MCP connection issued under the account.

Key benefits:

One setting for the whole account — Configure once; every OAuth MCP token your users create inherits the config
Predictable billing — Per-record cost is determined by the datasets you provision, not by ad-hoc parameters sent at runtime
Admin-only control — Only account admins and owners with API token provisioning permission can edit the configuration
Applies automatically — Newly created and rotated OAuth MCP tokens pick up the latest configuration

Where to Find It

API Tokens → MCP Server Datasets

Or go directly to app.batchdata.com/api-tokens/mcp-oauth-config.

What You Can Configure

The MCP Dataset Configuration page controls the datasets returned by the Property Lookup, Property Search, and Comparable Property MCP tools.

Data Tier

Choose one:

Basic Property Data — Core property identifiers, address, and basic characteristics
Core Property Data (Tax Assessor) — Extended tax assessor data

Dataset Add-ons

Layer any of the following add-ons on top of the selected tier:

Contact Enrichment
Valuation
Mortgage Transaction + Open Liens
History (Deed) — Add-on to Mortgage Transaction
Demographics
Pre-Foreclosure
Listing Data
Property Owner Profile
Quick Lists
Permit Summary
BatchRank

Use the Select All button to toggle everything on or off at once.

Tools Affected

The configuration controls what's returned by these MCP tools:

lookup_property
search_properties_count, search_properties_preview, search_properties_page
comparable_property

Address, Phone, and Skip Trace MCP tools are always available on OAuth MCP tokens and do not require dataset configuration.

Defaults for New Accounts

If no account configuration has been saved, OAuth MCP connections default to:

Core Property Data (Tax Assessor) tier only
All dataset add-ons disabled

This provides a safe, predictable starting point. Admins can opt into additional datasets at any time.

How Changes Apply

New OAuth MCP tokens use the current configuration the moment they're issued
Rotated OAuth MCP tokens pick up the latest configuration on rotation
Existing active OAuth MCP tokens are updated when the configuration is saved — the success message shows how many tokens were updated

Server-side API tokens are not affected. The MCP Dataset Configuration applies only to OAuth-based MCP connections. Your existing server-side API tokens continue to use their own provisioned datasets.

Permissions

Admins and owners with API token provisioning permission see editable controls and the Save Configuration button
All other users see the page in read-only mode with a banner indicating they don't have permission to edit

Billing Impact

Per-record billing for OAuth MCP Property Lookup and Property Search calls is determined by the datasets you enable on this page — not by datasets or customProjection parameters sent at runtime.

To keep costs aligned with your use case:

Enable only the tiers and add-ons your team actually needs
Review the configuration before onboarding a new set of users to OAuth MCP
Check Usage Reports in the dashboard to confirm per-record costs match expectations

For a full breakdown of dataset pricing and the token-based billing model, see the OAuth Authentication for MCP Server release notes.