# How to integrate Identitycheck MCP with CrewAI ```json { "title": "How to integrate Identitycheck MCP with CrewAI", "toolkit": "Identitycheck", "toolkit_slug": "identitycheck", "framework": "CrewAI", "framework_slug": "crew-ai", "url": "https://composio.dev/toolkits/identitycheck/framework/crew-ai", "markdown_url": "https://composio.dev/toolkits/identitycheck/framework/crew-ai.md", "updated_at": "2026-05-12T10:15:38.342Z" } ``` ## Introduction This guide walks you through connecting Identitycheck to CrewAI using the Composio tool router. By the end, you'll have a working Identitycheck agent that can check onboarding status for a specific user, list all successful onboardings from last week, fetch document content for a given onboarding through natural language commands. This guide will help you understand how to give your CrewAI agent real control over a Identitycheck account through Composio's Identitycheck MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Identitycheck with - [OpenAI Agents SDK](https://composio.dev/toolkits/identitycheck/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/identitycheck/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/identitycheck/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/identitycheck/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/identitycheck/framework/codex) - [OpenClaw](https://composio.dev/toolkits/identitycheck/framework/openclaw) - [Hermes](https://composio.dev/toolkits/identitycheck/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/identitycheck/framework/cli) - [Google ADK](https://composio.dev/toolkits/identitycheck/framework/google-adk) - [LangChain](https://composio.dev/toolkits/identitycheck/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/identitycheck/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/identitycheck/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/identitycheck/framework/llama-index) ## TL;DR Here's what you'll learn: - Get a Composio API key and configure your Identitycheck connection - Set up CrewAI with an MCP enabled agent - Create a Tool Router session or standalone MCP server for Identitycheck - Build a conversational loop where your agent can execute Identitycheck 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 Identitycheck MCP server, and what's possible with it? The Identitycheck MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Identitycheck account. It provides structured and secure access to your verification workflows, so your agent can perform actions like checking onboarding status, fetching document content, managing notification endpoints, and retrieving configurations on your behalf. - Instant onboarding status checks: Your agent can retrieve and monitor the progress or result of any onboarding process, keeping you updated in real time. - Document content retrieval: Effortlessly fetch base64-encoded document content tied to a specific onboarding and document code for further analysis or archiving. - Comprehensive configuration management: List, fetch, or delete identity verification configurations, giving you full control over your Identitycheck setup without manual dashboard work. - Notification endpoint oversight: List, fetch, or remove notification endpoints to customize how and where you receive verification event updates. - API health monitoring: Quickly verify API availability before performing operations, ensuring reliability and uptime for your verification workflows. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `IDENTITYCHECK_CHECK_API_HEALTH` | Check API Health | Performs an API health check to verify endpoint availability and responsiveness. This tool sends an HTTP request to a specified endpoint and interprets a 200 OK response as indicating the API is UP. It handles both JSON and non-JSON responses (including HTML). Use this before other operations to confirm the API is reachable. | | `IDENTITYCHECK_DELETE_CONFIGURATION` | Delete configuration | Tool to delete an existing configuration. Use when you need to remove a configuration by its unique code. | | `IDENTITYCHECK_DELETE_NOTIFICATION_ENDPOINT` | Delete Notification Endpoint | Tool to delete a notification endpoint by its unique code. This operation is idempotent - it will succeed whether the endpoint exists or has already been deleted. Use when you need to remove a callback endpoint that receives webhook notifications for identity verification events. | | `IDENTITYCHECK_FETCH_ALL_CONFIGURATIONS` | Fetch All Configurations | Tool to fetch all existing configurations. Use when you need to list all customer configurations after authentication. | | `IDENTITYCHECK_FETCH_ALL_NOTIFICATION_ENDPOINTS` | Fetch all notification endpoints | Fetches all configured notification endpoints (webhooks) for the IdentityCheck SDK. Use this to list all callback URLs that receive onboarding event notifications (START_ONBOARDING, END_ONBOARDING). | | `IDENTITYCHECK_FETCH_CONFIGURATION` | Fetch Configuration | Fetch a specific identity verification configuration by its code. Use this action when you need to: - Retrieve theme customizations (logo, colors, button styles) for a configuration - Get custom wordings/translations defined for different languages - Review configuration options like link validity, email sender name, or ID capture settings - Verify that a configuration exists before using it in an onboarding flow The configuration code is the unique identifier assigned when the configuration was created. | | `IDENTITYCHECK_FETCH_NOTIFICATION_ENDPOINT` | Fetch Notification Endpoint | Tool to fetch a notification endpoint by its code. Use when you need the current configuration of a specific callback endpoint. | | `IDENTITYCHECK_FETCH_ONBOARDINGS` | Fetch Onboardings | Retrieves identity verification onboarding sessions with comprehensive filtering and pagination. An onboarding represents a customer's identity verification journey, tracking their progress from link creation through document capture and verification completion. Each onboarding has a unique link sent via email/phone/none, and transitions through states: CREATED → CLICKED → CAPTURE_ONGOING → SUCCESS/ERROR/EXPIRED. Use this to: - Monitor verification sessions by status, date range, or customer identifiers - Track onboarding completion rates and error patterns - Retrieve specific onboardings by UID or business-specific identifiers - Analyze notification delivery methods and their effectiveness Returns paginated results with statistics (total results, distinct users, captures per document). All filter parameters are optional; omit them to retrieve all onboardings. Example: Find all failed verifications due to network errors in January 2024 | | `IDENTITYCHECK_GET_DOCUMENT_CONTENT` | Get Document Content | Tool to retrieve base64-encoded document content. Use when you have an onboarding UID and document code. | | `IDENTITYCHECK_RETRIEVE_ONBOARDING_STATUS` | Retrieve Onboarding Status | Retrieve the current status and results of an identity verification onboarding session. Use this tool to check the progress of an onboarding (CREATED, CLICKED, CAPTURE_ONGOING) or get final results (SUCCESS, ERROR, EXPIRED). Returns detailed analysis results, error causes, and CIS export data when available. | | `IDENTITYCHECK_UPDATE_CONFIGURATION` | Update Configuration | Tool to update an existing configuration. Use when you need to modify properties of a configuration identified by code. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Identitycheck MCP server is an implementation of the Model Context Protocol that connects your AI agent to Identitycheck. It provides structured and secure access so your agent can perform Identitycheck 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 Identitycheck 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 Identitycheck 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 Identitycheck 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 Identitycheck **What's happening:** - You create a Identitycheck only session through Composio - Composio returns an MCP HTTP URL that exposes Identitycheck tools ```python composio_client = Composio(api_key=COMPOSIO_API_KEY) session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["identitycheck"]) 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=["identitycheck"], ) 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 Identitycheck through Composio's Tool Router. The agent can perform Identitycheck 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 Identitycheck MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/identitycheck/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/identitycheck/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/identitycheck/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/identitycheck/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/identitycheck/framework/codex) - [OpenClaw](https://composio.dev/toolkits/identitycheck/framework/openclaw) - [Hermes](https://composio.dev/toolkits/identitycheck/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/identitycheck/framework/cli) - [Google ADK](https://composio.dev/toolkits/identitycheck/framework/google-adk) - [LangChain](https://composio.dev/toolkits/identitycheck/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/identitycheck/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/identitycheck/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/identitycheck/framework/llama-index) ## Related Toolkits - [Gmail](https://composio.dev/toolkits/gmail) - Gmail is Google's email service with powerful spam protection, search, and G Suite integration. It keeps your inbox organized and makes communication fast and reliable. - [Google Calendar](https://composio.dev/toolkits/googlecalendar) - Google Calendar is a time management service for scheduling meetings, events, and reminders. It streamlines personal and team organization with integrated notifications and sharing options. - [Google Drive](https://composio.dev/toolkits/googledrive) - Google Drive is a cloud storage platform for uploading, sharing, and collaborating on files. It's perfect for keeping your documents accessible and organized across devices. - [Outlook](https://composio.dev/toolkits/outlook) - Outlook is Microsoft's email and calendaring platform for unified communications and scheduling. It helps users stay organized with powerful email, contacts, and calendar management. - [Twitter](https://composio.dev/toolkits/twitter) - Twitter is a social media platform for sharing real-time updates, conversations, and news. Stay connected, informed, and engaged with communities worldwide. - [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. - [Supabase](https://composio.dev/toolkits/supabase) - Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure. - [Composio](https://composio.dev/toolkits/composio) - Composio is an integration platform that connects AI agents with hundreds of business tools. It streamlines authentication and lets you trigger actions across services—no custom code needed. - [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. - [Slack](https://composio.dev/toolkits/slack) - Slack is a channel-based messaging platform for teams and organizations. It helps people collaborate in real time, share files, and connect all their tools 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. - [Google Docs](https://composio.dev/toolkits/googledocs) - Google Docs is a cloud-based word processor that enables document creation and real-time collaboration. Its seamless sharing and version history make team editing and content management a breeze. - [Google Super](https://composio.dev/toolkits/googlesuper) - Google Super is an all-in-one suite combining Gmail, Drive, Calendar, Sheets, Analytics, and more. It gives you a unified platform to manage your digital life, boosting productivity and organization. - [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. - [Codeinterpreter](https://composio.dev/toolkits/codeinterpreter) - Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms. - [Gong](https://composio.dev/toolkits/gong) - Gong is a platform for video meetings, call recording, and team collaboration. It helps teams capture conversations, analyze calls, and turn insights into action. - [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. - [Ashby](https://composio.dev/toolkits/ashby) - Ashby is an applicant tracking system that handles job postings, candidate management, and hiring analytics. - [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. - [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. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Identitycheck MCP? With a standalone Identitycheck MCP server, the agents and LLMs can only access a fixed set of Identitycheck tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Identitycheck 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 Identitycheck tools. ### Can I manage the permissions and scopes for Identitycheck while using Tool Router? Yes, absolutely. You can configure which Identitycheck 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 Identitycheck data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)