# 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. Source: https://elaichi.ai/connectors/folk/ ## Facts | | | | --- | --- | | Application | folk | | Category | CRM | | AI tools | 37 | | Authentication | Connects over OAuth | | Bring your own OAuth app | No | | Native MCP | Yes. folk builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top | | Support for its tools | help.folk.app/en | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead | ## What you can ask once folk is connected - 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? ## Connect folk in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick folk. 2. Optionally set Share with, then press Connect. 3. Approve it in folk. folk's own window opens. Whoever approves it decides what this connection can reach. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which folk tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## folk MCP connector for Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect folk to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a folk tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with folk through Elaichi ### Catch a person up after a call Sales. 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. ### Find every company in a group Partnerships. 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. ### Keep investor notes in one place Founders. 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. ### Track candidates as people in folk Recruiting. Create a person for each candidate, add them to the hiring group for the role, and update their stage as interviews happen. ### Update the company record before a renewal Customer success. Open the company in folk, read the latest notes, and bring the record current before the renewal conversation. ### Build a group for the next event Marketing. Create a group in folk for the event, add the people who registered, and adjust member roles as the guest list changes. ## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026. Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/). ## 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 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 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. ## All 37 folk tools Every tool below is callable through https://api.elaichi.ai/mcp once folk is connected, subject to the toolbox it is in and the restrictions on the caller. - **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… - **Folk update company** (Update). Update an existing company by id. Partial update — omit any field you don't want to change. Scalar fields (name, description, industry, foundationYear, fundingRaised, lastFundingDate, employeeRange): provide the new value directly. Multi-value fields (emails, phones,… - **Folk search people** (Search). Search people in the folk workspace using one or more filters. - **Folk get person** (Get). Fetch a single person by their folk person id and return the full person payload (names, emails, phones, addresses, urls, companies, groups, custom field values, interaction metadata). Use this only when you already have the person id (e.g. from folk_search_people or a… - **Folk create person** (Create). Create a new person in the folk workspace and return the full created person. Provide at least a name (fullName, or firstName/lastName) OR at least one email. For every multi-value field (emails, phones, addresses, urls), the first element is treated as the primary value.… - **Folk update person** (Update). Update an existing person in the folk workspace. Only the fields you provide are changed — omitted fields are left untouched. For multi-value fields (emails, phones, addresses, urls, companyIds) use addX / removeX for incremental changes or setX to replace the full list.… - **Folk search objects** (Search). Search objects (e.g. deals) in the folk workspace using one or more filters. - **Folk get object** (Get). Fetch a single object (e.g. deal) by its ID within a specific group and object type. Use when you already have an objectId from a previous folk_search_objects or folk_create_object call. Returns the full object: name, people, companies, createdAt, createdBy, customFieldValues. - **Folk create object** (Create). Create a new object (e.g. deal) within a specific group and object type in the folk workspace. Use folk_get_workspace_structure first to discover available groupIds and object types. Provide name, and optionally link people and companies by their folk IDs. customFieldValues is… - **Folk update object** (Update). Update an existing object (e.g. deal) in the folk workspace. Partial update — omit any field you don't want to change. name: provide new value to rename. people / companies: providing a list REPLACES all current associations. Omit to leave unchanged. customFieldValues: flat… - **Folk search notes** (Search). Search notes in the folk workspace. - **Folk create note** (Create). Create a new note linked to a person or company in the folk workspace. - **Folk update note** (Update). Update the content or visibility of an existing note. Partial update — omit any field you do not want to change. noteId: the note to update (format: `nte_<uuid>`). Obtain from folk_search_notes. content: new markdown body (optional). visibility: "public" or "private" (optional). - **Folk list groups** (List). List the groups in the folk workspace that the caller can access. - **Folk create group** (Create). Create a new group in the folk workspace. name: required — the name of the group. visibility: "public" (visible to all workspace members) or "private" (visible only to explicitly added group members). - **Folk update group** (Update). Update the name and/or visibility of an existing group. Partial update — omit any field you do not want to change. groupId: the group to update (format: `grp_<uuid>`). Obtain from folk_list_groups. name: new name of the group (optional). visibility: "public" or "private"… - **Folk list group members** (List). List the members of a group, paginated. For a public group, this returns every workspace member as they are all members of the group — role defaults to admin unless the member has an explicit role in the group. - **Folk add group member** (Add). Add a workspace member to a group with the given role. - **Folk update group member role** (Update). Update the role of an existing group member. Fails on a public group, and when the target user is not an explicit member of the group. - **Folk remove group member** (Delete). Remove a member from a group. Fails on a public group, when the target is not a member, or when the target is the group owner. - **Folk list group custom fields** (List). Returns the list of the group's custom fields for an entity type. - **Folk get group custom field** (Get). Fetch a single group custom field by group, entity type, and custom field name. Returns the detailed custom field definition (name, type, options, config) for that entity type. Use folk_list_group_custom_fields if the custom field name isn't already known. - **Folk create group custom field** (Create). Creates a new group custom field for an entity type (person, company, or a custom object name). - **Folk update group custom field** (Update). Updates a group custom field: rename it, update its numeric config, or add/update/remove its select options. - **Folk create interaction** (Create). Log a past interaction (a recorded touchpoint such as a call, meeting, or message) with a person or company. - **Folk list interactions** (List). List past or upcoming interactions for a single person, company, or object. - **Folk get interaction** (Get). Fetch a single interaction by its id, including the full email or calendar body, or the call transcript, when interaction privacy rules allow it. - **Folk update interaction** (Update). Update an existing manually logged interaction. Partial update — provide only the fields you want to change (title, content, dateTime, activityType). - **Folk search tasks** (Search). Search tasks in the folk workspace with optional attribute filters, paginated via cursor. - **Folk create task** (Create). Create a new task linked to a person, company, or object in folk. - **Folk get task** (Get). Fetch a single task by its ID. Use when you already have a taskId from a previous folk_search_tasks or folk_create_task call. Do not use to find or look up a task by title, due date, or other attribute — use folk_search_tasks instead. Returns the full task object: title,… - **Folk update task** (Update). Update an existing task. All fields are optional — omit any to leave unchanged. - **Folk update task todo or done** (Update). Mark a task as done or todo. Pass a completedAt datetime to mark as done, or null to mark as todo.