# How to integrate Firmao MCP with CrewAI ```json { "title": "How to integrate Firmao MCP with CrewAI", "toolkit": "Firmao", "toolkit_slug": "firmao", "framework": "CrewAI", "framework_slug": "crew-ai", "url": "https://composio.dev/toolkits/firmao/framework/crew-ai", "markdown_url": "https://composio.dev/toolkits/firmao/framework/crew-ai.md", "updated_at": "2026-05-12T10:11:45.171Z" } ``` ## Introduction This guide walks you through connecting Firmao to CrewAI using the Composio tool router. By the end, you'll have a working Firmao agent that can list all invoices created this month, get details for invoice id 12345, delete a contact named john doe through natural language commands. This guide will help you understand how to give your CrewAI agent real control over a Firmao account through Composio's Firmao MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Firmao with - [OpenAI Agents SDK](https://composio.dev/toolkits/firmao/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/firmao/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/firmao/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/firmao/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/firmao/framework/codex) - [OpenClaw](https://composio.dev/toolkits/firmao/framework/openclaw) - [Hermes](https://composio.dev/toolkits/firmao/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/firmao/framework/cli) - [Google ADK](https://composio.dev/toolkits/firmao/framework/google-adk) - [LangChain](https://composio.dev/toolkits/firmao/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/firmao/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/firmao/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/firmao/framework/llama-index) ## TL;DR Here's what you'll learn: - Get a Composio API key and configure your Firmao connection - Set up CrewAI with an MCP enabled agent - Create a Tool Router session or standalone MCP server for Firmao - Build a conversational loop where your agent can execute Firmao 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 Firmao MCP server, and what's possible with it? The Firmao MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Firmao account. It provides structured and secure access to your business data, so your agent can perform actions like retrieving invoices, managing offers, handling tasks, and updating company settings on your behalf. - Invoice management and automation: Let your agent create new invoices, retrieve detailed invoice data, list all invoices, or delete invoices as needed—all without manual entry. - Offer tracking and updates: Effortlessly get the details of any offer, or have your agent delete offers that are no longer relevant to your business pipeline. - Task and contact handling: Fetch specific task details or manage your contact list, including the ability to remove outdated or incorrect contacts with ease. - Company configuration oversight: List and review your company’s settings or delete obsolete company configurations—helping you keep your business data clean and up to date. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `FIRMAO_CREATE_INVOICE` | Create Invoice | Creates a new sales or purchase invoice in Firmao CRM. This action generates an invoice transaction with line items, customer information, pricing details, and payment terms. It can auto-create customers if needed and supports automatic invoice numbering. | | `FIRMAO_DELETE_COMPANY_SETTING` | Delete Company Setting | Deletes a company setting by its unique identifier. Returns success status and details about the deletion attempt. Use this when you need to permanently remove a specific company setting configuration. | | `FIRMAO_DELETE_CONTACT` | Delete Contact | Soft-deletes a contact in Firmao CRM by marking it as deleted (sets deleted=true). This action sends a PUT request to mark the contact as deleted without permanently removing it from the system. The contact can potentially be restored later through the Firmao interface. Returns a changelog documenting the deletion operation. If the API returns errors (e.g., authentication issues, contact not found, insufficient permissions), the action gracefully returns an empty changelog to maintain usability in restricted environments. Use this when you need to remove a contact from active use in Firmao CRM. | | `FIRMAO_DELETE_INVOICE` | Delete Invoice | Soft-deletes a Firmao invoice by marking it as deleted. This action sends a PUT request to mark the invoice's 'deleted' field as true. The invoice record remains in the system but is marked as deleted. Returns a changelog documenting the deletion operation. If the API returns unexpected response formats, the action normalizes them to the expected schema. | | `FIRMAO_DELETE_OFFER` | Delete Offer | Soft-delete an offer in Firmao by marking it as deleted. The offer record is not permanently removed but is marked with deleted=true, making it inactive in the system. Use this action when you need to remove an offer without permanently destroying the record. The action returns a changelog documenting the deletion operation. | | `FIRMAO_GET_INVOICE` | Get Invoice | Retrieve detailed information about a specific invoice by its ID. Returns comprehensive invoice data including customer details, line items, payment status, pricing information, and metadata. Use this when you need complete invoice details for a known invoice ID. | | `FIRMAO_GET_OFFER` | Get Offer | Retrieve detailed information about a specific offer from Firmao CRM by its unique ID. This action fetches comprehensive offer data including customer details, pricing, line items, payment information, and metadata. Use this when you need to view or analyze a specific offer, display offer details to users, or retrieve offer information for further processing. The action implements robust endpoint fallback logic to handle various Firmao API configurations. Returns an empty result set if the offer is not found or authentication fails. | | `FIRMAO_GET_TASK` | Get Task | Retrieves detailed information about a specific task by its unique ID. Use this action when you need to: - Get full details of a task after obtaining its ID from a list or search - Check the current status, progress, or assignments of a specific task - Access task metadata like creation date, responsible users, or financial information Returns a single task's complete information including status, dates, responsible users, progress percentage, financial data (costs, income), and related entities (customer, contact, project). | | `FIRMAO_LIST_COMPANY_SETTINGS` | List Company Settings | Lists all company settings from Firmao. Company settings are key-value configuration pairs that store custom configurations for companies. Use this action to retrieve settings, with optional filtering by company ID and pagination support. Returns an empty list if no settings exist or the endpoint is not available in the current Firmao deployment. | | `FIRMAO_LIST_INVOICES` | List Invoices | Tool to list invoices. Use when retrieving a list of invoices with optional pagination and filtering. | | `FIRMAO_LIST_TASKS` | List Tasks | Retrieves a paginated list of tasks from Firmao. Returns task details including status, priority, dates, responsible users, tags, and financial data. Supports sorting, filtering by various fields, and configurable detail levels (MINIMAL, MEDIUM, FULL). | | `FIRMAO_UPDATE_CONTACT` | Update Contact in Firmao | Updates an existing contact in Firmao CRM by its ID. Use this tool to modify contact information such as name, email, phone, position, or customer association. Only include the fields you want to change - omitted fields will remain unchanged. Returns a changelog of the modifications made. Prerequisites: - The contact ID must exist in your Firmao organization - If updating the customer field, the customer ID must already exist | | `FIRMAO_UPDATE_OFFER` | Update Offer | Updates an existing offer/quote in Firmao by ID. Modifies specified fields while preserving unspecified ones. Returns a changelog detailing what changed. Supports partial updates - only provide fields you want to change. | | `FIRMAO_UPDATE_TASK` | Update Task | Tool to update an existing task. Use when you need to modify one or more fields of a task after confirming its current details. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Firmao MCP server is an implementation of the Model Context Protocol that connects your AI agent to Firmao. It provides structured and secure access so your agent can perform Firmao 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 Firmao 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 Firmao 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 Firmao 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 Firmao **What's happening:** - You create a Firmao only session through Composio - Composio returns an MCP HTTP URL that exposes Firmao tools ```python composio_client = Composio(api_key=COMPOSIO_API_KEY) session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["firmao"]) 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=["firmao"], ) 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 Firmao through Composio's Tool Router. The agent can perform Firmao 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 Firmao MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/firmao/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/firmao/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/firmao/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/firmao/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/firmao/framework/codex) - [OpenClaw](https://composio.dev/toolkits/firmao/framework/openclaw) - [Hermes](https://composio.dev/toolkits/firmao/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/firmao/framework/cli) - [Google ADK](https://composio.dev/toolkits/firmao/framework/google-adk) - [LangChain](https://composio.dev/toolkits/firmao/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/firmao/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/firmao/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/firmao/framework/llama-index) ## Related Toolkits - [Hubspot](https://composio.dev/toolkits/hubspot) - HubSpot is an all-in-one marketing, sales, and customer service platform. It lets teams nurture leads, automate outreach, and track every customer interaction in one place. - [Pipedrive](https://composio.dev/toolkits/pipedrive) - Pipedrive is a sales management platform offering pipeline visualization, lead tracking, and workflow automation. It helps sales teams keep deals moving forward efficiently and never miss a follow-up. - [Salesforce](https://composio.dev/toolkits/salesforce) - Salesforce is a leading CRM platform that helps businesses manage sales, service, and marketing. It centralizes customer data, enabling teams to drive growth and build strong relationships. - [Apollo](https://composio.dev/toolkits/apollo) - Apollo is a CRM and lead generation platform that helps businesses discover contacts and manage sales pipelines. Use it to streamline customer outreach and track your deals from one place. - [Attio](https://composio.dev/toolkits/attio) - Attio is a customizable CRM and workspace for managing your team's relationships and workflows. It helps teams organize contacts, automate tasks, and collaborate more efficiently. - [Acculynx](https://composio.dev/toolkits/acculynx) - AccuLynx is a cloud-based roofing business management software for contractors. It streamlines project tracking, lead management, and document sharing. - [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. - [Affinity](https://composio.dev/toolkits/affinity) - Affinity is a relationship intelligence CRM that helps private capital investors find, manage, and close more deals. It streamlines deal flow and surfaces key connections to help you win opportunities. - [Agencyzoom](https://composio.dev/toolkits/agencyzoom) - AgencyZoom is a sales and performance platform built for P&C insurance agencies. It helps agents boost sales, retain clients, and analyze producer results in one place. - [Bettercontact](https://composio.dev/toolkits/bettercontact) - Bettercontact is a smart contact enrichment tool for finding emails and phone numbers. It helps boost lead generation with automated, waterfall search across multiple sources. - [Blackbaud](https://composio.dev/toolkits/blackbaud) - Blackbaud provides cloud-based software for nonprofits, schools, and healthcare institutions. It streamlines fundraising, donor management, and mission-driven operations. - [Brilliant directories](https://composio.dev/toolkits/brilliant_directories) - Brilliant Directories is an all-in-one platform for building and managing online membership communities and business directories. It streamlines listings, member management, and engagement tools into a single, easy interface. - [Capsule crm](https://composio.dev/toolkits/capsule_crm) - Capsule CRM is a user-friendly CRM platform for managing contacts and sales pipelines. It helps businesses organize relationships and streamline their sales process efficiently. - [Centralstationcrm](https://composio.dev/toolkits/centralstationcrm) - CentralStationCRM is an easy-to-use CRM software focused on collaboration and long-term customer relationships. It helps teams manage contacts, deals, and communications all in one place. - [Clientary](https://composio.dev/toolkits/clientary) - Clientary is a platform for managing clients, invoices, projects, proposals, and more. It streamlines client work and saves you serious admin time. - [Close](https://composio.dev/toolkits/close) - Close is a CRM platform built for sales teams, combining calling, email automation, and predictive dialers. It streamlines sales workflows and boosts productivity with all-in-one communication tools. - [Dropcontact](https://composio.dev/toolkits/dropcontact) - Dropcontact is a B2B email finder and data enrichment service for professionals. It delivers verified email addresses and enriches contact info with up-to-date data. - [Dynamics365](https://composio.dev/toolkits/dynamics365) - Dynamics 365 is Microsoft's platform combining CRM, ERP, and productivity apps. It streamlines sales, marketing, service, and operations in one place. - [Espocrm](https://composio.dev/toolkits/espocrm) - EspoCRM is an open-source web application for managing customer relationships. It helps businesses organize contacts, track leads, and streamline their sales process. - [Fireberry](https://composio.dev/toolkits/fireberry) - Fireberry is a CRM platform that streamlines customer and sales management. It helps businesses organize contacts, automate sales, and integrate with other business tools. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Firmao MCP? With a standalone Firmao MCP server, the agents and LLMs can only access a fixed set of Firmao tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Firmao 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 Firmao tools. ### Can I manage the permissions and scopes for Firmao while using Tool Router? Yes, absolutely. You can configure which Firmao 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 Firmao data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)