{
  "listings": [
    {
      "slug": "relaticle",
      "name": "Relaticle",
      "company": "Relaticle, Inc.",
      "grade": "C",
      "fit": "yes",
      "why": "POST /v1/people/upsert and /v1/companies/upsert match on a unique attribute such as emails, get-crm-schema-tool lists custom field codes, and malformed values such as a phone without a country code return 422.",
      "source": "https://relaticle.com/developers/rest-api",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/relaticle"
    },
    {
      "slug": "affinity",
      "name": "Affinity",
      "company": "Project Affinity, Inc.",
      "grade": "B",
      "fit": "caveat",
      "why": "No upsert or matching-key create; create person is a beta endpoint and a retry can duplicate. Fields and dropdown values are discoverable through get_entity_fields. Rejection of bad emails isn't documented.",
      "source": "https://developer.affinity.co/api-reference/openapi.json",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/affinity"
    },
    {
      "slug": "attio",
      "name": "Attio API + MCP",
      "company": "Attio Limited",
      "grade": "B",
      "fit": "caveat",
      "why": "upsert-record and the assert endpoints match on email or domain, plain creates throw on unique conflicts, and list-attribute-definitions gives API slugs and options. Rejection of malformed emails wasn't documented in what we read.",
      "source": "https://docs.attio.com/mcp/overview.md",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/attio"
    },
    {
      "slug": "breakcold",
      "name": "Breakcold",
      "company": "Logike SAS",
      "grade": "C",
      "fit": "caveat",
      "why": "Required fields are enforced and the Idempotency-Key makes a retried create return the original, but there is no match-by-email upsert, so an existing person with the same email can still be duplicated. crm_fields_list exposes custom fields.",
      "source": "https://docs.breakcold.com/api/mcp-tools.md",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/breakcold"
    },
    {
      "slug": "capsule-crm",
      "name": "Capsule CRM",
      "company": "Zestia Limited",
      "grade": "C",
      "fit": "caveat",
      "why": "No upsert or idempotency key. Over MCP, update_contact changes only custom fields and tags, so a job title edit needs REST. Invalid values reject the whole update, and list_custom_fields gives definitions.",
      "source": "https://capsulecrm.com/support/integrations/capsule-mcp-integration-tool-reference/",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/capsule-crm"
    },
    {
      "slug": "close",
      "name": "Close API + MCP",
      "company": "Elastic Inc",
      "grade": "C",
      "fit": "caveat",
      "why": "No upsert or idempotency key, so find_contacts (exact email, normalised phone) must come first. Custom field ids, types and choices are listed by find_contact_custom_fields and describe_fields.",
      "source": "https://developer.close.com/mcp/tools.md",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/close"
    },
    {
      "slug": "copper",
      "name": "Copper API",
      "company": "Copper CRM, Inc.",
      "grade": "D",
      "fit": "caveat",
      "why": "PUT /leads/upsert matches on criteria or a custom field and returns 422 on several matches, and people can be fetched by email, but there is no upsert for people or companies, so those need find-first.",
      "source": "https://developer.copper.com/leads/upsert-a-lead.html",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/copper"
    },
    {
      "slug": "dynamics-365-sales",
      "name": "Microsoft Dynamics 365 Sales",
      "company": "Microsoft Corporation",
      "grade": "B",
      "fit": "caveat",
      "why": "PATCH on an alternate key creates or updates in one call, If-Match: * prevents a create, and describe plus $metadata give logical column names and keys. Keys must be configured per table first, and value validation wasn't in the pages read.",
      "source": "https://learn.microsoft.com/en-us/power-apps/developer/data-platform/webapi/update-delete-entities-using-web-api",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/dynamics-365-sales"
    },
    {
      "slug": "folk",
      "name": "folk API + MCP",
      "company": "Folk Inc.",
      "grade": "C",
      "fit": "caveat",
      "why": "folk_create_people takes up to 100 records with no match-by-email upsert, so find-first is needed; custom field keys and allowed values come from folk_get_workspace_structure. Each record succeeds or fails on its own.",
      "source": "https://developer.folk.app/mcp/tools.md",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/folk"
    },
    {
      "slug": "freshsales",
      "name": "Freshsales API",
      "company": "Freshworks Inc.",
      "grade": "E",
      "fit": "caveat",
      "why": "/api/contacts/upsert and bulk_upsert match on email or another unique field and error with ids to merge on duplicates; /api/settings/contacts/fields gives field names. Rejection of malformed emails isn't documented.",
      "source": "https://developers.freshworks.com/crm/api/",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/freshsales"
    },
    {
      "slug": "hubspot-mcp",
      "name": "HubSpot API + MCP",
      "company": "HubSpot, Inc.",
      "grade": "BB",
      "fit": "caveat",
      "why": "REST batch upsert matches on an idProperty and the MCP's search_properties and get_properties give internal names and enum values, but MCP writes have no upsert or idempotency key, and a17 saw a just-created contact's properties missing on first read.",
      "source": "https://developers.hubspot.com/docs/_llms/apis/2026-09/crm.txt",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/hubspot-mcp"
    },
    {
      "slug": "nutshell",
      "name": "Nutshell",
      "company": "Nutshell, Inc.",
      "grade": "D",
      "fit": "caveat",
      "why": "People and companies can be created or updated and per-entity field lists give valid keys, but no upsert or idempotency key exists, so a retry can duplicate unless the agent searches first.",
      "source": "https://developers.nutshell.com/llms.txt",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/nutshell"
    },
    {
      "slug": "pipedrive",
      "name": "Pipedrive API + MCP",
      "company": "Pipedrive Inc.",
      "grade": "B",
      "fit": "caveat",
      "why": "addPerson and updatePerson exist with custom fields listed by getAccountContext, but there's no upsert or idempotency key, so a retried create duplicates unless searchPersons runs first.",
      "source": "https://support.pipedrive.com/en/article/mcp-tools",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/pipedrive"
    },
    {
      "slug": "salesflare",
      "name": "Salesflare",
      "company": "Salesflare BVBA",
      "grade": "E",
      "fit": "caveat",
      "why": "Creating a contact with force=false skips an existing email, and update_if_exists on accounts updates instead of duplicating, but bad-value rejection isn't documented and most responses are typed only as a default string.",
      "source": "https://api.salesflare.com/openapi.json",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/salesflare"
    },
    {
      "slug": "streak",
      "name": "Streak API + MCP",
      "company": "Rewardly, Inc.",
      "grade": "E",
      "fit": "caveat",
      "why": "Contacts can be created and contact field definitions listed, but no upsert or idempotency key is documented, so a retry can duplicate.",
      "source": "https://streak.readme.io/llms.txt",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/streak"
    },
    {
      "slug": "sugarcrm",
      "name": "SugarAI (SugarCRM)",
      "company": "SugarAI Software Inc.",
      "grade": "D",
      "fit": "caveat",
      "why": "PATCH /integrate/:module/:sync_key_field_name/:value inserts or updates by sync key and /duplicateCheck flags duplicates, but contacts need a sync key set first, and value validation wasn't in the pages read.",
      "source": "https://support.sugarai.com/documentation/sugar_developer/sugar_developer_guide_26.1/integration/web_services/rest_api/endpoints/",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/sugarcrm"
    },
    {
      "slug": "twenty",
      "name": "Twenty API + MCP",
      "company": "Twenty.com PBC",
      "grade": "C",
      "fit": "caveat",
      "why": "upsert_records (and GraphQL batch upsert) creates or updates in one call, get_field_metadata lists fields, and unknown fields return 400, but which key the upsert matches on and value validation aren't stated.",
      "source": "https://raw.githubusercontent.com/twentyhq/twenty/main/packages/twenty-docs/user-guide/ai/capabilities/mcp.mdx",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/twenty"
    },
    {
      "slug": "zoho-crm",
      "name": "Zoho CRM",
      "company": "Zoho Corporation Private Limited",
      "grade": "BB",
      "fit": "caveat",
      "why": "/{module}/upsert matches on duplicate-check fields such as Email and fields metadata gives API names, but a13 failed writing a custom field by its label, and value rejection wasn't in the pages read.",
      "source": "https://www.zoho.com/crm/developer/docs/api/v8/upsert-records.html",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/zoho-crm"
    },
    {
      "slug": "salesforce",
      "name": "Salesforce API + MCP",
      "company": "Salesforce, Inc.",
      "grade": "F",
      "fit": "unchecked",
      "why": "Upsert and describe documentation sit on the developer site that refused our reader; a23 shows standard lead and contact operations missing the person account model.",
      "source": "https://community.n8n.io/t/212674",
      "confidence": "low",
      "url": "https://www.anchorterminal.com/tools/salesforce"
    },
    {
      "slug": "payani-ai",
      "name": "Payani AI",
      "company": "Payani Media LLC",
      "grade": "F",
      "fit": "no",
      "why": "Contacts and companies are readable only; the server cannot create or edit records.",
      "source": "https://payani.ai/mcp",
      "confidence": "low",
      "url": "https://www.anchorterminal.com/tools/payani-ai"
    }
  ],
  "marks": "yes: the docs show it does the job as the success test says. caveat: it does the job with a limit an agent should know. no: it doesn't do this job. unchecked: we couldn't read it.",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "useCase": {
    "accounts": 8,
    "after": [
      "crm.move-deal",
      "crm.log-activity"
    ],
    "area": "business",
    "asks": [
      "add this person to the CRM",
      "create a lead from this form",
      "import these contacts",
      "update their job title and score"
    ],
    "before": [
      "lead-data.enrich-known-contact",
      "web-scrapers.lead-list-building",
      "voice-agents.inbound-receptionist"
    ],
    "blockers": [
      "custom field must be named by API name the agent cannot discover (a13)",
      "object model differs by edition, such as person accounts (a23)",
      "no upsert or idempotency key on the listing (Affinity, Close, HubSpot per context notes)"
    ],
    "capabilities": [
      "crm.records",
      "crm.search"
    ],
    "category": "crm",
    "categoryName": "CRM \u0026 customer platforms",
    "checked": "2026-11-15",
    "companies": {
      "fit": 1,
      "fitWithLimit": 17,
      "tagged": 27
    },
    "competition": "one",
    "fits": [
      "relaticle"
    ],
    "fitsWithLimit": [
      "affinity",
      "attio",
      "breakcold",
      "capsule-crm",
      "close",
      "copper",
      "dynamics-365-sales",
      "folk",
      "freshsales",
      "hubspot-mcp",
      "nutshell",
      "pipedrive",
      "salesflare",
      "streak",
      "sugarcrm",
      "twenty",
      "zoho-crm"
    ],
    "id": "crm.upsert-contact",
    "listings": {
      "caveat": 17,
      "no": 1,
      "notRead": 0,
      "tagged": 27,
      "unchecked": 1,
      "yes": 1
    },
    "name": "Create or update a contact, company or lead without duplicates",
    "status": "draft",
    "success": "Precisely one record per key after the call and after a retry; supplied standard and custom fields are written and read back; invalid values (bad email) are rejected rather than stored.",
    "url": "https://www.anchorterminal.com/api/v1/use-cases/crm.upsert-contact.json",
    "weight": 15,
    "weightBasis": "8 of 48 accounts (a03, a07, a10, a11, a13, a21, a23, a46), raised two points as above; lead-data's map already sends six use cases to crm.upsert-contact"
  }
}
