How to integrate Imagekit io MCP with CrewAI

Framework Integration Gradient
Imagekit io Logo
CrewAI Logo
divider

Introduction

This guide walks you through connecting Imagekit io to CrewAI using the Composio tool router. By the end, you'll have a working Imagekit io agent that can move all event photos to new 2024 folder, delete outdated logo file from media library, create custom metadata field for copyright info, copy marketing assets folder to backup location through natural language commands.

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

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

TL;DR

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

The Imagekit io MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your ImageKit.io account. It provides structured and secure access to your media library, so your agent can perform actions like organizing folders, managing files, handling bulk operations, editing metadata, and cleaning up assets on your behalf.

  • Bulk file operations: Effortlessly move, copy, or update tags on multiple files at once to streamline large-scale asset management.
  • Folder organization and management: Ask your agent to create new folders for better asset structuring or delete old folders—including all their contents—when you need to tidy up.
  • Custom metadata control: Let your agent create or delete custom metadata fields, so your media assets stay rich with the information your workflows need.
  • File and version cleanup: Instruct the agent to permanently delete files or remove outdated file versions to keep your storage lean and organized.
  • Bulk job monitoring: Have your agent track the status of ongoing bulk jobs, like folder copies or moves, so you always know what’s happening behind the scenes.

Supported Tools & Triggers

Tools
Bulk Job StatusTool to check status of a bulk job.
Bulk Move FilesTool to move multiple files in bulk.
Bulk Remove TagsTool to remove tags from multiple files in bulk.
Copy FolderTool to initiate a bulk copy of a folder.
Create Custom Metadata FieldTool to create a custom metadata field.
Create FolderTool to create a new folder.
Delete Custom Metadata FieldTool to delete a custom metadata field.
Delete FileTool to delete a file.
Delete File VersionTool to delete a specific non-current file version.
Delete FolderTool to delete a folder.
Delete Multiple FilesTool to delete multiple files.
Get Upload Authentication ParametersTool to generate authentication parameters for client-side file uploads.
Get File DetailsTool to retrieve details of a specific file.
Get File MetadataTool to retrieve metadata of an uploaded file.
Get File Version DetailsTool to retrieve details of a specific file version.
Get UsageTool to retrieve account usage metrics.
List and Search AssetsTool to list and search assets in your ImageKit account.
List Custom Metadata FieldsTool to list all custom metadata fields.
List File VersionsTool to list all versions of a file.
Move FolderTool to initiate a bulk move of a folder.
Purge ImageKit CacheTool to purge CDN and ImageKit caches for a given URL.
Check purge cache statusTool to check the status of a cache purge request.
Rename FileTool to rename a file.
Restore File VersionTool to restore a specific non-current file version as the current one.
Update Custom Metadata FieldTool to update an existing custom metadata field.
Update File DetailsTool to update details of a file.

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

What is Tool Router?

Composio's Tool Router 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 Tool Router

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

How the Tool Router works

The Tool Router 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

Prerequisites

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

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.

Install dependencies

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

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

Import dependencies

python
from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter  # optional import if you plan to adapt tools
from composio import Composio
from dotenv import load_dotenv
import os
from crewai.mcp import MCPServerHTTP

load_dotenv()
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 Imagekit io MCP URL

Create a Composio Tool Router session for Imagekit io

python
composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
session = composio.create(
    user_id=os.getenv("USER_ID"),
    toolkits=["imagekit_io"],
)
url = session.mcp.url
What's happening:
  • You create a Imagekit io only session through Composio
  • Composio returns an MCP HTTP URL that exposes Imagekit io tools

Configure the LLM

python
llm = LLM(
    model="gpt-5-mini",
    api_key=os.getenv("OPENAI_API_KEY"),
)
What's happening:
  • CrewAI will call this LLM for planning and responses
  • You can swap in a different model if needed

Attach the MCP server and create the agent

python
toolkit_agent = Agent(
    role="Imagekit io Assistant",
    goal="Help users interact with Imagekit io through natural language commands",
    backstory=(
        "You are an expert assistant with access to Imagekit io tools. "
        "You can perform various Imagekit io operations on behalf of the user."
    ),
    mcps=[
        MCPServerHTTP(
            url=url,
            streamable=True,
            cache_tools_list=True,
            headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")},
        ),
    ],
    llm=llm,
    verbose=True,
    max_iter=10,
)
What's happening:
  • MCPServerHTTP connects the agent to the Imagekit io MCP endpoint
  • cache_tools_list saves a tools catalog for faster subsequent runs
  • verbose helps you see what the agent is doing

Add a REPL loop with Task and Crew

python
print("Chat started! Type 'exit' or 'quit' to end.\n")
print("Try asking the agent to perform Imagekit io operations.\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"Based on the conversation history:\n{conversation_context}\n\n"
            f"Current user request: {user_input}\n\n"
            f"Please help the user with their Imagekit io related request."
        ),
        expected_output="A helpful response addressing the user's request",
        agent=toolkit_agent,
    )

    crew = Crew(
        agents=[toolkit_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:
  • You build a simple chat loop and keep a running context
  • Each user turn becomes a Task handled by the same agent
  • Crew executes the task and returns a response

Run the application

python
if __name__ == "__main__":
    main()
What's happening:
  • Standard Python entry point so you can run python crewai_imagekit_io_agent.py

Complete Code

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

python
# file: crewai_imagekit_io_agent.py
from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter  # optional
from composio import Composio
from dotenv import load_dotenv
import os
from crewai.mcp import MCPServerHTTP

load_dotenv()

def main():
    # Initialize Composio and create a Imagekit io session
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    session = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["imagekit_io"],
    )
    url = session.mcp.url

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

    # Create Imagekit io assistant agent
    toolkit_agent = Agent(
        role="Imagekit io Assistant",
        goal="Help users interact with Imagekit io through natural language commands",
        backstory=(
            "You are an expert assistant with access to Imagekit io tools. "
            "You can perform various Imagekit io operations on behalf of the user."
        ),
        mcps=[
            MCPServerHTTP(
                url=url,
                streamable=True,
                cache_tools_list=True,
                headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")},
            ),
        ],
        llm=llm,
        verbose=True,
        max_iter=10,
    )

    print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
    print("Try asking the agent to perform Imagekit io operations.\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"Based on the conversation history:\n{conversation_context}\n\n"
                f"Current user request: {user_input}\n\n"
                f"Please help the user with their Imagekit io related request."
            ),
            expected_output="A helpful response addressing the user's request",
            agent=toolkit_agent,
        )

        crew = Crew(
            agents=[toolkit_agent],
            tasks=[task],
            verbose=False,
        )

        result = crew.kickoff()
        response = str(result)

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

if __name__ == "__main__":
    main()

Conclusion

You now have a CrewAI agent connected to Imagekit io through Composio's Tool Router. The agent can perform Imagekit io 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 Imagekit io MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Imagekit io MCP?

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

Can I manage the permissions and scopes for Imagekit io while using Tool Router?

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

Used by agents from

Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.