Skip to content

CRM

folk MCP connector

The folk connector brings folk people, companies, notes and groups to Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent through one OAuth endpoint, so your team can search and update the CRM in plain language inside their own access.

  • Connects over OAuth
  • Free 14-day trial
  • No credit card
ChatGPT Elaichi connected

Find every person at Acme in folk and show their latest notes

Working in folk with Elaichi

  • Folk get current user
  • Folk get workspace structure
  • Folk search companies
Ask anything…
Governance / Audit log Last 24 hours
folk Folk search companies Emily Carter · ChatGPT · 9:41 AM Done
folk Folk get workspace structure Emily Carter · ChatGPT · 9:41 AM Done
folk Folk get current user Emily Carter · ChatGPT · 9:41 AM Done
folk Folk get company Megan Brooks · Claude · 9:38 AM Done
folk Folk create company Ryan Hayes · Cursor · 9:35 AM Done

How to connect folk to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

folk MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

folk MCP connector for Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

    https://api.elaichi.ai/mcp
  2. 2

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

folk MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

folk MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

folk MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

    https://api.elaichi.ai/mcp
  3. 3

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

Connect folk to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

What teams do with folk through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in folk is logged.

  • Sales

    Catch a person up after a call

    Ask for the person in folk, add a note on what was discussed, and update the fields that changed, all from the chat you already have open.

  • Partnerships

    Find every company in a group

    Pull the companies in your Partners group in folk and see which ones have no recent note, so follow-ups go to the right people.

  • Founders

    Keep investor notes in one place

    After a pitch, add the investor as a person in folk, attach them to the right company, and drop in a note before the details fade.

  • Recruiting

    Track candidates as people in folk

    Create a person for each candidate, add them to the hiring group for the role, and update their stage as interviews happen.

  • Customer success

    Update the company record before a renewal

    Open the company in folk, read the latest notes, and bring the record current before the renewal conversation.

  • Marketing

    Build a group for the next event

    Create a group in folk for the event, add the people who registered, and adjust member roles as the guest list changes.

Try asking

  • “Find every person at Acme in folk and show their latest notes”
  • “Add a note to Maria Chen about today's pricing call”
  • “Which companies in the Investors group have no note this quarter?”

See all 37 folk tools →

What connecting folk gets you

6 screens from Elaichi, each doing one job for your folk account.

Elaichi Agent

Ask Elaichi to work across your apps.

Find every person at Acme in folk and show their latest notes

Add a note to Maria Chen about today's pricing call

Which companies in the Investors group have no note this quarter?

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask folk a question, get a live answer.

Three starter prompts search people, companies and notes in folk as they stand right now.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

Every MCP client reaches folk through one endpoint.

Claude, ChatGPT, Cursor and Microsoft Copilot use one governed endpoint, no SDK and no shared API key.

ElaichiTools
Tool Action Description
Folk get current user Get Returns the identity of the authenticated folk user for this MCP session: their id, email, and fullName. Call once per session when you need to attribute an action to the current user (e.g. assigning a task, filtering by owner). Do not call to look up other workspace members —…
Folk get workspace structure Get Retrieves the complete structure of the folk workspace: groups, entity types per group, native fields (person/company/object), custom field definitions (names, types, allowed values), pipeline views, and workspace members. Call at the start of every fresh session before…
Folk search companies Search Search companies in the folk workspace using one or more filters.
Folk get company Get Fetch a single company by companyId. Use when you already have a companyId from a previous search_companies call or from another tool response. Do not use to find or look up a company by name, domain, or other attribute — use search_companies instead. Returns the full company…
Folk create company Create Create a new company in the folk workspace. Provide at least a name to identify the company. Multi-value fields (emails, phones, addresses, urls) accept plain arrays — the first element becomes the primary value. Use groups (array of { id }) to add the company to one or more…

Tool catalog

37 folk tools, ready without writing code.

People, companies, notes, groups and custom objects, with searching, creating and updating covered.

ElaichiToolboxes
Name Source template Tools Created

Sales toolbox

folk · people and companies

folk starter 18 Mar 4, 2026

Partnerships toolbox

folk · partner companies and notes

— 9 Mar 2, 2026

Founders toolbox

folk · investors and fundraising notes

— 24 Feb 27, 2026

Recruiting toolbox

folk · candidates and hiring groups

folk starter 6 Feb 19, 2026

Customer success toolbox

folk · accounts and renewal notes

— 31 Jan 30, 2026

Marketing toolbox

folk · event groups and contacts

— 12 Jan 22, 2026

Toolboxes

Each team gets its own folk toolbox.

Sales, partnerships and recruiting each see the folk tools their work needs, nothing more.

ElaichiConnections
Connection Scope Status Access
FO

folk (Sales EMEA)

Connected by Emily Carter

Personal • Active 1 team · 6 members
FO

folk (Sales US)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
FO

folk (Partnerships)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
FO

folk (Fundraising)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
FO

folk (Recruiting)

Connected by Ryan Hayes

Personal • Active Not shared
FO

folk (Community)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Share a folk connection, never a credential.

One person connects folk, teammates work through it, and nobody else handles a login.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

folk Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

folk People Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

folk People List Toolbox

Audit log

Every folk call is logged with a name.

When, who, what happened, type and resource, for every person and company touched in folk.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.

folk digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch people

    folk

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    folk

    Queued

Workflows

A schedule starts folk work, a person approves.

New folk people are fetched, grouped and drafted into a digest, approved, then posted back.

folk health

Refreshed 4 minutes ago · every 15 minutes · from the people collection

Live

People

1,284 ↓ 12%

Companies

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

People created

Last 14 days

By team

Share of activity

Sales EMEA 34%

Sales US 27%

Partnerships 21%

Fundraising 18%

Collections and dashboards

Your folk numbers arrive before anyone asks.

Four metrics, 14 days of people created, a team breakdown, computed with no model involved.

Why connect folk's MCP server through Elaichi

folk builds and runs this MCP server. Elaichi sits in front of it, so folk's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to folk's server directly, outside Elaichi, get none of this.

  • One address for every AI client

    Claude, ChatGPT, Cursor and Microsoft Copilot reach folk's tools at the same Elaichi address as every other connected app. Nobody adds folk's server to each client one by one.

  • Each person signs in as themselves

    Each person signs in to Elaichi as themselves. Members connect with their own folk sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.

  • Rules checked before a call leaves

    Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches folk's server. By default, a tool folk does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.

  • One audit log for every app

    Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.

  • Tool issues go to folk

    folk builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the folk team.

    help.folk.app/en

Why run a vendor's MCP server through Elaichi →

For IT and engineering

Elaichi vs Zapier MCP vs Composio for folk

All three can connect folk to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for folk, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over folk tools Allow or restrict single folk tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per folk call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price Free for one person; $15 per user per month on Gold. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

folk tools for your AI agents

37 tools are ready to call through Elaichi's MCP endpoint the moment you connect folk, governed by the same roles, restrictions, and audit log as everything else in Elaichi. folk builds and runs these tools.

Questions, answered

How do I connect folk to Claude?

Connect folk in Elaichi first: pick folk from the catalog, click connect, and sign in to folk over OAuth in the window that opens. There is no OAuth application to register and no client ID or secret to generate. Then in Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you into Elaichi and folk is ready in your next chat.

Does folk work with ChatGPT and Cursor as well as Claude?

Yes. Once folk is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect folk once and every client you sign into picks it up.

What can an AI agent actually do with my folk data?

It can search the people and companies in your folk workspace, open a record, add or update a note, create a new person or company, and update fields after a call. It can also list your folk groups, create one, and add or remove members. Short, concrete asks like 'find everyone at Acme and summarize their notes' work better than long paragraphs.

Does connecting folk give the AI my whole workspace?

No. The AI works inside the folk access of the person who signed in, so it sees only the people, companies, groups and notes that person can already see in folk. Elaichi can narrow that further with roles and restrictions, and it can never widen it beyond what folk itself allows.

Can my team share one folk connection?

Yes. One person connects folk in Elaichi and shares the connection with a team, and nobody else ever handles a folk credential. Each teammate still signs in to Elaichi as themselves, so every search, note and update in folk is logged under their own name.

Can I stop an agent from changing things in folk?

Yes. Restrictions in Elaichi work per action, so you can allow searching people and companies in folk while restricting creating or updating records, notes or group members. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.

What happens to a folk connection when someone leaves?

Offboarding that person in Elaichi ends their access to folk through every client at once. A folk connection they shared keeps working for everyone else on the team. If you want folk gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.

Does the folk MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. folk is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for folk?

Yes. Both let Claude, ChatGPT or Cursor use folk. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every folk call.

How is Elaichi different from Composio for folk?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to folk: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put folk in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot