# How to integrate Firmao MCP with Autogen ```json { "title": "How to integrate Firmao MCP with Autogen", "toolkit": "Firmao", "toolkit_slug": "firmao", "framework": "AutoGen", "framework_slug": "autogen", "url": "https://composio.dev/toolkits/firmao/framework/autogen", "markdown_url": "https://composio.dev/toolkits/firmao/framework/autogen.md", "updated_at": "2026-05-12T10:11:45.171Z" } ``` ## Introduction This guide walks you through connecting Firmao to AutoGen 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 AutoGen 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) - [CrewAI](https://composio.dev/toolkits/firmao/framework/crew-ai) ## TL;DR Here's what you'll learn: - Get and set up your OpenAI and Composio API keys - Install the required dependencies for Autogen and Composio - Initialize Composio and create a Tool Router session for Firmao - Wire that MCP URL into Autogen using McpWorkbench and StreamableHttpServerParams - Configure an Autogen AssistantAgent that can call Firmao tools - Run a live chat loop where you ask the agent to perform Firmao operations ## What is AutoGen? Autogen is a framework for building multi-agent conversational AI systems from Microsoft. It enables you to create agents that can collaborate, use tools, and maintain complex workflows. Key features include: - Multi-Agent Systems: Build collaborative agent workflows - MCP Workbench: Native support for Model Context Protocol tools - Streaming HTTP: Connect to external services through streamable HTTP - AssistantAgent: Pre-built agent class for tool-using assistants ## 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 agents and assistants directly to Firmao. Instead of manually wiring Firmao APIs, OAuth, and scopes yourself, you get a structured, tool-based interface that an LLM can call safely. 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 You will need: - A Composio API key - An OpenAI API key (used by Autogen's OpenAIChatCompletionClient) - A Firmao account you can connect to Composio - Some basic familiarity with Autogen and Python async ### 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 Install Composio, Autogen extensions, and dotenv. What's happening: - composio connects your agent to Firmao via MCP - autogen-agentchat provides the AssistantAgent class - autogen-ext-openai provides the OpenAI model client - autogen-ext-tools provides MCP workbench support ```bash pip install composio python-dotenv pip install autogen-agentchat autogen-ext-openai autogen-ext-tools ``` ### 3. Set up environment variables Create a .env file in your project folder. What's happening: - COMPOSIO_API_KEY is required to talk to Composio - OPENAI_API_KEY is used by Autogen's OpenAI client - USER_ID is how Composio identifies which user's Firmao connections to use ```bash COMPOSIO_API_KEY=your-composio-api-key OPENAI_API_KEY=your-openai-api-key USER_ID=your-user-identifier@example.com ``` ### 4. Import dependencies and create Tool Router session What's happening: - load_dotenv() reads your .env file - Composio(api_key=...) initializes the SDK - create(...) creates a Tool Router session that exposes Firmao tools - session.mcp.url is the MCP endpoint that Autogen will connect to ```python import asyncio import os from dotenv import load_dotenv from composio import Composio from autogen_agentchat.agents import AssistantAgent from autogen_ext.models.openai import OpenAIChatCompletionClient from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams load_dotenv() async def main(): # Initialize Composio and create a Firmao session composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY")) session = composio.create( user_id=os.getenv("USER_ID"), toolkits=["firmao"] ) url = session.mcp.url ``` ### 5. Configure MCP parameters for Autogen Autogen expects parameters describing how to talk to the MCP server. That is what StreamableHttpServerParams is for. What's happening: - url points to the Tool Router MCP endpoint from Composio - timeout is the HTTP timeout for requests - sse_read_timeout controls how long to wait when streaming responses - terminate_on_close=True cleans up the MCP server process when the workbench is closed ```python # Configure MCP server parameters for Streamable HTTP server_params = StreamableHttpServerParams( url=url, timeout=30.0, sse_read_timeout=300.0, terminate_on_close=True, headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")} ) ``` ### 6. Create the model client and agent What's happening: - OpenAIChatCompletionClient wraps the OpenAI model for Autogen - McpWorkbench connects the agent to the MCP tools - AssistantAgent is configured with the Firmao tools from the workbench ```python # Create model client model_client = OpenAIChatCompletionClient( model="gpt-5", api_key=os.getenv("OPENAI_API_KEY") ) # Use McpWorkbench as context manager async with McpWorkbench(server_params) as workbench: # Create Firmao assistant agent with MCP tools agent = AssistantAgent( name="firmao_assistant", description="An AI assistant that helps with Firmao operations.", model_client=model_client, workbench=workbench, model_client_stream=True, max_tool_iterations=10 ) ``` ### 7. Run the interactive chat loop What's happening: - The script prompts you in a loop with You: - Autogen passes your input to the model, which decides which Firmao tools to call via MCP - agent.run_stream(...) yields streaming messages as the agent thinks and calls tools - Typing exit, quit, or bye ends the loop ```python print("Chat started! Type 'exit' or 'quit' to end the conversation.\n") print("Ask any Firmao related question or task to the agent.\n") # Conversation loop while True: user_input = input("You: ").strip() if user_input.lower() in ["exit", "quit", "bye"]: print("\nGoodbye!") break if not user_input: continue print("\nAgent is thinking...\n") # Run the agent with streaming try: response_text = "" async for message in agent.run_stream(task=user_input): if hasattr(message, "content") and message.content: response_text = message.content # Print the final response if response_text: print(f"Agent: {response_text}\n") else: print("Agent: I encountered an issue processing your request.\n") except Exception as e: print(f"Agent: Sorry, I encountered an error: {str(e)}\n") ``` ## Complete Code ```python import asyncio import os from dotenv import load_dotenv from composio import Composio from autogen_agentchat.agents import AssistantAgent from autogen_ext.models.openai import OpenAIChatCompletionClient from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams load_dotenv() async def main(): # Initialize Composio and create a Firmao session composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY")) session = composio.create( user_id=os.getenv("USER_ID"), toolkits=["firmao"] ) url = session.mcp.url # Configure MCP server parameters for Streamable HTTP server_params = StreamableHttpServerParams( url=url, timeout=30.0, sse_read_timeout=300.0, terminate_on_close=True, headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")} ) # Create model client model_client = OpenAIChatCompletionClient( model="gpt-5", api_key=os.getenv("OPENAI_API_KEY") ) # Use McpWorkbench as context manager async with McpWorkbench(server_params) as workbench: # Create Firmao assistant agent with MCP tools agent = AssistantAgent( name="firmao_assistant", description="An AI assistant that helps with Firmao operations.", model_client=model_client, workbench=workbench, model_client_stream=True, max_tool_iterations=10 ) print("Chat started! Type 'exit' or 'quit' to end the conversation.\n") print("Ask any Firmao related question or task to the agent.\n") # Conversation loop while True: user_input = input("You: ").strip() if user_input.lower() in ['exit', 'quit', 'bye']: print("\nGoodbye!") break if not user_input: continue print("\nAgent is thinking...\n") # Run the agent with streaming try: response_text = "" async for message in agent.run_stream(task=user_input): if hasattr(message, 'content') and message.content: response_text = message.content # Print the final response if response_text: print(f"Agent: {response_text}\n") else: print("Agent: I encountered an issue processing your request.\n") except Exception as e: print(f"Agent: Sorry, I encountered an error: {str(e)}\n") if __name__ == "__main__": asyncio.run(main()) ``` ## Conclusion You now have an Autogen assistant wired into Firmao through Composio's Tool Router and MCP. From here you can: - Add more toolkits to the toolkits list, for example notion or hubspot - Refine the agent description to point it at specific workflows - Wrap this script behind a UI, Slack bot, or internal tool Once the pattern is clear for Firmao, you can reuse the same structure for other MCP-enabled apps with minimal code changes. ## 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) - [CrewAI](https://composio.dev/toolkits/firmao/framework/crew-ai) ## 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 Autogen? Yes, you can. Autogen 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)