January 29, 2026
We're excited to announce OAuth authentication for the BatchData MCP Server. This new authentication method makes connecting your AI assistant to BatchData simpler and more secure.
What's New
The BatchData MCP Server now supports OAuth authentication, eliminating the need for manual API token configuration. Simply provide the server URL and sign in with your BatchData account.
Key benefits:
No API token configuration — Just enter the server URL and authenticate
Browser-based login — Use your existing BatchData credentials or Google Sign-In
Automatic token management — Access tokens refresh automatically
Multi-device sync — Configure once, use everywhere (Desktop, Web, Mobile)
Supported Clients
OAuth authentication is available for:
Claude (Desktop, Web, and Mobile)
ChatGPT (Plus/Pro with Developer Mode)
Cursor
Claude Code
How to Set Up OAuth
Prerequisites
A BatchData account with valid credentials
An MCP-compatible client (Claude Desktop/Web/Mobile, ChatGPT, Cursor, Claude Code, or similar)
Claude (Desktop, Web, or Mobile)
Open Settings > Connectors (or Settings > MCP Servers)
Click Add Connector
Enter the server URL:
https://mcp.batchdata.comClick Add — your browser will open to the BatchData login page
Sign in with your email/password or Google Sign-In
After login, enable the connector via the + button in any chat
Mobile users: Add the connector on Desktop or Web first. It will automatically sync to your mobile app.
Anthropic Teams/Enterprise: If you use Claude through an Anthropic Teams or Enterprise workspace, your workspace admin must first add the BatchData connector to the list of available connectors before team members can configure it.
Claude Code
Run this command in your terminal:
claude mcp add BatchData --url https://mcp.batchdata.com
When prompted, authenticate through your browser.
ChatGPT (Developer Mode)
Prerequisites: ChatGPT Plus or Pro subscription. For Business/Enterprise, your admin must enable Developer Mode in Workspace Settings.
Enable Developer Mode: Settings > Apps & Connectors > Advanced settings > Developer mode
Go to Settings > Connectors and click Create
Enter:
Connector name:
BatchDataMCP Server URL:
https://mcp.batchdata.comClick Create and authenticate when prompted
Cursor
Open Cursor Settings
Navigate to the MCP configuration section
Click Add MCP Server
Enter the server URL:
https://mcp.batchdata.comAuthenticate through the browser popup
Migrating from API Token to OAuth
If you previously configured BatchData using an API token, you can switch to OAuth for a simpler experience.
Claude Desktop
Go to Settings > Developer > Edit Config
Remove the existing BatchData configuration block
Save and close the config file
Add the connector via the UI using the steps above
Claude Code
claude mcp remove BatchDataclaude mcp add BatchData --url https://mcp.batchdata.com
Why Migrate?
Aspect | API Token | OAuth |
Setup | Manual JSON editing | Simple UI flow |
Token management | Manual rotation | Automatic refresh |
Security | Token stored in config file | Tokens managed by client |
Multi-device | Configure each device | Syncs across devices |
API Token Still Supported
The API token authentication method remains available for:
Custom MCP clients that don't support OAuth
Debugging and automation scripts
Users who prefer explicit token management
See the MCP Server Developer Integration Guide for API token configuration instructions.
Usage and Billing
The MCP Server incurs usage charges for the BatchData APIs that it accesses. Usage is billed the same as if the API request was made directly against the BatchData API endpoint.
For example, when your AI assistant uses the lookup_property tool, it counts as a Property Lookup API request. The same applies to all other MCP tools — each tool call is metered and billed according to your BatchData subscription plan.
Billing Model for Property Search and Property Lookup: OAuth-authenticated MCP tools that access Property Search and Property Lookup endpoints follow the same token-based billing model as direct API access. Costs are determined by your authentication token's provisioned dataset access, not by the specific data requested at runtime.
Why Token-Based Billing?: This approach provides predictable cost estimation and transparent usage reporting. You can accurately forecast API expenses based on expected property record volumes and your token's dataset provisioning. Usage reports directly correlate charges to property records retrieved, making it simple to validate billing against actual usage and understand cost breakdowns.
OAuth Token Provisioning: When setting up OAuth for MCP server access, ensure your tokens are provisioned with only the datasets needed for your specific use case. Each property record retrieved through OAuth-authenticated MCP tools incurs the full per-record rate based on all datasets your token is provisioned to access.
Runtime Parameter Effects: The datasets and customProjection parameters in OAuth-authenticated MCP property search operations filter response data but do not reduce per-record billing costs.
OAuth-Specific Cost Control:
Configure OAuth applications with sandbox tokens during development
Implement proper scoping in OAuth flows to limit dataset access
Use the
takeparameter to control the number of property records returnedMonitor OAuth token usage through your account dashboard
For comprehensive billing information and dataset details, see Datasets and Custom Projections.
Questions?
Contact our support team at support@batchservice.com or visit https://help.batchdata.io for more information.