Der DataMerge MCP MCP-Server,
verbunden mit einem Klick.

“Nutze „configure_datamerge“: Configure DataMerge API authentication (required before using other tools if DATAMERGE_API_KEY is not set).”

“Nutze „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, glo.”

“Nutze „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 ·.”

“Nutze „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.”

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, glo

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 ·

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

run_company_enrichment — Agent-friendly company enrichment. On the first call provide enrichment params (domain, domains, company_name, country_code, etc.); the serv

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

run_contact_search — Agent-friendly contact search. On the first call provide domains and enrich_fields; the server starts the job and polls internally for up to

get_company — Get a single company record. GET /v1/company/get?datamerge_id={id} or ?record_id={uuid}. Provide either datamerge_id (charges 1 credit) or r