GTM-engineering walkthrough · Folk MCP · 2026

Folk + Claude via community MCP — the relationship-led CRM in your AI client

Folk doesn't ship first-party MCP yet, but NimbleBrain's community-maintained mcp-folk server at github.com/NimbleBrainInc/mcp-folk is the working integration today. It uses stdio transport with FOLK_API_KEY authentication, exposes Folk's core surface (contacts, companies, notes, reminders, interaction logging), and slots into Claude Desktop alongside any other MCP server you already run.

This page is the operator-grade walkthrough: the 5-10 minute setup, five concrete workflows that match Folk's relationship-led motion, the key-hygiene gotchas (long-lived API keys are not OAuth), and the realistic comparison to first-party hosted MCPs from Attio and HubSpot.

Transport
stdio
Local Node process via npx
Auth
FOLK_API_KEY
Long-lived key, store as env var
Setup time
5-10 min
One config edit + restart Claude
Maintainer
NimbleBrain
Community-built, official-adjacent

TL;DR

Want to try Folk?

Folk + MCP is the relationship-led CRM motion in an AI client

Tag-and-list CRM built for solopreneurs, agencies, and small sales teams. Free tier available; AI Assistants bundle in the paid tiers; community MCP from NimbleBrain ships today.

Start with Folk →Affiliate link — StackSwap earns a commission if you sign up for Folk. We only partner with tools we'd recommend anyway.

What Folk MCP exposes

Folk's CRM is intentionally narrow — tags, lists, contacts, companies, notes, reminders, interaction logs. There's no relational object schema (no custom objects like Attio), no native sequencing engine (Folk pairs with Smartlead/Instantly for cadence), no pipeline-stage workflow engine (Folk's pipeline view is lighter than HubSpot's). The MCP surface mirrors that narrow product: it exposes the operations that map to Folk's actual feature set, no more.

Five workflows that match Folk's motion

1. Weekly interaction-log summary

Prompt Claude with "pull all interactions from the past 7 days across my Investors list, group by company, and surface anyone I haven't touched in 30+ days." Claude routes the query through Folk MCP, aggregates the response, returns a structured Monday-morning digest. Replaces the manual "let me check each contact card" ritual that eats 30 minutes a week.

2. Bulk-tag cleanup from a LinkedIn scrape

Paste a list of new contacts captured via Folk's Chrome extension or a LinkedIn export into Claude. Ask Claude to assign matching Folk tags ("Founders 2026", "AI/ML", "EU") and add them to the right lists based on their LinkedIn descriptions. The LLM judgment replaces the manual tag-assignment step; the MCP write back to Folk is one operation per contact.

3. Follow-up reminder triage

"Show me all reminders due this week. For each, pull the contact's last 3 interactions and draft a short follow-up message grounded in that context." Claude fans out via the Folk reminders endpoint, pulls per-contact interaction history, drafts personalized outreach. You review, tweak, send. The drudgery part disappears.

4. Prep-for-meeting context

Drop a calendar event title or paste a meeting invite into Claude. Ask it to look up the contact in Folk, pull their interaction history + linked company + active reminders, and write a one-paragraph briefing. Replaces the "let me search Folk for this person" tab-switch right before every call.

5. Cross-list move based on engagement

"Move everyone in my Prospects list who's responded twice into the Active Discussion list, and tag them as 'engaged_q2'." Claude reads the Prospects list, filters by response count from interaction logs, executes the moves and tags. Twenty minutes of manual list-management becomes a single prompt.

Setup walkthrough

Folk MCP runs as a stdio Node process configured in your Claude Desktop config file. Path varies by OS: ~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%/Claude/claude_desktop_config.json on Windows.

  1. Install Node.js if you don't have it (18+ recommended).
  2. Generate a Folk API key. Folk Settings → Developer → API Keys. Create a key scoped to a dedicated AI user (not your admin account). Copy the key.
  3. Edit your Claude Desktop config. Add an entry under mcpServers that invokes the mcp-folk package via npx with FOLK_API_KEY set as an env var. The repo README at github.com/NimbleBrainInc/mcp-folk has the exact snippet.
  4. Restart Claude Desktop. The MCP tools from Folk appear in your next session.
  5. Verify connectivity. Ask Claude "list my recent Folk contacts" — if you see real data, you're wired.

The API-key hygiene gotcha

OAuth-based MCPs (Apollo, HubSpot, Attio) handle the secret-management burden for you. API-key MCPs like Folk put that burden on you. Three rules to follow:

When Folk MCP doesn't unlock value

If you don't run daily orchestration through Claude / Cursor / ChatGPT and your team uses Folk only through the UI + AI Assistants feature, the MCP layer doesn't add anything to your motion. Folk's native AI Assistants do a lot of the same in-product work (drafting follow-ups, suggesting tags, summarizing interactions) without the 5-10 minute setup. Evaluate Folk on its core fit (tag-and-list CRM, LinkedIn capture, fast onboarding); add the MCP only if your AI client is part of your daily workflow.

Want to try Folk?

Folk's relationship-led CRM + community MCP is the right shape for solo/agency motion in 2026

Tag-and-list model, LinkedIn capture extension, Folk AI Assistants in-product, and NimbleBrain's mcp-folk for Claude/Cursor power users. Pair with Smartlead or Instantly MCP for cadence.

Start with Folk →Affiliate link — StackSwap earns a commission if you sign up for Folk. We only partner with tools we'd recommend anyway.

FAQ

Folk MCP is community-built by NimbleBrain and runs as a stdio Node process — there's no one-click connector directory listing the way Apollo, HubSpot, and Attio have. The path: (1) install Node.js if you don't have it, (2) generate a Folk API key in Folk Settings → Developer → API Keys, (3) add an entry to your Claude Desktop config (claude_desktop_config.json) pointing at the mcp-folk npx command with FOLK_API_KEY as an env var, (4) restart Claude. Total time: 5-10 min if you're comfortable with JSON. The repo is at github.com/NimbleBrainInc/mcp-folk and the README has a working config snippet.

Two structural reasons. (1) Folk MCP is community-built, not first-party — the OAuth integration would require Folk to ship an OAuth app and host an MCP endpoint, which is a meaningful product investment. NimbleBrain built the MCP layer against the existing public Folk API, and that API authenticates with long-lived keys. (2) stdio MCP servers run locally on your machine, so the secret stays on your machine — it's not flowing through a third-party hosted endpoint. The tradeoff vs Attio MCP (OAuth, hosted) is real: less convenience, more responsibility for key hygiene.

Five patterns that match Folk's relationship-led CRM motion: (1) weekly interaction-log summary — 'pull all interactions from the past 7 days across my Investors list, group by company, surface anyone I haven't touched in 30+ days'; (2) bulk-tag cleanup — paste a list of new contacts from a LinkedIn scrape, ask Claude to assign matching Folk tags + add to the right lists; (3) follow-up reminder triage — 'show me all reminders due this week, prioritize by deal size or relationship score, draft outreach copy for each'; (4) prep-for-meeting context — drop a calendar event into chat, Claude pulls the contact's interaction history + linked company context from Folk; (5) cross-list move — 'move everyone in my Prospects list who's responded twice into the Active Discussion list'. Workflows we'd skip: anything bulk-write-heavy without confirmation, anything that depends on Folk objects the API doesn't expose (custom field schema gaps).

Yes — this is the standard multi-MCP pattern. Folk MCP runs as a stdio server; you can configure Claude Desktop with multiple MCP servers simultaneously (Folk + Smartlead + StackSwap MCP, for example). The LLM treats them as independent tool surfaces and routes natural-language requests to the right one. For a relationship-led solo or agency motion, Folk MCP + a sequencing MCP (Smartlead or Instantly) + StackSwap MCP for stack-level decisions is a tight, complete loop. Each MCP server is a separate entry in your claude_desktop_config.json — they don't conflict.

Different risk profile, not strictly safer or riskier. Pros: stdio means your Folk API key never leaves your machine — there's no hosted MCP endpoint to compromise. Cons: long-lived API key is a worse hygiene shape than OAuth (no automatic token refresh, harder to revoke surgically, easier to commit to a repo by accident). The community-built status also means there's no SLA — if NimbleBrain stops maintaining the repo, you maintain the fork. For solo/agency Folk users, the pros outweigh the cons; for enterprise compliance contexts with strict procurement, the community-MCP status is a structural blocker regardless of the protocol-level safety.

Zapier and Folk MCP solve different problems. Zapier wires deterministic event-driven automation — 'when a new contact gets created in Folk, send a Slack message and create a Calendly link'. Folk MCP lets the LLM read and write Folk objects in conversation — 'summarize this week's investor interactions, surface stalled conversations, draft re-engagement notes'. You'll likely run both if you're a serious Folk user: Zapier for the automation, Folk MCP for the in-conversation work.

Limited. Folk's product value is largely in the UI: fast onboarding, LinkedIn capture extension, AI Assistants for automation inside Folk itself, the tag-and-list mental model. If you don't run your daily orchestration through Claude or Cursor, adding the MCP layer is overhead for capability you won't use. The Folk product still earns its $20-50/user/mo on UI and motion fit; the MCP is incremental for the AI-forward subset of the user base.

Probably, given the direction the CRM category is moving (Attio, HubSpot, Apollo, Close, Zoho all ship first-party MCP in 2026). Folk has a public API and a product team that thinks about integrations as a strategic lever, so a first-party MCP would be on-brand. No public timeline as of mid-2026; the NimbleBrain community MCP is the right shape to use today and would either get absorbed or co-exist if a first-party shipped. Worth watching but not worth waiting for if you want LLM-native Folk workflows now.

Related reading

Canonical URL: https://stackswap.ai/folk-mcp-claude-integration. Disclosure: StackSwap is a Folk affiliate. The structural read above is the same operator analysis we'd give a GTM operator evaluating Folk cold against Attio and HubSpot.