# How to integrate Gagelist MCP with CrewAI ```json { "title": "How to integrate Gagelist MCP with CrewAI", "toolkit": "Gagelist", "toolkit_slug": "gagelist", "framework": "CrewAI", "framework_slug": "crew-ai", "url": "https://composio.dev/toolkits/gagelist/framework/crew-ai", "markdown_url": "https://composio.dev/toolkits/gagelist/framework/crew-ai.md", "updated_at": "2026-05-12T10:12:28.664Z" } ``` ## Introduction This guide walks you through connecting Gagelist to CrewAI using the Composio tool router. By the end, you'll have a working Gagelist agent that can add a new calibration record for this gage, generate calibration certificate for equipment id 2345, list all gages due for calibration this month through natural language commands. This guide will help you understand how to give your CrewAI agent real control over a Gagelist account through Composio's Gagelist MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Gagelist with - [OpenAI Agents SDK](https://composio.dev/toolkits/gagelist/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/gagelist/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/gagelist/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/gagelist/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/gagelist/framework/codex) - [OpenClaw](https://composio.dev/toolkits/gagelist/framework/openclaw) - [Hermes](https://composio.dev/toolkits/gagelist/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/gagelist/framework/cli) - [Google ADK](https://composio.dev/toolkits/gagelist/framework/google-adk) - [LangChain](https://composio.dev/toolkits/gagelist/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/gagelist/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/gagelist/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/gagelist/framework/llama-index) ## TL;DR Here's what you'll learn: - Get a Composio API key and configure your Gagelist connection - Set up CrewAI with an MCP enabled agent - Create a Tool Router session or standalone MCP server for Gagelist - Build a conversational loop where your agent can execute Gagelist 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 Gagelist MCP server, and what's possible with it? The Gagelist MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Gagelist account. It provides structured and secure access to your calibration records and asset management workflows, so your agent can perform actions like adding new gages, managing calibration events, generating certificates, and retrieving account information on your behalf. - Seamless calibration record management: Direct your agent to add, update, or delete calibration records, keeping your asset compliance up-to-date with minimal manual effort. - Automated gage and manufacturer tracking: Have the agent add new gages or manufacturers to your Gagelist inventory, or remove outdated entries as your equipment changes. - Instant calibration certificate generation: Let your agent generate official PDF calibration certificates from existing records, streamlining audit and reporting processes. - Account insights and status checks: Quickly retrieve your account settings or overall status, giving you a real-time view into your calibration program's health. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `GAGELIST_ADD_CALIBRATION_RECORD` | Add Calibration Record | Creates a new calibration record in GageList to document equipment calibration results. Use this tool to record calibration activities including test results, dates, technician info, and equipment condition. Can optionally link to an existing gage record via EquipmentRefId, or create a standalone calibration record. Supports detailed test data, attachments, and custom fields. | | `GAGELIST_ADD_GAGE_RECORD` | Add Gage Record | Tool to add a new gage record. Use after gathering all required gage attributes to create a record. | | `GAGELIST_ADD_MANUFACTURER` | Add Manufacturer | Creates a new manufacturer record in the GageList calibration management system. A manufacturer represents the company that produces gages and measurement instruments. Use this action when you need to add a new manufacturer to the system for tracking and managing calibration records for their equipment. Returns the unique identifier of the newly created manufacturer record. | | `GAGELIST_AUTHENTICATE_WITH_GAGELIST` | Authenticate with Gagelist | Tool to obtain a Gagelist API access token. Use when you need to authenticate with Gagelist using client credentials. Returns OAuth2 tokens for subsequent requests. | | `GAGELIST_DELETE_CALIBRATION_RECORD` | Delete Calibration Record | Deletes a calibration record by its ID. This is a destructive operation that permanently removes the record. Verify the record exists before deletion. | | `GAGELIST_DELETE_GAGE_RECORD` | Delete Gage Record | Deletes a gage record by its ID. The record must exist in the system to be deleted successfully. This operation is destructive and cannot be undone. | | `GAGELIST_DELETE_MANUFACTURER` | Delete Manufacturer | Tool to delete a manufacturer by its ID. Use after confirming the manufacturer exists. | | `GAGELIST_GENERATE_CALIBRATION_CERTIFICATE` | Generate Calibration Certificate | Tool to generate a PDF certificate from a calibration record. Use after ensuring record ID and authentication. | | `GAGELIST_GET_ACCOUNT_SETTINGS` | Get Account Settings | Tool to get account settings. Use after successful authentication to retrieve user-specific settings. | | `GAGELIST_GET_ACCOUNT_STATUS` | Get account status | Tool to retrieve account status. Use after authenticating with Gagelist. | | `GAGELIST_GET_ALL_CALIBRATION_RECORDS` | Get all calibration records | Tool to retrieve a paginated list of calibration records. Use after obtaining a valid access token. | | `GAGELIST_GET_ALL_GAGE_RECORDS` | Get All Gage Records | Tool to retrieve a paginated list of gage records. Use after confirming the access token. | | `GAGELIST_GET_ALL_MANUFACTURERS` | Get All Manufacturers | Tool to retrieve a list of all manufacturers. Use after obtaining a valid access token. Returns manufacturer details including ID, name, contact information, and timestamps. | | `GAGELIST_GET_ATTACHMENT` | Get Attachment | Tool to retrieve an attachment by its ID. Use when you need to download file attachments from the system. | | `GAGELIST_GET_CUSTOM_FIELDS` | Get Custom Fields | Tool to retrieve custom field definitions. Use when you need to list all custom fields configured for both gage and calibration items after authentication. | | `GAGELIST_GET_SINGLE_CALIBRATION_RECORD` | Get Single Calibration Record | Tool to retrieve details of a single calibration record. Use when you need a specific record's detailed data. Ensure a valid Bearer token is set. | | `GAGELIST_GET_SINGLE_GAGE_RECORD` | Get Single Gage Record | Retrieves comprehensive details of a single gage/gauge record from GageList by its unique ID. Returns complete gage information including: serial number, control number, manufacturer details, calibration dates and intervals, measurement specifications (range, tolerance, unit of measure), location, responsible user, test templates, and attached files. Use this after obtaining a valid gage ID from GAGELIST_GET_ALL_GAGE_RECORDS or GAGELIST_ADD_GAGE_RECORD. Example: GetSingleGageRecord(id=123) | | `GAGELIST_UPDATE_ACCOUNT_SETTINGS` | Update Account Settings | Tool to update account settings. Use after retrieving current settings to apply user preference changes. | | `GAGELIST_UPDATE_CUSTOM_FIELD_VALUES` | Update Custom Field Values | Tool to update custom field values. Use when you need to set or modify custom field values for a gage or calibration record after authentication. | | `GAGELIST_UPDATE_MANUFACTURER` | Update Manufacturer | Tool to update a manufacturer by its ID. Use after confirming the manufacturer exists. | | `GAGELIST_UPLOAD_ATTACHMENT_TO_GAGE_RECORD` | Upload Attachment To Gage Record | Tool to upload an attachment to a gage record. Use when adding files to an existing gage record. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Gagelist MCP server is an implementation of the Model Context Protocol that connects your AI agent to Gagelist. It provides structured and secure access so your agent can perform Gagelist 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 Gagelist 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 Gagelist 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 Gagelist 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 Gagelist **What's happening:** - You create a Gagelist only session through Composio - Composio returns an MCP HTTP URL that exposes Gagelist tools ```python composio_client = Composio(api_key=COMPOSIO_API_KEY) session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["gagelist"]) 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=["gagelist"], ) 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 Gagelist through Composio's Tool Router. The agent can perform Gagelist 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 Gagelist MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/gagelist/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/gagelist/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/gagelist/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/gagelist/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/gagelist/framework/codex) - [OpenClaw](https://composio.dev/toolkits/gagelist/framework/openclaw) - [Hermes](https://composio.dev/toolkits/gagelist/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/gagelist/framework/cli) - [Google ADK](https://composio.dev/toolkits/gagelist/framework/google-adk) - [LangChain](https://composio.dev/toolkits/gagelist/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/gagelist/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/gagelist/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/gagelist/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. - [Ascora](https://composio.dev/toolkits/ascora) - Ascora is a cloud-based field service management platform for service businesses. It streamlines scheduling, invoicing, and customer operations 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. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Gagelist MCP? With a standalone Gagelist MCP server, the agents and LLMs can only access a fixed set of Gagelist tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Gagelist 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 Gagelist tools. ### Can I manage the permissions and scopes for Gagelist while using Tool Router? Yes, absolutely. You can configure which Gagelist 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 Gagelist data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)