How do AI agents use Folk through Open Connector?

Your user connects Folk once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Folk tools to your agent over MCP or a typed API, with credentials injected server-side on each call.

Is this a Folk MCP server?

Yes. Open Connector can serve Folk as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Folk actions with credentials injected server-side.

Where do Folk credentials live?

In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

Folk integration

Folk integration for AI agents.

Folk integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves Folk tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.

View source on GitHub All integrations →

What your agents can do

Real Folk actions, managed and audited.

Your user connects Folk once; your agent can then use Folk's CRM API to manage people, companies, deals, notes, reminders, tasks, interactions, users, groups, and webhooks — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.

1
Your user grants Folk access once (OAuth) — the token lands in the vault.
2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
3
Every routed call appends a hash-chained audit record — nothing leaves your infra.

Tools & triggers

Supported Folk tools.

50 tools are generated from the published Folk catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.

Showing 50 tools. All published catalog entries are included in this page's server-rendered HTML.

Complete a task: Mark an existing task as completed.; Tasks
Create a company: Create a new company in the workspace.; Companies
Create a deal: Create a new deal in the workspace.; Deals
Create an interaction: Creates a new [interaction](https://help.folk.app/en/articles/7012167-log-a-new-interaction) with a person or a company.; Interactions
Create a note: Create a new note in the workspace.; Notes
Create a person: Create a new person in the workspace.; People
Create a reminder: Create a new reminder in the workspace.; Reminders
Create a task: Create a new task in the workspace.; Tasks
Create a webhook: Creates a new webhook listening to workspace events.; Webhooks
Delete a company: Delete an existing company in the workspace.; Companies
Delete a deal: Delete an existing deal in the workspace.; Deals
Delete an interaction: Delete an existing logged interaction. Imported interactions cannot be deleted.; Interactions
Delete a note: Delete an existing note in the workspace.; Notes
Delete a person: Delete an existing person in the workspace.; People
Delete a reminder: Delete an existing reminder in the workspace.; Reminders
Delete a task: Delete an existing task in the workspace.; Tasks
Delete a webhook: Delete an existing webhook in the workspace.; Webhooks
Get a company: Retrieve an existing company in the workspace.; Companies
Get the current user: Returns the current workspace user.; Users
Get a deal: Retrieve an existing deal in the workspace.; Deals
Get an interaction: Retrieves a single interaction. Full email or calendar body is included when privacy rules allow it.; Interactions
Get a note: Retrieve an existing note in the workspace.; Notes
Get a person: Retrieve an existing person in the workspace.; People
Get a reminder: Retrieve an existing reminder in the workspace.; Reminders
Get a task: Retrieve an existing task in the workspace.; Tasks
Get a user: Returns a workspace user.; Users
Get a webhook: Retrieve an existing webhook in the workspace.; Webhooks
Search for companies: Search for companies in the workspace.; Companies
Search deals: Search deals in the workspace.; Deals
Search for people: Search for people in the workspace.; People
List companies: Retrieve a list of companies in the workspace.; Companies
List deals: Retrieve a list of deals in the workspace.; Deals
List group custom fields: Returns a list of group custom fields for an entity type.; Groups
List groups: Returns a list of workspace groups.; Groups
List notes: Retrieve a list of notes in the workspace.; Notes
List past interactions: Retrieves paginated past interactions linked to a person, company, or object.; Interactions
List people: Retrieve a list of people in the workspace.; People
List reminders: Retrieve a list of reminders in the workspace.; Reminders
List upcoming interactions: Retrieves paginated upcoming interactions linked to a person, company, or object.; Interactions
List users: Returns a list of workspace users.; Users
List webhooks: Retrieve a list of webhooks in the workspace.; Webhooks
Cancel the completion of a task: Mark an existing task as not completed.; Tasks
Update a company: Update an existing company in the workspace.; Companies
Update a deal: Update an existing deal in the workspace.; Deals
Update an interaction: Partially update an existing logged interaction (title, content, date-time, activityType). Imported interactions cannot be updated.; Interactions
Update a note: Update an existing note in the workspace.; Notes
Update a person: Update an existing person in the workspace.; People
Update a reminder: Update an existing reminder in the workspace.; Reminders
Update a task: Update an existing task in the workspace.; Tasks
Update a webhook: Update an existing webhook in the workspace.; Webhooks

FAQ

Folk integration, answered

How do AI agents use Folk through Open Connector?: Your user connects Folk once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Folk tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
Is this a Folk MCP server?: Yes. Open Connector can serve Folk as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Folk actions with credentials injected server-side.
Where do Folk credentials live?: In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

Give your agents Folk — keep the keys.

Open source, self-hostable, with Folk credentials that never leave your infrastructure. Run it from source today.

View source on GitHub How the MCP gateway works →