How to integrate Fibery MCP with CrewAI

Trusted by
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Fibery logo
CrewAI logo
divider

Introduction

This guide walks you through connecting Fibery to CrewAI using the Composio tool router. By the end, you'll have a working Fibery agent that can list all open tasks for your team, fetch details for project entity by id, delete file attachment from a task through natural language commands.

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

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

Also integrate Fibery with

TL;DR

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

The Fibery MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Fibery account. It provides structured and secure access to your workspace data, so your agent can perform actions like querying entities, managing custom apps, running GraphQL queries, and organizing files—all with zero manual integration code.

  • Entity query and retrieval: Instantly fetch detailed information or lists of entities based on type, filters, and fields, making it easy to surface project or task data as needed.
  • Custom app and endpoint management: Let your agent list, inspect, or delete custom apps and endpoints, streamlining workspace configuration and app lifecycle management.
  • Flexible data manipulation with GraphQL: Execute custom GraphQL queries and mutations against your Fibery space to fetch, update, or manipulate structured data programmatically.
  • File and resource cleanup: Remove outdated files or entities efficiently, helping keep your workspace organized and clutter-free with automated deletions.
  • Authentication and workspace insights: Validate tokens securely and retrieve workspace or app metadata, ensuring your agent always operates with up-to-date context and permissions.

Supported Tools & Triggers

Tools
Delete Custom App EndpointTool to delete a specific custom app endpoint.
Delete EntityPermanently delete a Fibery entity by its UUID and type.
Delete FileDelete a file from Fibery storage using its secret identifier.
Execute GraphQL QueryExecute GraphQL queries or mutations against a Fibery workspace.
Get App InformationTool to retrieve application information.
Get Custom App EndpointsTool to list custom app endpoints.
Get Custom AppsTool to list all custom apps in the Fibery workspace.
Get FileDownload a file from Fibery by its secret or ID.
Get GraphQL SchemaRetrieves the GraphQL schema for the Fibery workspace using standard GraphQL introspection.
Get User PreferencesTool to retrieve the current user's UI preferences.
Refresh access tokenTool to validate and refresh an access token.
Validate Fibery authentication and get access tokenValidates Fibery API authentication and returns the active access token.
Create EntityTool to create a new Fibery entity.
Count Entities by TypeCount the total number of entities for a given Fibery type (database).
Fetch Datalist OptionsFetches one page of distinct values for a specific field from a Fibery entity type.
Fetch SchemaFetch the complete schema metadata for a Fibery workspace.
Exchange OAuth2 authorization codeExchange an OAuth2 authorization code for access and refresh tokens.
Delete/Revoke Access TokenDelete/revoke an existing Fibery API access token by its ID.
Validate Fibery Workspace CredentialsValidates Fibery workspace credentials by performing a test API query to retrieve the authenticated user's name.
Validate FilterValidates filter definitions before executing data queries.
Update EntityUpdate an existing Fibery entity's fields.
Update User PreferencesTool to update the current user's preferences by using the Commands API.
Upload FileUpload a file to Fibery's file storage.

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

Prerequisites

Before starting, make sure you have:
  • Python 3.9 or higher
  • A Composio account and API key
  • A Fibery 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[mcp] python-dotenv
What's happening:
  • composio connects your agent to Fibery via MCP
  • crewai provides Agent, Task, Crew, and LLM primitives
  • crewai-tools[mcp] 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
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 Fibery MCP URL

Create a Composio Tool Router session for Fibery

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

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

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.

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

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Fibery MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Fibery MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Fibery MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Fibery MCP with Claude Cowork

Codex logo

Codex

Use Fibery MCP with Codex

OpenClaw logo

OpenClaw

Use Fibery MCP with OpenClaw

Hermes logo

Hermes

Use Fibery MCP with Hermes

CLI logo

CLI

Use Fibery MCP with CLI

Google ADK logo

Google ADK

Use Fibery MCP with Google ADK

LangChain logo

LangChain

Use Fibery MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Fibery MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Fibery MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Fibery MCP with LlamaIndex

FAQ

What are the differences in Tool Router MCP and Fibery MCP?

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

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

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

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
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.

Get started for freeGet a demo↗