How to Connect Folk to Claude (and What It Can't Do)
folk is the CRM people pick because it feels like a well-organized contact book — groups instead of modules, custom fields per group, notes and reminders instead of heavyweight pipelines. Getting Claude to read that contact book is doable today, with two honest caveats up front: folk hasn’t released its own MCP server, and the community options are thinner (and churnier) than for bigger CRMs. One early folk server, NimbleBrain’s mcp-folk, has already been archived; the maintained paths as of mid-2026 are open-source projects like folk-crm-mcp and Composio’s hosted folk toolkit. All of them wrap folk’s developer API and authenticate with a folk API key (typically set as FOLK_API_KEY), and all of them join Claude as a custom connector — meaning a paid Claude plan.
What Claude can do inside your folk workspace
The available servers map closely onto folk’s core objects. Claude can list, fetch, create, and delete people and companies; browse your groups and each group’s custom fields; and add notes. Coverage varies by server, so check the tool list — but a typical session with a connected workspace looks like:
- “List everyone in my ‘Fundraise 2026’ group where the ‘intro path’ custom field is still empty.”
- “Create a company record for Meridian Labs, add it to the Agencies group, and note that Priya referred them.”
- “Add a note to Sam Okafor — met at SaaStock, wants a follow-up in September.”
For folk’s sweet spot — founders, agencies, investors running relationship-driven pipelines — this is a fast way to audit a group before an outreach push or to capture context without clicking through the app.
Setup itself is short: generate an API key in folk’s settings, point your chosen MCP server at it, and register the server in Claude’s connector settings. With a hosted option like Composio the key handling and server hosting are managed for you; with an open-source server you run it yourself and should skim the code first, since it will hold a key to your entire network.
The catch: folk runs on touchpoints, and Claude can’t feel them
folk’s whole discipline is keeping statuses and last-touch fields honest — you move a person from “Contacted” to “In conversation,” you log the touchpoint. Claude, connected, makes those edits faster to type. It does not make them happen. If an investor from your fundraise group finally replies after three weeks, their status stays stale until you open a chat and say so. If you promised yourself a September follow-up with Sam, no chat will start itself in September.
There’s no watching, no reminders acted on, no reaction to a reply — a Claude connector runs only inside a live conversation, then goes dormant. For a CRM whose value depends on nothing falling through the cracks, that’s precisely the gap that matters.
What to use when folk should update itself
Carly closes that gap from the other direction: she’s an AI executive assistant that acts on events instead of prompts. Running in the cloud around the clock, she notices the things folk users otherwise track by hand — a reply landing in your inbox, a meeting wrapping up, a follow-up date arriving — and executes the workflow: update the contact, log the note, draft and send the email through Gmail or Outlook (attachments included), put the next step on your calendar.
There’s nothing to host and no prompt engineering; you tell Carly what you want in plain English (“when someone from my investor list replies, update folk and schedule the call”) and she interviews you, then builds the workflow with you. AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited. Carly connects to 200+ tools — see integrations and the folk integration page.
Claude-with-folk vs Carly at a glance
| Claude (folk MCP) | Carly | |
|---|---|---|
| Browse groups & custom fields | Yes | Yes |
| Create people/companies, add notes | Yes, while chatting | Yes, on events |
| Updates a status when a contact replies | No | Yes |
| Acts on “follow up in September” | No | Yes |
| Server maintenance | Yours (or hosted third party) | None |
| Awake when you’re not | No | Yes (cloud) |
| Pricing | Paid Claude plan + API key setup | AI agents from $35/mo |
Frequently Asked Questions
Does Claude integrate with folk?
Yes, via community and hosted MCP servers that wrap folk’s API — there’s no official folk server or Claude directory app as of mid-2026. You add one as a custom connector with your folk API key; custom connectors require a paid Claude plan.
What can Claude actually change in folk?
Depending on the server: create and delete people and companies, manage group membership, read group custom fields, and add notes. Every change happens inside a chat you’re running — nothing is autonomous.
Are the folk MCP servers reliable?
Treat them as early. At least one has already been archived, and the remaining projects are maintained by individuals or integration platforms rather than folk itself. Hosted options (like Composio’s) remove the self-hosting burden but are still third-party.
Can Claude keep my folk statuses and touchpoints current automatically?
No — that’s the one thing the connector model can’t do. Claude has no visibility into replies, meetings, or dates passing. For self-updating statuses and scheduled follow-ups, use a trigger-driven agent like Carly.
Do I need to pay to connect Claude and folk?
Yes, at minimum a paid Claude plan (custom connectors aren’t on the free tier), plus folk API access and any hosting or platform costs for the MCP server you choose.
More: Claude connectors · Claude + Google Calendar · Can Claude send emails · Claude vs Carly · Best AI CRM tools · Claude + Nutshell · Claude + Salesflare · Claude + NetHunt CRM
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
