How to integrate FuseDesk MCP with CrewAI

This guide walks you through connecting FuseDesk to CrewAI using the Composio tool router. By the end, you'll have a working FuseDesk agent that can create support cases, view case details, add case notes, tag cases, and merge duplicate cases through natural language commands. This guide will help you understand how to give your CrewAI agent real control over a FuseDesk account through Composio's FuseDesk MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

FuseDesk logoFuseDesk
Api Key

FuseDesk is a customer support platform for managing cases, email conversations, contacts, departments, representatives, chats, and webhooks. It helps support teams keep customer conversations organized so issues get routed, tracked, and resolved faster.

27 Tools

Introduction

This guide walks you through connecting FuseDesk to CrewAI using the Composio tool router. By the end, you'll have a working FuseDesk agent that can create support cases, view case details, add case notes, tag cases, and merge duplicate cases through natural language commands.

This guide will help you understand how to give your CrewAI agent real control over a FuseDesk account through Composio's FuseDesk MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate FuseDesk with

TL;DR

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

The FuseDesk MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your FuseDesk account. It provides structured and secure access to support cases, email conversations, contacts, departments, representatives, chats, and webhooks, so your agent can create and update cases, reply to customers, manage contacts, monitor chats, and review support activity on your behalf.

  • Case creation and management: Have your agent open support cases, update their content or status, change tags, add internal notes, snooze follow-ups, and merge related cases.
  • Customer replies and email review: Let the agent search support emails, read complete messages, and send replies to customers from the appropriate case.
  • Contact and team coordination: Direct your agent to create, find, and update contacts, review departments, and check representative profiles when deciding where work belongs.
  • Chat monitoring and handling: Instruct your agent to list active chats, read conversation histories, transfer or rename chats, mark them seen or unseen, and close completed conversations.
  • Support oversight and automation review: Have your agent search cases by customer, assignment, status, text, or date, apply bulk changes, review case tags, and list configured webhook subscriptions.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step08 STEPS
1

Prerequisites

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

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard 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.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

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

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

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
5

Import dependencies

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")
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 FuseDesk MCP URL
6

Create a Composio Tool Router session for FuseDesk

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["fusedesk"])

url = session.mcp.url
What's happening:
  • You create a FuseDesk only session through Composio
  • Composio returns an MCP HTTP URL that exposes FuseDesk tools
7

Initialize the MCP Server

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,
    )
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.
8

Create a CLI Chatloop and define the Crew

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")
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.

Complete Code

Here's the complete code to get you started with FuseDesk and CrewAI:

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=["fusedesk"],
)
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 FuseDesk through Composio's Tool Router. The agent can perform FuseDesk 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
TOOLS

Supported Tools

Every FuseDesk action and event your agent gets out of the box.

Add Case Note

Add an internal note or call record to a case and optionally change its status.

Bulk Merge Cases

Irreversibly merge multiple FuseDesk cases.

Bulk Update Cases

Apply an assignment, department, status, tag, CRM automation, CRM tag, or snooze operation to multiple FuseDesk cases.

Change Case Tag

Apply or remove one existing case tag from one FuseDesk case.

Close Chat

Irreversibly close a FuseDesk chat and end the live conversation.

Create Case

Open a support case for a customer in a FuseDesk department.

Create Case Tag

Create a reusable FuseDesk case tag.

Create Contact

Create a FuseDesk contact.

Get Case

Get one FuseDesk support case and its complete history by case ID.

Get Chat

Get one FuseDesk chat and its complete message history by chat UUID.

Get Contact

Get a FuseDesk contact by UUID, including current data from its linked CRM contact.

Get Department

Get a FuseDesk department's assignment, template, staleness, feedback, phone, and archive settings by department ID.

Get Email

Get one FuseDesk email by its numeric ID, including its complete body.

Get Rep

Get a FuseDesk rep's detailed profile, permissions, and signatures.

List Case Tags

List available FuseDesk case tags and their case counts.

List Chats

List active FuseDesk chats across connected chat platforms, including assignment links, recent-message context, and lifecycle state.

List Departments

List active, archived, or all FuseDesk departments using the current v2 representation.

List Reps

List active and disabled FuseDesk reps for assignment and ownership decisions.

List Webhooks

List configured FuseDesk webhook subscriptions.

Reply To Case

Send an external email reply on a FuseDesk case using supplied content or an existing reply template.

Search Cases

Search support cases by customer, assignment, status, text, and lifecycle dates, returning one controllable page.

Search Contacts

Search FuseDesk and linked CRM contacts by required text.

Search Emails

Search all or only unassigned FuseDesk emails, returning one controllable page with optionally truncated bodies.

Snooze Case

Snooze a case until an absolute date/time or FuseDesk relative-time expression.

Update Case

Change a case's content, customer link, assignment, department, or status.

Update Chat

Rename, transfer, relink, or mark a live FuseDesk chat seen or unseen.

Update Contact

Update a FuseDesk contact.

FAQ

Frequently asked questions

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

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 FuseDesk tools.

Yes, absolutely. You can configure which FuseDesk 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.

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 FuseDesk data and credentials are handled as safely as possible.

Start with FuseDesk.It takes 30 seconds.

Managed auth, hosted MCP servers, and every FuseDesk tool your agent needs.Free to start.

Start building