# How to integrate Ascora MCP with CrewAI ```json { "title": "How to integrate Ascora MCP with CrewAI", "toolkit": "Ascora", "toolkit_slug": "ascora", "framework": "CrewAI", "framework_slug": "crew-ai", "url": "https://composio.dev/toolkits/ascora/framework/crew-ai", "markdown_url": "https://composio.dev/toolkits/ascora/framework/crew-ai.md", "updated_at": "2026-05-12T10:01:59.261Z" } ``` ## Introduction This guide walks you through connecting Ascora to CrewAI using the Composio tool router. By the end, you'll have a working Ascora agent that can list all open jobs for today, create a new quotation for customer, delete a customer record by id through natural language commands. This guide will help you understand how to give your CrewAI agent real control over a Ascora account through Composio's Ascora MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Ascora with - [OpenAI Agents SDK](https://composio.dev/toolkits/ascora/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/ascora/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/ascora/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/ascora/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/ascora/framework/codex) - [OpenClaw](https://composio.dev/toolkits/ascora/framework/openclaw) - [Hermes](https://composio.dev/toolkits/ascora/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/ascora/framework/cli) - [Google ADK](https://composio.dev/toolkits/ascora/framework/google-adk) - [LangChain](https://composio.dev/toolkits/ascora/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/ascora/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/ascora/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/ascora/framework/llama-index) ## TL;DR Here's what you'll learn: - Get a Composio API key and configure your Ascora connection - Set up CrewAI with an MCP enabled agent - Create a Tool Router session or standalone MCP server for Ascora - Build a conversational loop where your agent can execute Ascora 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 Ascora MCP server, and what's possible with it? The Ascora MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Ascora account. It provides structured and secure access to your field service operations, so your agent can perform actions like managing customer data, retrieving jobs, and automating quotations on your behalf. - Customer management and retrieval: Let your agent fetch a list of customers or access customer details to support scheduling and communications. - Automated quotation creation: Have your agent quickly generate new quotations for customers, streamlining your sales and service workflow. - Job list retrieval and filtering: Ask your agent to pull and filter job listings, making it easy to keep track of ongoing and upcoming work orders. - Customer record cleanup: Direct your agent to delete customer records safely after confirming their existence, helping you maintain an up-to-date database. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `ASCORA_CREATE_NOTE` | Create Note | Creates a note on an entity (customer, job, quote, etc.) in Ascora. Use this when you need to add comments, updates, or documentation to any entity in the system. Requires a valid entity ID from the Ascora system. | | `ASCORA_CREATE_OR_UPDATE_CONTACT` | Create or Update Contact | Tool to create a new contact or update an existing contact for a customer. Use when you need to add or modify contact information for a specific customer in Ascora. Requires a valid customer ID and accepts optional contact details like name, email, phone numbers, and default contact flag. | | `ASCORA_CREATE_OR_UPDATE_CUSTOMER` | Create or Update Customer | Tool to create a new customer or update an existing customer in Ascora. Use when you need to add a new customer with company name and optional contact details, address information (street and postal), and communication preferences. If the customer already exists, their details will be updated. | | `ASCORA_CREATE_OR_UPDATE_SUPPLIER` | Create or Update Supplier | Tool to create a new supplier or update an existing supplier in Ascora. Use when you need to add a new supplier with contact and address details, or modify an existing supplier's information by providing the supplierId. | | `ASCORA_CREATE_QUOTATION` | Create Quotation | Creates a new quotation/enquiry in Ascora for a customer. Use this tool when you need to submit a quote request with customer details (name, email, contact info), optional address information, work description, and custom fields. Returns a unique entity ID for the created enquiry that can be used to track or reference the quotation. | | `ASCORA_DELETE_CUSTOMER` | Delete Customer | Tool to delete a specific customer by ID. Use when you need to remove a customer after confirming its existence. | | `ASCORA_GET_CONTACT` | Get Contact | Tool to retrieve details of a specific contact by their unique identifier. Use when you need to fetch information about a contact including their name, contact details, address, and customer association. | | `ASCORA_GET_CUSTOMER` | Get Customer | Tool to retrieve details of a specific customer by their unique identifier. Use when you need to fetch information about a single customer including contact details, addresses, and status. | | `ASCORA_GET_CUSTOMERS` | Get Customers | Retrieves all customers from the Ascora system. Returns a list of customer records including contact information (name, email, phone) and address details (street, city, state, postcode, country). This is a read-only operation that requires authentication via API key. Useful for syncing customer data, creating customer lists, or verifying customer information exists in the system. | | `ASCORA_GET_INVENTORY_CATEGORIES` | Get Inventory Categories | Retrieves all inventory categories used to organize supplies and kits in Ascora. Returns a paginated list of categories with their IDs, names, and numeric identifiers. Use this when you need to list available inventory categories or reference category information for organizing inventory items. | | `ASCORA_GET_INVENTORY_KITS` | Get Inventory Kits | Retrieves all inventory kits from Ascora. Returns a paginated list of kit items that bundle multiple supplies together. Use this when you need to list available inventory kits or access kit details for quoting, job planning, or inventory management. | | `ASCORA_GET_INVENTORY_SUPPLIES` | Get Inventory Supplies | Retrieves all inventory supplies with pricing and stock information from Ascora. Returns a paginated list of supply items. Use this when you need to list available inventory supplies or access supply details including pricing and stock levels. | | `ASCORA_GET_JOB` | Get Job | Retrieves details of a specific job by its unique identifier. Returns comprehensive job information including job number, name, status, customer details, dates, and other job-specific data. Use this when you need to fetch detailed information about a particular job in the Ascora system. | | `ASCORA_GET_JOBS` | Get Jobs | Retrieves a paginated list of jobs from Ascora with optional filtering by job type, status, secondary status, and date range. Returns job details including job number, name, status, customer information, and assignment details. Use this when you need to list, search, or monitor jobs in the Ascora system. | | `ASCORA_GET_QUOTE_LABOUR_ROLES` | Get Quote Labour Roles | Retrieves labour roles available for use in quotes from Ascora. Use this when you need to list available labour roles with their hourly rates for quotation purposes. | | `ASCORA_GET_QUOTES` | Get Quotes | Retrieves a paginated list of quotes from Ascora with optional filtering by status, date range, or customer. Returns quote details including quote number, customer information, status, creation date, and total amount. Use this when you need to list, search, or monitor quotes in the Ascora system. | | `ASCORA_GET_QUOTE_STANDARD_SECTIONS` | Get Quote Standard Sections | Retrieves standard sections that can be used in quotes. Returns a list of pre-configured standard sections that can be included in quotations. This is a read-only operation that requires authentication via API key. Use when you need to list available standard sections for quote generation or to verify what sections exist in the system. | | `ASCORA_GET_QUOTE_STANDARD_STAGES` | Get Quote Standard Stages | Retrieves standard stages that can be used in quotes for progress tracking. Use this when you need to list available quote stages, display progress tracking options, or reference standard stages for quote management. Returns all configured standard stages in the Ascora system. | | `ASCORA_GET_SUPPLIER` | Get Supplier | Tool to retrieve details of a specific supplier by ID. Use when you need to fetch supplier information including contact details, address, and business information. | | `ASCORA_GET_SUPPLIER_INVOICES` | Get Supplier Invoices | Retrieves supplier invoices from Ascora with optional pagination. Returns invoice details including invoice number, supplier name, dates, amounts, and status. Use this when you need to list, search, or monitor supplier invoices in the Ascora system. | | `ASCORA_GET_SUPPLIERS` | Get Suppliers | Retrieves a list of suppliers from the Ascora system. Returns supplier details including name, contact information (email, phone), address details, ABN, and activity status. Use this when you need to list or search for suppliers in the Ascora system. | | `ASCORA_SEARCH_JOBS` | Search Jobs | Search for jobs by various criteria including job number, customer, or address. Use this when you need to find specific jobs based on identifiers or search terms rather than filtering by status or type. | | `ASCORA_UPLOAD_ATTACHMENT` | Upload Attachment | Tool to upload an attachment to an entity (quote, job, customer, etc.) in Ascora. Use when you need to attach files like documents, images, or plans to existing entities in the system. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Ascora MCP server is an implementation of the Model Context Protocol that connects your AI agent to Ascora. It provides structured and secure access so your agent can perform Ascora 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 Ascora 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 Ascora 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 Ascora 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 Ascora **What's happening:** - You create a Ascora only session through Composio - Composio returns an MCP HTTP URL that exposes Ascora tools ```python composio_client = Composio(api_key=COMPOSIO_API_KEY) session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["ascora"]) 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=["ascora"], ) 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 Ascora through Composio's Tool Router. The agent can perform Ascora 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 Ascora MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/ascora/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/ascora/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/ascora/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/ascora/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/ascora/framework/codex) - [OpenClaw](https://composio.dev/toolkits/ascora/framework/openclaw) - [Hermes](https://composio.dev/toolkits/ascora/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/ascora/framework/cli) - [Google ADK](https://composio.dev/toolkits/ascora/framework/google-adk) - [LangChain](https://composio.dev/toolkits/ascora/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/ascora/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/ascora/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/ascora/framework/llama-index) ## Related Toolkits - [Google Sheets](https://composio.dev/toolkits/googlesheets) - Google Sheets is a cloud-based spreadsheet tool for real-time collaboration and data analysis. It lets teams work together from anywhere, updating information instantly. - [Notion](https://composio.dev/toolkits/notion) - Notion is a collaborative workspace for notes, docs, wikis, and tasks. It streamlines team knowledge, project tracking, and workflow customization in one place. - [Airtable](https://composio.dev/toolkits/airtable) - Airtable combines the flexibility of spreadsheets with the power of a database for easy project and data management. Teams use Airtable to organize, track, and collaborate with custom views and automations. - [Asana](https://composio.dev/toolkits/asana) - Asana is a collaborative work management platform for teams to organize and track projects. It streamlines teamwork, boosts productivity, and keeps everyone aligned on goals. - [Google Tasks](https://composio.dev/toolkits/googletasks) - Google Tasks is a to-do list and task management tool integrated into Gmail and Google Calendar. It helps you organize, track, and complete tasks across your Google ecosystem. - [Linear](https://composio.dev/toolkits/linear) - Linear is a modern issue tracking and project planning tool for fast-moving teams. It helps streamline workflows, organize projects, and boost productivity. - [Jira](https://composio.dev/toolkits/jira) - Jira is Atlassian’s platform for bug tracking, issue tracking, and agile project management. It helps teams organize work, prioritize tasks, and deliver projects efficiently. - [Clickup](https://composio.dev/toolkits/clickup) - ClickUp is an all-in-one productivity platform for managing tasks, docs, goals, and team collaboration. It streamlines project workflows so teams can work smarter and stay organized in one place. - [Monday](https://composio.dev/toolkits/monday) - Monday.com is a customizable work management platform for project planning and collaboration. It helps teams organize tasks, automate workflows, and track progress in real time. - [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. - [Agiled](https://composio.dev/toolkits/agiled) - Agiled is an all-in-one business management platform for CRM, projects, and finance. It helps you streamline workflows, consolidate client data, and manage business processes in one place. - [Basecamp](https://composio.dev/toolkits/basecamp) - Basecamp is a project management and team collaboration tool by 37signals. It helps teams organize tasks, share files, and communicate efficiently in one place. - [Beeminder](https://composio.dev/toolkits/beeminder) - Beeminder is an online goal-tracking platform that uses monetary pledges to keep you motivated. Stay accountable and hit your targets with real financial incentives. - [Boxhero](https://composio.dev/toolkits/boxhero) - Boxhero is a cloud-based inventory management platform for SMBs, offering real-time updates, barcode scanning, and team collaboration. It helps businesses streamline stock tracking and analytics for smarter inventory decisions. - [Breathe HR](https://composio.dev/toolkits/breathehr) - Breathe HR is cloud-based HR software for SMEs to manage employee data, absences, and performance. It simplifies HR admin, making it easy to keep employee records accurate and up to date. - [Breeze](https://composio.dev/toolkits/breeze) - Breeze is a project management platform designed to help teams plan, track, and collaborate on projects. It streamlines workflows and keeps everyone on the same page. - [Bugherd](https://composio.dev/toolkits/bugherd) - Bugherd is a visual feedback and bug tracking tool for websites. It helps teams and clients report website issues directly on live sites for faster fixes. - [Canny](https://composio.dev/toolkits/canny) - Canny is a platform for managing customer feedback and feature requests. It helps teams prioritize product decisions based on real user insights. - [Chmeetings](https://composio.dev/toolkits/chmeetings) - Chmeetings is a church management platform for events, members, donations, and volunteers. It streamlines church operations and improves community engagement. - [ClickSend](https://composio.dev/toolkits/clicksend) - ClickSend is a cloud-based SMS and email marketing platform for businesses. It streamlines communication by enabling quick message delivery and contact management. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Ascora MCP? With a standalone Ascora MCP server, the agents and LLMs can only access a fixed set of Ascora tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Ascora 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 Ascora tools. ### Can I manage the permissions and scopes for Ascora while using Tool Router? Yes, absolutely. You can configure which Ascora 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 Ascora data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)