Folk MCP connector for AI agents

CALL ANY TOOL

12 tools covering folk.

folkmcp_folk_get_object

Folk get object

Retrieve a single custom object record from Folk CRM by its ID, including all native and custom fields.

Parameters

Name

Type

Required

Description

groupId

string

Required

The group ID the object belongs to.

objectId

string

Required

The ID of the object to retrieve.

objectType

string

Required

The object type.

folkmcp_folk_get_person

Folk get person

folkmcp_folk_get_company

Folk get company

folkmcp_folk_create_object

Folk create object

folkmcp_folk_create_person

Folk create person

folkmcp_folk_search_people

Folk search people

folkmcp_folk_update_object

Folk update object

folkmcp_folk_update_person

Folk update person

folkmcp_folk_create_company

Folk create company

folkmcp_folk_search_objects

Folk search objects

folkmcp_folk_update_company

Folk update company

folkmcp_folk_search_companies

Folk search companies

folkmcp_folk_get_current_user

Folk get current user

folkmcp_folk_get_workspace_structure

Folk get workspace structure

Build your Agent

Same auth pattern across every framework.

token = client.agent.get_token(user_id="user_id", connector="folkmcp")

const token = await client.agent.getToken({ userId: "user_id", connector: "folkmcp" });

const token = await client.agent.getToken({ userId: "user_id", connector: "folkmcp" });

token = client.agent.get_token(user_id="user_id", connector="folkmcp")

Try these prompts

Paste any prompt into your agent to get started.

Get started

SEE HOW AUTH WORKS

User authorises once. Every agent call after uses their token with scope enforcement.

1

Authorize

Your user connects

Folk MCP

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

2

Store

Their

Folk MCP

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

3

Resolve

When your agent calls a

Folk MCP

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

4

Audit

Every

Folk MCP

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other connectors.

GTM and RevOps Teams

CRM AI agent

Reads the Granola transcript after every call, extracts next steps and updates the HubSpot record, drafts the follow-up in Gmail, and confirms in Slack, all on the rep's own delegated OAuth.

GTM and RevOps Teams

Deal intelligence agent

Pulls recent Gong calls, scores deal risk with an LLM, cross-references the record in Attio, and DMs each owner their at-risk deals in Slack. Every read is scoped to that rep's own access.

GTM and RevOps Teams

Sales call prep agent

Reads tomorrow's calls from Google Calendar, mines past Granola notes and Attio history for context, and delivers each rep a prep brief in Slack, scoped to the calls that rep actually owns.

GTM and RevOps Teams

Outbound prospecting agent

Searches Apollo for prospects matching your ICP, scores and ranks them, drafts personalized outreach in Gmail, and logs every send to Google Sheets. Mail goes out as the rep, not from a shared inbox.

Test other agents

See the same per-user auth pattern across other connectors.

GTM

CRM AI agent

Turn each Granola call transcript into a HubSpot record update, a drafted Gmail follow-up, and a Slack recap.

SALES

Deal intelligence agent

Score Gong call risk with an LLM, cross-reference the Attio record, and DM each owner their at-risk deals in Slack.

SALES

Sales call prep agent

Read tomorrow's calls from Google Calendar, mine Granola notes and Attio history, and deliver each rep a prep brief in Slack.

SALES

Outbound prospecting agent

Search Apollo for ICP matches, rank them, draft personalised Gmail outreach, and log every send to Google Sheets.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Folk as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Folk OAuth token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Folk?
Yes. Pass a tool name filter to listScopedTools so the sales agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Folk.

What happens when a user revokes Folk access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Which contacts and groups can the agent manage in Folk?
Only those in workspaces the authorizing user belongs to. People, company, and object writes attribute to that user, so shared relationship history in Folk stays trustworthy.

Folk MCP

Folk MCP tools for AI agents