# How to integrate Magnetic MCP with CrewAI

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

## Introduction

This guide walks you through connecting Magnetic to CrewAI using the Composio tool router. By the end, you'll have a working Magnetic agent that can list all upcoming follow-ups for me, search client contacts by company name, get all tags for contact id 123 through natural language commands.
This guide will help you understand how to give your CrewAI agent real control over a Magnetic account through Composio's Magnetic MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Magnetic with

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

## TL;DR

Here's what you'll learn:
- Get a Composio API key and configure your Magnetic connection
- Set up CrewAI with an MCP enabled agent
- Create a Tool Router session or standalone MCP server for Magnetic
- Build a conversational loop where your agent can execute Magnetic 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 Magnetic MCP server, and what's possible with it?

The Magnetic MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Magnetic account. It provides structured and secure access to your projects, client contacts, users, and task data, so your agent can perform actions like managing follow-ups, searching contacts, retrieving project statuses, and organizing your team’s workflow with ease.
- Personal follow-up and task management: Automatically retrieve your upcoming follow-ups or tasks so you never miss important deadlines or action items.
- Client contact discovery and tagging: Search for client contacts using specific criteria and view all tags associated with any contact to keep your CRM up to date and organized.
- Project grouping and status tracking: Fetch groupings, view their statuses, and retrieve project-related tags to stay on top of ongoing jobs and opportunities.
- User and team information access: Instantly pull details about any team member or audit the list of all users in your company for better collaboration and resource planning.
- Opportunity status monitoring: Check the latest opportunity statuses to track sales pipelines or unsigned deals directly from your agent.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `MAGNETIC_CLIENTS_GET_CURRENT_FOLLOWUPS` | Get Current Follow-ups | Tool to retrieve upcoming follow-ups assigned to the authenticated user. Use after authentication to view scheduled tasks. |
| `MAGNETIC_CLIENTS_SEARCH_CONTACTS` | Search Client Contacts | Tool to search contacts by field or client ID. Use when you need to retrieve client contacts matching given criteria after authentication. |
| `MAGNETIC_CREATE_GROUPING` | Create Magnetic Grouping | Tool to create a new opportunity or job (grouping) in Magnetic HQ. Use when you need to organize tasks and track project progress for a new opportunity or job. |
| `MAGNETIC_CREATE_TASK` | Create Magnetic Task | Tool to create a new task in Magnetic HQ. Use when you need to add tasks to the system, optionally assigning them to users or linking to opportunities. |
| `MAGNETIC_GET_CONTACT_TAGS` | Get Contact Tags | Tool to get all tags associated with a contact. Use after confirming the contactId to list contact tags. |
| `MAGNETIC_GET_GROUPING_BY_ID` | Get Magnetic Grouping by ID | Tool to retrieve details for a specific grouping (opportunity/job) by its ID. Use when you need detailed information about a specific grouping. |
| `MAGNETIC_GET_GROUPING_STATUSES` | Get Grouping Statuses | Tool to retrieve the list of statuses for signed groupings. Use after authentication when you need available grouping status options for tasks or jobs. |
| `MAGNETIC_GET_GROUPING_TAGS` | Get Grouping Tags | Tool to retrieve tags associated with any groupings owned by the company. Use after authentication when grouping tags are needed. |
| `MAGNETIC_GET_OPPORTUNITY_STATUSES` | Get Magnetic Opportunity Statuses | Tool to retrieve opportunity statuses. Use when you need current status options for unsigned groupings (opportunities). |
| `MAGNETIC_GET_TASK` | Get Magnetic Task | Tool to retrieve a task by its ID. Use after confirming you have the taskId. |
| `MAGNETIC_GET_USER_BY_ID` | Get User by ID | Tool to retrieve details for a specific Magnetic user by their ID. Use when you need to fetch a user's profile information. |
| `MAGNETIC_GET_USERS` | Get Users | Tool to retrieve the list of all users in the authenticated user's company. Use after authentication to audit or manage user accounts. |
| `MAGNETIC_LIST_COMPANIES` | List Companies | Tool to retrieve all companies from the Magnetic HQ account. Use after authentication to view all client companies. |
| `MAGNETIC_TASKS_GET_GROUPING_CUSTOM_FIELD_DEFINITIONS` | Get Grouping Custom Field Definitions | Tool to retrieve all custom field definitions for groupings. Use after authentication when you need to fetch available grouping custom field definitions for tasks. |

## Supported Triggers

None listed.

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

The Magnetic MCP server is an implementation of the Model Context Protocol that connects your AI agent to Magnetic. It provides structured and secure access so your agent can perform Magnetic 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 Magnetic 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 Magnetic 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 Magnetic 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 Magnetic

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

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=["magnetic"],
)
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 Magnetic through Composio's Tool Router. The agent can perform Magnetic 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 Magnetic MCP Agent with another framework

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

## Related Toolkits

- [Google Sheets](https://composio.dev/toolkits/googlesheets) - Google Sheets is a cloud-based spreadsheet tool for real-time collaboration and data analysis. It lets teams work together from anywhere, updating information instantly.
- [Notion](https://composio.dev/toolkits/notion) - Notion is a collaborative workspace for notes, docs, wikis, and tasks. It streamlines team knowledge, project tracking, and workflow customization in one place.
- [Airtable](https://composio.dev/toolkits/airtable) - Airtable combines the flexibility of spreadsheets with the power of a database for easy project and data management. Teams use Airtable to organize, track, and collaborate with custom views and automations.
- [Asana](https://composio.dev/toolkits/asana) - Asana is a collaborative work management platform for teams to organize and track projects. It streamlines teamwork, boosts productivity, and keeps everyone aligned on goals.
- [Google Tasks](https://composio.dev/toolkits/googletasks) - Google Tasks is a to-do list and task management tool integrated into Gmail and Google Calendar. It helps you organize, track, and complete tasks across your Google ecosystem.
- [Linear](https://composio.dev/toolkits/linear) - Linear is a modern issue tracking and project planning tool for fast-moving teams. It helps streamline workflows, organize projects, and boost productivity.
- [Jira](https://composio.dev/toolkits/jira) - Jira is Atlassian’s platform for bug tracking, issue tracking, and agile project management. It helps teams organize work, prioritize tasks, and deliver projects efficiently.
- [Clickup](https://composio.dev/toolkits/clickup) - ClickUp is an all-in-one productivity platform for managing tasks, docs, goals, and team collaboration. It streamlines project workflows so teams can work smarter and stay organized in one place.
- [Monday](https://composio.dev/toolkits/monday) - Monday.com is a customizable work management platform for project planning and collaboration. It helps teams organize tasks, automate workflows, and track progress in real time.
- [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.
- [Agiled](https://composio.dev/toolkits/agiled) - Agiled is an all-in-one business management platform for CRM, projects, and finance. It helps you streamline workflows, consolidate client data, and manage business processes in one place.
- [Ascora](https://composio.dev/toolkits/ascora) - Ascora is a cloud-based field service management platform for service businesses. It streamlines scheduling, invoicing, and customer operations in one place.
- [Basecamp](https://composio.dev/toolkits/basecamp) - Basecamp is a project management and team collaboration tool by 37signals. It helps teams organize tasks, share files, and communicate efficiently in one place.
- [Beeminder](https://composio.dev/toolkits/beeminder) - Beeminder is an online goal-tracking platform that uses monetary pledges to keep you motivated. Stay accountable and hit your targets with real financial incentives.
- [Boxhero](https://composio.dev/toolkits/boxhero) - Boxhero is a cloud-based inventory management platform for SMBs, offering real-time updates, barcode scanning, and team collaboration. It helps businesses streamline stock tracking and analytics for smarter inventory decisions.
- [Breathe HR](https://composio.dev/toolkits/breathehr) - Breathe HR is cloud-based HR software for SMEs to manage employee data, absences, and performance. It simplifies HR admin, making it easy to keep employee records accurate and up to date.
- [Breeze](https://composio.dev/toolkits/breeze) - Breeze is a project management platform designed to help teams plan, track, and collaborate on projects. It streamlines workflows and keeps everyone on the same page.
- [Bugherd](https://composio.dev/toolkits/bugherd) - Bugherd is a visual feedback and bug tracking tool for websites. It helps teams and clients report website issues directly on live sites for faster fixes.
- [Canny](https://composio.dev/toolkits/canny) - Canny is a platform for managing customer feedback and feature requests. It helps teams prioritize product decisions based on real user insights.
- [Chmeetings](https://composio.dev/toolkits/chmeetings) - Chmeetings is a church management platform for events, members, donations, and volunteers. It streamlines church operations and improves community engagement.

## Frequently Asked Questions

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

With a standalone Magnetic MCP server, the agents and LLMs can only access a fixed set of Magnetic tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Magnetic 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 Magnetic tools.

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

Yes, absolutely. You can configure which Magnetic 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 Magnetic data and credentials are handled as safely as possible.

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