Skip to main content
Mapsdata exposes an MCP server over Streamable HTTP. It uses the same account, credits, searches, enrichment pipeline, and results as the dashboard and REST API.
MCP server URL

Authentication

Add the server URL, sign in to Mapsdata in your browser, review the requested access, and click Allow access. The client receives a revocable OAuth token. Mapsdata supports OAuth 2.1 authorization-code flow with PKCE, dynamic client registration, refresh-token rotation, protected-resource metadata, and token revocation.

Connect a client

1

Open the custom MCP setup

In ChatGPT, click the Plugins icon on the left-hand side (the @-shaped icon with a plug inside), then click Browse directory. Click Add to open the dropdown, then choose Add custom MCP server.
2

Enter the server details

Enter the fields below, keep Connection set to Server URL, and select OAuth for authentication.Name
Server URL
Authentication
3

Sign in and allow access

Create the connector, choose Sign in, then sign in to Mapsdata and click Allow access. Mapsdata will appear on the left-hand side. Start a chat and type @Mapsdata to use it.

Tools

Account and discovery

Supplied-business enrichment

All tools return structured output. Read-only tools are marked read-only in their MCP annotations. search_businesses and enrich_businesses are marked destructive because they reserve credits, even though their idempotency keys make safe retries possible. To retrieve an existing search, call list_searches. It returns the newest search first and includes searches created in the Mapsdata website by default. Pass scope: "dashboard" or scope: "integration" to narrow the list. Use search_status for job details, get_search_results for its businesses, and get_business when you need one complete record by ID.
1

Check the account

Call check_account. Do not request more than both credits_remaining and max_results_per_search.
2

Resolve the location

Call find_locations and select one returned location. Copy its label and country_code into search_businesses.
3

Confirm the cost

Tell the user the maximum number of credits the search can reserve. Call search_businesses only after approval, setting confirmed_credit_cost to exactly the same number as max_results.
4

Poll and paginate

Poll search_status every 5–10 seconds. Read live pages with get_search_results; after the job reaches completed, fetch every page again until has_more is false.
For supplied websites, use the same pattern: check_account, state the exact number of businesses and credits, obtain approval, then call enrich_businesses with the matching confirmed_credit_cost.

Credit and retry safety

  • Both credit-spending tools reject a call when confirmed_credit_cost does not match the maximum charge.
  • Use a stable, unique idempotency_key for each logical creation request. If a network call times out, retry the same body and key.
  • Never retry an uncertain creation with a new key; that can create and charge a second job.
  • Reading catalogs, account state, job status, lists, and results consumes no credits.
  • Result pages are capped at 100 leads in MCP to keep agent context bounded. Continue while has_more is true.