MoltSets has its own MCP server. Many popular CRMs now have MCP servers too. That means you can connect both to Claude at once and use Claude as the bridge between them: MoltSets finds and enriches contact data, Claude does the translation, and your CRM receives clean, structured records without you touching an API or writing a script.

This article covers how the pattern works, what to expect from each major CRM's MCP support, and a few example workflows to get you started.

Once both MCP servers are connected in Claude:

No middleware, no CSV exports, no Zapier step in between. The trade-off is that Claude is doing the mapping live, in the conversation, so it's worth reviewing what it's about to write before you ask it to commit anything.

You'll need:

Both connectors need to be active in the same conversation (or the same Claude Code / Claude Desktop session) for Claude to act as the bridge. If you only have one connected, ask Claude to check its tool list before assuming the other is missing.

Support varies a lot by CRM right now. Some are official and full read/write, some are official but read-only, and some are community-maintained. Worth knowing before you build a workflow around one.

Official MCP server covers contacts, companies, and deals. Read-only at the moment — you can pull HubSpot data into a MoltSets-powered enrichment pass, but writing enriched records back requires a manual step (or a community server, which has lower adoption and isn't something we'd recommend relying on for production data). Good fit for: enrichment research and reporting, not yet for automated write-back.

Official server (salesforcecli/mcp), the most comprehensive of any CRM — 60+ tools, full read/write, SOQL/SOSL queries, record CRUD. Currently in beta and leans developer-focused rather than sales-rep-friendly, but it's the strongest option if you want Claude to both pull from and push to Salesforce using MoltSets data in the same session.

Official hosted MCP server with full CRUD across people, companies, deals, lists, tasks, and notes, plus Attio's relationship graph. This is the smoothest end-to-end experience of the group — enrich with MoltSets, write straight back into Attio's flexible object model without translation headaches. If your team is on Attio, start here.

Community-maintained only. The most popular option is read-only (deals and activities). There's a full-CRUD community alternative, but it has limited adoption — treat it as unverified for anything you depend on. Fine for pulling deal data to inform a MoltSets enrichment run; be cautious about write-back.

Official hosted server with 57 tools. Solid full read/write coverage if your team runs on Close.

Official server, well-adopted. Useful if you're running your pipeline as a Monday board rather than a traditional CRM — same bridge pattern applies.

Both have official MCP support but noticeably thinner toolsets than the above (Dynamics currently around 5 tools; Zoho covers the core CRM module only). Workable for simple lookups, not yet a full bridge experience.

"Here's a list of 50 companies from our trade show. Find the VP of Marketing at each using MoltSets, then create them as contacts in [CRM] with their title and company."

"Pull all HubSpot contacts missing a phone number, then use MoltSets to find and fill them in." (Note: with HubSpot's current read-only access, Claude can find the gaps and enrich the data, but you'll need to import the results back manually.)

"Check which of these 200 leads already exist in [CRM] before you run them through MoltSets, so we're not paying to enrich contacts we already have."

This landscape is moving fast — several CRMs added official MCP support only in the last few months, and write access is actively expanding. We'll keep this article updated as that changes.