# How to integrate Folk MCP with CrewAI

```json
{
  "title": "How to integrate Folk MCP with CrewAI",
  "toolkit": "Folk",
  "toolkit_slug": "folk",
  "framework": "CrewAI",
  "framework_slug": "crew-ai",
  "url": "https://composio.dev/toolkits/folk/framework/crew-ai",
  "markdown_url": "https://composio.dev/toolkits/folk/framework/crew-ai.md",
  "updated_at": "2026-05-12T10:12:00.414Z"
}
```

## Introduction

This guide walks you through connecting Folk to CrewAI using the Composio tool router. By the end, you'll have a working Folk agent that can list all companies added this week, add a new company called acme corp, get details for person with email john@acme.com through natural language commands.
This guide will help you understand how to give your CrewAI agent real control over a Folk account through Composio's Folk MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Folk with

- [OpenAI Agents SDK](https://composio.dev/toolkits/folk/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/folk/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/folk/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/folk/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/folk/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/folk/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/folk/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/folk/framework/cli)
- [Google ADK](https://composio.dev/toolkits/folk/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/folk/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/folk/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/folk/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/folk/framework/llama-index)

## TL;DR

Here's what you'll learn:
- Get a Composio API key and configure your Folk connection
- Set up CrewAI with an MCP enabled agent
- Create a Tool Router session or standalone MCP server for Folk
- Build a conversational loop where your agent can execute Folk operations

## What is CrewAI?

CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews.
Key features include:
- Agent Roles: Define specialized agents with specific goals and backstories
- Task Management: Create tasks with clear descriptions and expected outputs
- Crew Orchestration: Combine agents and tasks into collaborative workflows
- MCP Integration: Connect to external tools through Model Context Protocol

## What is the Folk MCP server, and what's possible with it?

The Folk MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Folk account. It provides structured and secure access to your CRM workspace, so your agent can perform actions like managing contacts, organizing companies, retrieving group info, and handling custom fields on your behalf.
- Contact management and retrieval: Let your agent list, fetch, or delete people in your workspace, ensuring your contact database stays relevant and up to date.
- Company and organization operations: Effortlessly create new companies, retrieve details, or remove outdated organizations from your workspace via your agent.
- Workspace group insights: Ask your agent to list workspace groups and explore available group custom fields for efficient segmentation and tracking.
- User profile and context access: Allow your agent to pull current workspace user details, making personalized automations and actions possible.
- Custom field exploration: Enable your agent to list and understand custom fields for groups and entity types, powering more tailored CRM workflows.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `FOLK_CREATE_COMPANY` | Create Company | Creates a new company in the Folk workspace with the specified details. Required: company name (unique identifier). Optional: description, industry, funding details, employee range, contact info (emails, phones, urls, addresses), group assignments, and custom field values. Returns the created company with a unique ID, all provided fields, timestamps, and creator information. |
| `FOLK_CREATE_NOTE` | Create Note | Tool to create a new note in the Folk workspace. Use when you need to add a note to a person, company, or deal entity. |
| `FOLK_CREATE_PERSON` | Create Person | Creates a new person in the Folk workspace with the specified details. Optional fields include: first name, last name, emails, phones, group assignments, and custom field values. The first email/phone in the list is treated as the primary contact. Returns the created person with a unique ID, all provided fields, timestamps, and creator information. |
| `FOLK_DELETE_COMPANY` | Delete Company | Tool to delete a company from the workspace (irreversible). Use after confirming this company should be removed. |
| `FOLK_DELETE_NOTE` | Delete Note | Tool to delete an existing note in the workspace (irreversible). Use after confirming this note should be permanently removed. |
| `FOLK_FOLK_DELETE_PERSON` | Delete Person | Tool to delete an existing person in the workspace (irreversible). Use after confirming this person should be permanently removed. |
| `FOLK_DELETE_REMINDER` | Delete Reminder | Tool to delete an existing reminder in the workspace (irreversible). Use after confirming this reminder should be permanently removed. |
| `FOLK_GET_COMPANY` | Get Company | Tool to retrieve an existing company by its ID. Use after authentication has been verified. |
| `FOLK_GET_CURRENT_WORKSPACE_USER` | Get Current Workspace User | Tool to get details of the current authenticated workspace user. Use after authentication to retrieve the user's profile information. |
| `FOLK_GET_NOTE` | Get Note | Tool to retrieve an existing note by its ID. Use when you need the full content and metadata of a specific note. |
| `FOLK_GET_PERSON` | Get Person | Tool to retrieve an existing person by their ID. Use when you need full profile details of a person by their unique identifier. |
| `FOLK_GET_USER` | Get User | Tool to retrieve a user by their unique identifier. Use when you need to get details of a specific workspace user. |
| `FOLK_FOLK_LIST_COMPANIES` | List Companies | Tool to list companies in the workspace. Use when you need a paginated overview of companies, optionally filtered. |
| `FOLK_LIST_GROUP_CUSTOM_FIELDS` | List Group Custom Fields | Tool to list custom fields for a specific group and entity type. Use after selecting a group and entity type to inspect available custom fields. |
| `FOLK_LIST_GROUPS` | List Groups | Tool to list workspace groups. Use when you need to retrieve a paginated list of all workspace groups after authentication. |
| `FOLK_LIST_NOTES` | List Notes | Tool to list notes in the workspace. Use when you need to retrieve notes with pagination support. |
| `FOLK_LIST_PEOPLE` | List People | Tool to list people in the workspace. Use when you need to paginate through contacts after authentication. |
| `FOLK_LIST_REMINDERS` | List Reminders | Tool to list reminders in the workspace. Use when you need a paginated overview of reminders, optionally filtered by entity. |
| `FOLK_LIST_USERS` | List Users | Tool to list workspace users. Use when you need to paginate through users list. |
| `FOLK_LIST_WEBHOOKS` | List Webhooks | Tool to list webhooks in the workspace. Use when you need to retrieve configured webhooks with pagination support. |
| `FOLK_UPDATE_COMPANY` | Update Company | Tool to update an existing company in the workspace. Use after confirming the company ID; only provided fields are updated and list fields replace existing values. |
| `FOLK_UPDATE_NOTE` | Update Note | Tool to update an existing note in the workspace. Use after confirming the note ID; only provided fields are updated. |
| `FOLK_UPDATE_PERSON` | Update Person | Tool to update an existing person in the workspace. Use after confirming the person ID; only provided fields are updated and list fields replace existing values. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Folk MCP server is an implementation of the Model Context Protocol that connects your AI agent to Folk. It provides structured and secure access so your agent can perform Folk operations on your behalf through a secure, permission-based interface.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. Prerequisites

Before starting, make sure you have:
- Python 3.9 or higher
- A Composio account and API key
- A Folk connection authorized in Composio
- An OpenAI API key for the CrewAI LLM
- Basic familiarity with Python

### 1. Getting API Keys for OpenAI and Composio

OpenAI API Key
- Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) and create an API key. You'll need credits to use the models, or you can connect to another model provider.
- Keep the API key safe.
Composio API Key
- Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Navigate to your API settings and generate a new API key.
- Store this key securely as you'll need it for authentication.

### 2. Install dependencies

**What's happening:**
- composio connects your agent to Folk via MCP
- crewai provides Agent, Task, Crew, and LLM primitives
- crewai-tools[mcp] includes MCP helpers
- python-dotenv loads environment variables from .env
```bash
pip install composio crewai crewai-tools[mcp] python-dotenv
```

### 3. Set up environment variables

Create a .env file in your project root.
What's happening:
- COMPOSIO_API_KEY authenticates with Composio
- USER_ID scopes the session to your account
- OPENAI_API_KEY lets CrewAI use your chosen OpenAI model
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here
```

### 4. Import dependencies

**What's happening:**
- CrewAI classes define agents and tasks, and run the workflow
- MCPServerHTTP connects the agent to an MCP endpoint
- Composio will give you a short lived Folk MCP URL
```python
import os
from composio import Composio
from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
import dotenv

dotenv.load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")
```

### 5. Create a Composio Tool Router session for Folk

**What's happening:**
- You create a Folk only session through Composio
- Composio returns an MCP HTTP URL that exposes Folk tools
```python
composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["folk"])

url = session.mcp.url
```

### 6. Initialize the MCP Server

**What's Happening:**
- Server Configuration: The code sets up connection parameters including the MCP server URL, streamable HTTP transport, and Composio API key authentication.
- MCP Adapter Bridge: MCPServerAdapter acts as a context manager that converts Composio MCP tools into a CrewAI-compatible format.
- Agent Setup: Creates a CrewAI Agent with a defined role (Search Assistant), goal (help with internet searches), and access to the MCP tools.
- Configuration Options: The agent includes settings like verbose=False for clean output and max_iter=10 to prevent infinite loops.
- Dynamic Tool Usage: Once created, the agent automatically accesses all Composio Search tools and decides when to use them based on user queries.
```python
server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users search the internet effectively",
        backstory="You are a helpful assistant with access to search tools.",
        tools=tools,
        verbose=False,
        max_iter=10,
    )
```

### 7. Create a CLI Chatloop and define the Crew

**What's Happening:**
- Interactive CLI Setup: The code creates an infinite loop that continuously prompts for user input and maintains the entire conversation history in a string variable.
- Input Validation: Empty inputs are ignored to prevent processing blank messages and keep the conversation clean.
- Context Building: Each user message is appended to the conversation context, which preserves the full dialogue history for better agent responses.
- Dynamic Task Creation: For every user input, a new Task is created that includes both the full conversation history and the current request as context.
- Crew Execution: A Crew is instantiated with the agent and task, then kicked off to process the request and generate a response.
- Response Management: The agent's response is converted to a string, added to the conversation context, and displayed to the user, maintaining conversational continuity.
```python
print("Chat started! Type 'exit' or 'quit' to end.\n")

conversation_context = ""

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ["exit", "quit", "bye"]:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_context += f"\nUser: {user_input}\n"
    print("\nAgent is thinking...\n")

    task = Task(
        description=(
            f"Conversation history:\n{conversation_context}\n\n"
            f"Current request: {user_input}"
        ),
        expected_output="A helpful response addressing the user's request",
        agent=agent,
    )

    crew = Crew(agents=[agent], tasks=[task], verbose=False)
    result = crew.kickoff()
    response = str(result)

    conversation_context += f"Agent: {response}\n"
    print(f"Agent: {response}\n")
```

## Complete Code

```python
from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter
from composio import Composio
from dotenv import load_dotenv
import os

load_dotenv()

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

# Initialize Composio and create a session
composio = Composio(api_key=COMPOSIO_API_KEY)
session = composio.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["folk"],
)
url = session.mcp.url

# Configure LLM
llm = LLM(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY"),
)

server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users with internet searches",
        backstory="You are an expert assistant with access to Composio Search tools.",
        tools=tools,
        llm=llm,
        verbose=False,
        max_iter=10,
    )

    print("Chat started! Type 'exit' or 'quit' to end.\n")

    conversation_context = ""

    while True:
        user_input = input("You: ").strip()

        if user_input.lower() in ["exit", "quit", "bye"]:
            print("\nGoodbye!")
            break

        if not user_input:
            continue

        conversation_context += f"\nUser: {user_input}\n"
        print("\nAgent is thinking...\n")

        task = Task(
            description=(
                f"Conversation history:\n{conversation_context}\n\n"
                f"Current request: {user_input}"
            ),
            expected_output="A helpful response addressing the user's request",
            agent=agent,
        )

        crew = Crew(agents=[agent], tasks=[task], verbose=False)
        result = crew.kickoff()
        response = str(result)

        conversation_context += f"Agent: {response}\n"
        print(f"Agent: {response}\n")
```

## Conclusion

You now have a CrewAI agent connected to Folk through Composio's Tool Router. The agent can perform Folk operations through natural language commands.
Next steps:
- Add role-specific instructions to customize agent behavior
- Plug in more toolkits for multi-app workflows
- Chain tasks for complex multi-step operations

## How to build Folk MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/folk/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/folk/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/folk/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/folk/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/folk/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/folk/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/folk/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/folk/framework/cli)
- [Google ADK](https://composio.dev/toolkits/folk/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/folk/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/folk/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/folk/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/folk/framework/llama-index)

## Related Toolkits

- [Hubspot](https://composio.dev/toolkits/hubspot) - HubSpot is an all-in-one marketing, sales, and customer service platform. It lets teams nurture leads, automate outreach, and track every customer interaction in one place.
- [Pipedrive](https://composio.dev/toolkits/pipedrive) - Pipedrive is a sales management platform offering pipeline visualization, lead tracking, and workflow automation. It helps sales teams keep deals moving forward efficiently and never miss a follow-up.
- [Salesforce](https://composio.dev/toolkits/salesforce) - Salesforce is a leading CRM platform that helps businesses manage sales, service, and marketing. It centralizes customer data, enabling teams to drive growth and build strong relationships.
- [Apollo](https://composio.dev/toolkits/apollo) - Apollo is a CRM and lead generation platform that helps businesses discover contacts and manage sales pipelines. Use it to streamline customer outreach and track your deals from one place.
- [Attio](https://composio.dev/toolkits/attio) - Attio is a customizable CRM and workspace for managing your team's relationships and workflows. It helps teams organize contacts, automate tasks, and collaborate more efficiently.
- [Acculynx](https://composio.dev/toolkits/acculynx) - AccuLynx is a cloud-based roofing business management software for contractors. It streamlines project tracking, lead management, and document sharing.
- [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time.
- [Affinity](https://composio.dev/toolkits/affinity) - Affinity is a relationship intelligence CRM that helps private capital investors find, manage, and close more deals. It streamlines deal flow and surfaces key connections to help you win opportunities.
- [Agencyzoom](https://composio.dev/toolkits/agencyzoom) - AgencyZoom is a sales and performance platform built for P&C insurance agencies. It helps agents boost sales, retain clients, and analyze producer results in one place.
- [Bettercontact](https://composio.dev/toolkits/bettercontact) - Bettercontact is a smart contact enrichment tool for finding emails and phone numbers. It helps boost lead generation with automated, waterfall search across multiple sources.
- [Blackbaud](https://composio.dev/toolkits/blackbaud) - Blackbaud provides cloud-based software for nonprofits, schools, and healthcare institutions. It streamlines fundraising, donor management, and mission-driven operations.
- [Brilliant directories](https://composio.dev/toolkits/brilliant_directories) - Brilliant Directories is an all-in-one platform for building and managing online membership communities and business directories. It streamlines listings, member management, and engagement tools into a single, easy interface.
- [Capsule crm](https://composio.dev/toolkits/capsule_crm) - Capsule CRM is a user-friendly CRM platform for managing contacts and sales pipelines. It helps businesses organize relationships and streamline their sales process efficiently.
- [Centralstationcrm](https://composio.dev/toolkits/centralstationcrm) - CentralStationCRM is an easy-to-use CRM software focused on collaboration and long-term customer relationships. It helps teams manage contacts, deals, and communications all in one place.
- [Clientary](https://composio.dev/toolkits/clientary) - Clientary is a platform for managing clients, invoices, projects, proposals, and more. It streamlines client work and saves you serious admin time.
- [Close](https://composio.dev/toolkits/close) - Close is a CRM platform built for sales teams, combining calling, email automation, and predictive dialers. It streamlines sales workflows and boosts productivity with all-in-one communication tools.
- [Dropcontact](https://composio.dev/toolkits/dropcontact) - Dropcontact is a B2B email finder and data enrichment service for professionals. It delivers verified email addresses and enriches contact info with up-to-date data.
- [Dynamics365](https://composio.dev/toolkits/dynamics365) - Dynamics 365 is Microsoft's platform combining CRM, ERP, and productivity apps. It streamlines sales, marketing, service, and operations in one place.
- [Espocrm](https://composio.dev/toolkits/espocrm) - EspoCRM is an open-source web application for managing customer relationships. It helps businesses organize contacts, track leads, and streamline their sales process.
- [Fireberry](https://composio.dev/toolkits/fireberry) - Fireberry is a CRM platform that streamlines customer and sales management. It helps businesses organize contacts, automate sales, and integrate with other business tools.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Folk MCP?

With a standalone Folk MCP server, the agents and LLMs can only access a fixed set of Folk tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Folk and many other apps based on the task at hand, all through a single MCP endpoint.

### Can I use Tool Router MCP with CrewAI?

Yes, you can. CrewAI fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Folk tools.

### Can I manage the permissions and scopes for Folk while using Tool Router?

Yes, absolutely. You can configure which Folk scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

### How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Folk data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)
