# How to integrate Flowiseai MCP with CrewAI ```json { "title": "How to integrate Flowiseai MCP with CrewAI", "toolkit": "Flowiseai", "toolkit_slug": "flowiseai", "framework": "CrewAI", "framework_slug": "crew-ai", "url": "https://composio.dev/toolkits/flowiseai/framework/crew-ai", "markdown_url": "https://composio.dev/toolkits/flowiseai/framework/crew-ai.md", "updated_at": "2026-05-12T10:11:53.393Z" } ``` ## Introduction This guide walks you through connecting Flowiseai to CrewAI using the Composio tool router. By the end, you'll have a working Flowiseai agent that can list all chatflows available in your account, clone an existing chatflow for testing, delete chat messages from a specific chatflow through natural language commands. This guide will help you understand how to give your CrewAI agent real control over a Flowiseai account through Composio's Flowiseai MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Flowiseai with - [OpenAI Agents SDK](https://composio.dev/toolkits/flowiseai/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/flowiseai/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/flowiseai/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/flowiseai/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/flowiseai/framework/codex) - [OpenClaw](https://composio.dev/toolkits/flowiseai/framework/openclaw) - [Hermes](https://composio.dev/toolkits/flowiseai/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/flowiseai/framework/cli) - [Google ADK](https://composio.dev/toolkits/flowiseai/framework/google-adk) - [LangChain](https://composio.dev/toolkits/flowiseai/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/flowiseai/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/flowiseai/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/flowiseai/framework/llama-index) ## TL;DR Here's what you'll learn: - Get a Composio API key and configure your Flowiseai connection - Set up CrewAI with an MCP enabled agent - Create a Tool Router session or standalone MCP server for Flowiseai - Build a conversational loop where your agent can execute Flowiseai 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 Flowiseai MCP server, and what's possible with it? The Flowiseai MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Flowiseai account. It provides structured and secure access to your FlowiseAI workspace, so your agent can manage chatflows, automate workflow creation, clone or delete existing flows, and handle tool configurations on your behalf. - Automated chatflow creation and management: Instantly create new chatflows, fetch details of existing ones, or update and organize your LLM workflows programmatically. - Seamless cloning and exporting of chatflows: Duplicate any chatflow with a single request or export them for backup, sharing, or versioning across projects. - Easy clean-up and deletion: Direct your agent to delete chatflows, remove outdated tools, or erase chat messages to keep your workspace tidy and relevant. - Tool and workflow introspection: Retrieve detailed metadata for specific tools or chatflows so your agent can make informed decisions about which components to use or modify. - Effortless import and migration: Import chatflows from exported JSON files, making it simple to migrate or restore entire AI workflows with minimal manual effort. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `FLOWISEAI_CLONE_CHATFLOW` | Clone Chatflow | Tool to clone an existing chatflow. Use when you need to duplicate a chatflow by its ID. | | `FLOWISEAI_CREATE_CHATFLOW` | Create Chatflow | Creates a new chatflow in FlowiseAI. Chatflows are visual workflows that define AI agent behavior using nodes and edges. Use this to programmatically create single-agent (CHATFLOW) or multi-agent (MULTIAGENT) flows. Only 'name' is required; type defaults to 'CHATFLOW' and flowData defaults to an empty flow structure. | | `FLOWISEAI_CREATE_DOCUMENT_STORE` | Create Document Store | Creates a new document store in FlowiseAI. Document stores are used to manage embeddings and vector data for AI applications. Use this to programmatically create storage for documents that will be embedded and searched. | | `FLOWISEAI_CREATE_LEAD` | Create Lead | Tool to create a new lead in a chatflow. Use when you need to capture lead information from a chat session for follow-up or CRM integration. | | `FLOWISEAI_CREATE_TOOL` | Create Tool | Tool to create a new FlowiseAI tool. Use when you need to create a custom tool with specific name, description, and color. Optionally provide icon URL, JSON schema, or JavaScript function code. | | `FLOWISEAI_CREATE_VARIABLE` | Create Variable | Creates a new variable in FlowiseAI. Variables are used to store configuration values, API keys, and other data that can be referenced across chatflows. Use this to programmatically create string or number variables with optional values. | | `FLOWISEAI_DELETE_CHATFLOW` | Delete Chatflow | Tool to delete a chatflow by its ID. Use after confirming the chatflow ID is correct. | | `FLOWISEAI_DELETE_CHAT_MESSAGES` | Delete Chat Messages | Tool to delete chat messages for a specific chatflow. Use when you need to remove messages based on optional filters. Use after confirming the chatflow ID. | | `FLOWISEAI_DELETE_DOCUMENT_STORE` | Delete Document Store | Tool to delete a specific document store by its ID. Use when you need to permanently remove a document store. This action is destructive and cannot be undone. | | `FLOWISEAI_DELETE_TOOL_BY_ID` | Delete Tool By ID | Permanently deletes a FlowiseAI tool by its unique ID. This action is destructive and cannot be undone. Use FLOWISEAI_LIST_ALL_TOOLS first to verify the correct tool ID before deletion. | | `FLOWISEAI_DELETE_VARIABLE` | Delete Variable | Tool to delete a variable by its unique ID. Use when you need to permanently remove a variable from FlowiseAI. | | `FLOWISEAI_EDIT_DOCUMENT_STORE_FILE_CHUNK` | Edit Document Store File Chunk | Tool to update a specific chunk in a FlowiseAI document store. Use when you need to modify the content or metadata of an existing chunk. At least one of pageContent or metadata must be provided. | | `FLOWISEAI_GET_ALL_CHATFLOWS` | Get All Chatflows | Retrieves all chatflows from the authenticated FlowiseAI account. Use this to list available chatflows, get their IDs for subsequent operations (like update, delete, export), or check chatflow deployment status. Returns an empty list if no chatflows exist. | | `FLOWISEAI_GET_ALL_CHAT_MESSAGE_FEEDBACK` | Get All Chat Message Feedback | Tool to list all chat message feedbacks for a chatflow. Use when you need to view feedback given on messages in a specific chatflow. | | `FLOWISEAI_GET_ALL_LEADS_FOR_CHATFLOW` | Get All Leads for Chatflow | Tool to retrieve all leads for a specific chatflow. Use when you need to see lead information collected from a chatflow's interactions. | | `FLOWISEAI_GET_ALL_UPSERT_HISTORY` | Get All Upsert History | Tool to retrieve all upsert history records for a specific chatflow. Use when you need to view the history of upsert operations. | | `FLOWISEAI_GET_ALL_VARIABLES` | Get All Variables | Tool to retrieve a list of all variables. Use when you need to list all variables available in the FlowiseAI workspace. Returns an empty list if no variables exist. | | `FLOWISEAI_GET_DOCUMENT_STORE_BY_ID` | Get Document Store By ID | Tool to retrieve a document store by its ID. Use when you have a document store ID and need its full details including configuration and status. | | `FLOWISEAI_GET_DOCUMENT_STORE_FILE_CHUNKS` | Get Document Store File Chunks | Tool to get chunks from a specific document loader. Use when you need to retrieve chunked content from a document in a FlowiseAI document store. | | `FLOWISEAI_GET_SINGLE_CHATFLOW` | Get Single Chatflow | Tool to retrieve a chatflow by its ID. Use when you have a chatflow ID and need its full details. | | `FLOWISEAI_GET_TOOL_BY_ID` | Get Tool By ID | Tool to retrieve a specific FlowiseAI tool by its ID. Use when you need detailed metadata of a tool before interacting with it. | | `FLOWISEAI_LIST_ALL_TOOLS` | List All Tools | Tool to retrieve a list of all tools. Use when you need to list every tool available after authentication. | | `FLOWISEAI_LIST_ASSISTANTS` | List Assistants | Tool to retrieve a list of all assistants. Use when you need to list every assistant available in the authenticated FlowiseAI account. | | `FLOWISEAI_LIST_CHAT_MESSAGES` | List Chat Messages | Tool to list chat messages of a chatflow. Use after selecting a chatflow when you need to view its messages. | | `FLOWISEAI_PING_SERVER` | Ping Server | Tool to ping the FlowiseAI server to verify it is running and accessible. Use this to perform a health check before executing other operations or to diagnose connectivity issues. | | `FLOWISEAI_UPDATE_CHATFLOW_DETAILS` | Update Chatflow Details | Tool to update details of an existing chatflow. Use when you have confirmed the chatflow ID and want to modify its fields. | | `FLOWISEAI_UPDATE_DOCUMENT_STORE` | Update Document Store | Tool to update a specific document store. Use when you need to modify properties of an existing document store. | | `FLOWISEAI_UPDATE_TOOL_BY_ID` | Update Tool By ID | Updates a FlowiseAI tool's properties by its ID. Use this to modify tool name, description, color, icon, JSON schema, or JavaScript function code. Requires the tool's UUID from LIST_ALL_TOOLS or GET_TOOL_BY_ID. At least one field must be provided for update. | | `FLOWISEAI_UPDATE_VARIABLE` | Update Variable | Tool to update a variable by its ID. Use when you need to modify a variable's name, value, or type. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Flowiseai MCP server is an implementation of the Model Context Protocol that connects your AI agent to Flowiseai. It provides structured and secure access so your agent can perform Flowiseai 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 Flowiseai 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 Flowiseai 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 Flowiseai 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 Flowiseai **What's happening:** - You create a Flowiseai only session through Composio - Composio returns an MCP HTTP URL that exposes Flowiseai tools ```python composio_client = Composio(api_key=COMPOSIO_API_KEY) session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["flowiseai"]) 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=["flowiseai"], ) 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 Flowiseai through Composio's Tool Router. The agent can perform Flowiseai 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 Flowiseai MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/flowiseai/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/flowiseai/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/flowiseai/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/flowiseai/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/flowiseai/framework/codex) - [OpenClaw](https://composio.dev/toolkits/flowiseai/framework/openclaw) - [Hermes](https://composio.dev/toolkits/flowiseai/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/flowiseai/framework/cli) - [Google ADK](https://composio.dev/toolkits/flowiseai/framework/google-adk) - [LangChain](https://composio.dev/toolkits/flowiseai/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/flowiseai/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/flowiseai/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/flowiseai/framework/llama-index) ## Related Toolkits - [Composio](https://composio.dev/toolkits/composio) - Composio is an integration platform that connects AI agents with hundreds of business tools. It streamlines authentication and lets you trigger actions across services—no custom code needed. - [Composio search](https://composio.dev/toolkits/composio_search) - Composio search is a unified web search toolkit spanning travel, e-commerce, news, financial markets, images, and more. It lets you and your apps tap into up-to-date web data from a single, easy-to-integrate service. - [Perplexityai](https://composio.dev/toolkits/perplexityai) - Perplexityai delivers natural, conversational AI models for generating human-like text. Instantly get context-aware, high-quality responses for chat, search, or complex workflows. - [Browser tool](https://composio.dev/toolkits/browser_tool) - Browser tool is a virtual browser integration that lets AI agents interact with the web programmatically. It enables automated browsing, scraping, and action-taking from any AI workflow. - [Ai ml api](https://composio.dev/toolkits/ai_ml_api) - Ai ml api is a suite of AI/ML models for natural language and image tasks. It provides fast, scalable access to advanced AI capabilities for your apps and workflows. - [Aivoov](https://composio.dev/toolkits/aivoov) - Aivoov is an AI-powered text-to-speech platform offering 1,000+ voices in over 150 languages. Instantly turn written content into natural, human-like audio for any application. - [All images ai](https://composio.dev/toolkits/all_images_ai) - All-Images.ai is an AI-powered image generation and management platform. It helps you create, search, and organize images effortlessly with advanced AI capabilities. - [Anthropic administrator](https://composio.dev/toolkits/anthropic_administrator) - Anthropic administrator is an API for managing Anthropic organizational resources like members, workspaces, and API keys. It helps you automate admin tasks and streamline resource management across your Anthropic organization. - [Api labz](https://composio.dev/toolkits/api_labz) - Api labz is a platform offering a suite of AI-driven APIs and workflow tools. It helps developers automate tasks and build smarter, more efficient applications. - [Apipie ai](https://composio.dev/toolkits/apipie_ai) - Apipie ai is an AI model aggregator offering a single API for accessing top AI models from multiple providers. It helps developers build cost-efficient, latency-optimized AI solutions without juggling multiple integrations. - [Astica ai](https://composio.dev/toolkits/astica_ai) - Astica ai provides APIs for computer vision, NLP, and voice synthesis. Integrate advanced AI features into your app with a single API key. - [Bigml](https://composio.dev/toolkits/bigml) - BigML is a machine learning platform that lets you build, train, and deploy predictive models from your data. Its intuitive interface and robust API make machine learning accessible and efficient. - [Botbaba](https://composio.dev/toolkits/botbaba) - Botbaba is a platform for building, managing, and deploying conversational AI chatbots across messaging channels. It streamlines chatbot automation, making it easier to integrate AI into customer interactions. - [Botpress](https://composio.dev/toolkits/botpress) - Botpress is an open-source platform for building, deploying, and managing chatbots. It helps teams automate conversations and deliver rich, interactive messaging experiences. - [Chatbotkit](https://composio.dev/toolkits/chatbotkit) - Chatbotkit is a platform for building and managing AI-powered chatbots using robust APIs and SDKs. It lets you easily add conversational AI to your apps for better user engagement. - [Cody](https://composio.dev/toolkits/cody) - Cody is an AI assistant built for businesses, trained on your company's knowledge and data. It delivers instant answers and insights, tailored for your team. - [Context7 MCP](https://composio.dev/toolkits/context7_mcp) - Context7 MCP delivers live, version-specific code docs and examples right from the source. It helps developers and AI agents instantly retrieve authoritative programming info—no more out-of-date docs. - [Customgpt](https://composio.dev/toolkits/customgpt) - CustomGPT.ai lets you build and deploy chatbots tailored to your own data and business needs. Get precise and context-aware AI conversations without writing code. - [Datarobot](https://composio.dev/toolkits/datarobot) - Datarobot is a machine learning platform that automates model development, deployment, and monitoring. It empowers organizations to quickly gain predictive insights from large datasets. - [Deepgram](https://composio.dev/toolkits/deepgram) - Deepgram is an AI-powered speech recognition platform for accurate audio transcription and understanding. It enables fast, scalable speech-to-text with advanced audio intelligence features. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Flowiseai MCP? With a standalone Flowiseai MCP server, the agents and LLMs can only access a fixed set of Flowiseai tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Flowiseai 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 Flowiseai tools. ### Can I manage the permissions and scopes for Flowiseai while using Tool Router? Yes, absolutely. You can configure which Flowiseai 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 Flowiseai data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)