DataMerge MCP

What it can reach

From its install config and its own description; a sandbox run will confirm this later.

Checks on v1.0.0

1. Real tool

   passrules 2026-09-29.1 · 6 hours ago

2. Static scan

   failrules 2026-09-29.1 · 6 hours ago
   • highTells the model how to use other tools.tool:configure_datamerge.description

Install

Each app still asks you to confirm. Everything is pinned to the version checked above.

{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://mcp.datamerge.ai"
    }
  }
}

Tools it offers

As the server describes them. This text comes from the publisher and is shown as-is.

• configure_datamerge

  Configure DataMerge API authentication (required before using other tools if DATAMERGE_API_KEY is not set).

• start_company_enrichment

  POST /v1/company/enrich. Enrich one or more companies by domain. Returns a job_id (async). Single: domain. Batch: domains, country_code, global_ultimate, list, skip_if_exists.

• get_company_enrichment_result

  GET /v1/company/enrich/{job_id}/status. Poll until status is "completed" or "failed". Response includes record_ids. Status values: queued · processing · completed · failed.

• start_company_enrichment_and_wait

  POST /v1/company/enrich then poll GET /v1/company/enrich/{job_id}/status until status is "completed" or "failed" or timeout. Same params as start_company_enrichment plus poll_interval_seconds and timeout_seconds.

• run_company_enrichment

  Agent-friendly company enrichment. On the first call provide enrichment params (domain, domains, company_name, country_code, etc.); the server starts the job and polls internally for up to ~25s. If the job is still running, the response will be {status:"pending", continuation_token, attempt, elapsed_seconds}. When you see status "pending" you MUST immediately call run_company_enrichment again with only continuation_token set — do not ask the user, do not call any other tool first. Typical jobs finish within 5 attempts (~125s). On completion the response contains record_ids and full company records.

• run_contact_enrich

  Agent-friendly contact enrichment. On the first call provide contacts and enrich_fields; the server starts the job and polls internally for up to ~25s. If still running, returns {status:"pending", continuation_token, attempt, elapsed_seconds} — you MUST immediately call run_contact_enrich again with only continuation_token set. Do not ask the user. Typical jobs finish within 5 attempts. On completion the response contains record_ids and full contact records.