folk MCP connector
The folk connector brings folk people, companies, notes and groups to Claude, ChatGPT, Cursor and the Elaichi Agent through one OAuth endpoint, so your team can search and update the CRM in plain language inside their own access.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect folk to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect folk once
-
Open Connections, choose Add connection, and pick folk.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in folk. folk's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
folk MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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 ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
folk MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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.
Connect folk to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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.
Use cases
What teams do with folk through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
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?”
Compare
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.
| 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 | $15 per user per month. | 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.
AI tools
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.
No tools match your search.
See it in Elaichi
What connecting folk gets you
6 screens from the product, each doing one job for your folk account.
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.
- people
- companies
- notes
- groups
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 or Cursor
MCP clients
Every MCP client reaches folk through one endpoint.
Claude, ChatGPT and Cursor use one governed endpoint, no SDK and no shared API key.
Copy the endpoint
Tool catalog
37 folk tools, ready without writing code.
People, companies, notes, groups and custom objects, with searching, creating and updating covered.
- Folk get current user
- Folk get workspace structure
- Folk search companies
- Folk get company
Toolboxes
Each team gets its own folk toolbox.
Sales, partnerships and recruiting each see the folk tools their work needs, nothing more.
- Sales
- Partnerships
- Founders
- Recruiting
Shared connections
Share a folk connection, never a credential.
One person connects folk, teammates work through it, and nobody else handles a login.
- Sales EMEA
- Sales US
- Partnerships
- Fundraising
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.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule starts folk work, a person approves.
New folk people are fetched, grouped and drafted into a digest, approved, then posted back.
folk digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch people
folk
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
folk
Queued
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.
folk health
Refreshed 4 minutes ago · every 15 minutes · from the people collection
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%
Related connectors
More from the catalog
FAQ
Frequently asked questions
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, 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 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 blocking creating or updating records, notes or group members. A restricted action is never advertised to Claude, ChatGPT or Cursor, so no prompt can reach it.
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 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, 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 on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.