# How to integrate Statuscake MCP with CrewAI ```json { "title": "How to integrate Statuscake MCP with CrewAI", "toolkit": "Statuscake", "toolkit_slug": "statuscake", "framework": "CrewAI", "framework_slug": "crew-ai", "url": "https://composio.dev/toolkits/statuscake/framework/crew-ai", "markdown_url": "https://composio.dev/toolkits/statuscake/framework/crew-ai.md", "updated_at": "2026-05-12T10:27:10.885Z" } ``` ## Introduction This guide walks you through connecting Statuscake to CrewAI using the Composio tool router. By the end, you'll have a working Statuscake agent that can list all uptime monitoring tests for your sites, show details for ssl check on your domain, retrieve all recent pagespeed test results through natural language commands. This guide will help you understand how to give your CrewAI agent real control over a Statuscake account through Composio's Statuscake MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Statuscake with - [OpenAI Agents SDK](https://composio.dev/toolkits/statuscake/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/statuscake/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/statuscake/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/statuscake/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/statuscake/framework/codex) - [OpenClaw](https://composio.dev/toolkits/statuscake/framework/openclaw) - [Hermes](https://composio.dev/toolkits/statuscake/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/statuscake/framework/cli) - [Google ADK](https://composio.dev/toolkits/statuscake/framework/google-adk) - [LangChain](https://composio.dev/toolkits/statuscake/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/statuscake/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/statuscake/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/statuscake/framework/llama-index) ## TL;DR Here's what you'll learn: - Get a Composio API key and configure your Statuscake connection - Set up CrewAI with an MCP enabled agent - Create a Tool Router session or standalone MCP server for Statuscake - Build a conversational loop where your agent can execute Statuscake 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 Statuscake MCP server, and what's possible with it? The Statuscake MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Statuscake account. It provides structured and secure access to your website and application monitoring tools, so your agent can perform actions like listing uptime tests, checking SSL status, retrieving page speed results, and managing contact groups on your behalf. - Comprehensive uptime monitoring: Let your agent list and review all website monitoring tests to ensure your services are online and performing as expected. - SSL certificate management: Retrieve current SSL check details or get a full overview of all SSL tests to monitor certificate health and prevent expirations. - Page speed insights: Access and analyze all PageSpeed test results to identify performance bottlenecks and track improvements over time. - Contact group automation: List, retrieve details for, or delete contact groups to efficiently manage who gets notified about incidents and alerts. - Heartbeat and monitoring location checks: Have your agent fetch heartbeat check statuses and list all available monitoring locations for comprehensive observability and troubleshooting. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `STATUSCAKE_CREATE_CONTACT_GROUP` | Create Contact Group | Tool to create a contact group for alert notifications in StatusCake. Use when you need to set up a new group of notification recipients for monitoring alerts. The group can include email addresses, mobile numbers, integrations, and a webhook URL. At minimum, provide a name; other notification methods are optional. | | `STATUSCAKE_CREATE_HEARTBEAT_TEST` | Create Heartbeat Test | Tool to create a heartbeat check in StatusCake. Use when you need to set up monitoring for services that send periodic pings. A heartbeat check monitors whether your service is sending regular "heartbeat" pings to StatusCake. If the service fails to send a ping within the specified period, StatusCake will alert you through the configured contact groups. This is ideal for monitoring cron jobs, backup processes, or any scheduled tasks that should run at regular intervals. | | `STATUSCAKE_CREATE_PAGESPEED_TEST` | Create PageSpeed Test | Tool to create a new pagespeed check in StatusCake. Use when you need to set up performance monitoring for a website URL with specific check frequency and region. Returns the ID of the newly created test. | | `STATUSCAKE_CREATE_UPTIME_TEST` | Create Uptime Test | Tool to create a new uptime monitoring check in StatusCake. Use when you need to set up monitoring for a website or server. Supports various check types including HTTP, PING, TCP, DNS, and more. Returns the ID of the newly created test. | | `STATUSCAKE_DELETE_CONTACT_GROUP` | Delete Contact Group | Tool to delete a contact group. Use when you need to remove an existing contact group by its ID after confirming its existence. | | `STATUSCAKE_DELETE_HEARTBEAT_TEST` | Delete Heartbeat Test | Permanently deletes a StatusCake heartbeat check. Use this to remove heartbeat monitoring tests that are no longer needed. This operation is irreversible - the heartbeat check and all its historical data will be removed. | | `STATUSCAKE_DELETE_PAGESPEED_TEST` | Delete PageSpeed Test | Permanently deletes a StatusCake PageSpeed test. Use this to remove PageSpeed tests that are no longer needed. This operation is irreversible - the test and all its historical data will be removed. The operation is idempotent - deleting an already-deleted test will still return success. | | `STATUSCAKE_DELETE_SSL_TEST` | Delete SSL Test | Tool to delete an SSL check with the given ID. Use when you need to permanently remove an SSL monitoring test from StatusCake. | | `STATUSCAKE_DELETE_TEST` | Delete Test | Permanently deletes a StatusCake uptime monitoring test. Use this to remove tests that are no longer needed. This operation is irreversible - the test and all its historical data will be removed. The operation is idempotent - deleting an already-deleted test will still return success. | | `STATUSCAKE_GET_ALL_CONTACT_GROUPS` | Get All Contact Groups | Retrieves a paginated list of contact groups for alert notifications. Contact groups define who receives alerts when monitoring tests fail. Returns group names, email addresses, mobile numbers, and integrations. Use this to find existing contact groups before creating new ones or to verify notification recipients. | | `STATUSCAKE_GET_ALL_LOCATIONS` | Get All Monitoring Locations | Retrieves all available uptime monitoring server locations from StatusCake. Use this tool to: - List all monitoring locations to show users available regions - Get region_code values needed when creating or updating uptime checks - Check the current status of monitoring servers - Get IP addresses of monitoring servers for firewall whitelisting Returns ~150 monitoring locations across 30+ countries with their region codes, IP addresses, and availability status. | | `STATUSCAKE_GET_ALL_PAGESPEED_TESTS` | Get All PageSpeed Tests | Tool to retrieve all PageSpeed tests. Use when you need to list existing PageSpeed performance tests in StatusCake after authenticating. | | `STATUSCAKE_GET_ALL_TESTS` | Get All Tests | Tool to retrieve a list of all tests. Use when you need to list your monitoring tests in StatusCake. Results reflect only pre-configured tests; missing results or stale check data do not indicate real-time downtime. | | `STATUSCAKE_GET_CONTACT_GROUP_DETAILS` | Get Contact Group Details | Tool to retrieve details of a specific contact group. Use when you need group metadata by providing its ID. Example: "Get details for contact group 12345". | | `STATUSCAKE_GET_HEARTBEAT_CHECKS` | Get Heartbeat Checks | Tool to list heartbeat checks. Use when you need to retrieve all heartbeat monitoring tests for your account. | | `STATUSCAKE_GET_HEARTBEAT_TEST` | Get Heartbeat Test | Tool to retrieve details of a specific heartbeat check. Use when you need configuration and status of a heartbeat test by providing its ID. Example: "Get heartbeat test details for 7884186". | | `STATUSCAKE_GET_PAGESPEED_TEST` | Get Pagespeed Test | Tool to retrieve details of a specific pagespeed check. Use when you need configuration and status of a pagespeed test by providing its ID. Example: "Get pagespeed test details for 122582". | | `STATUSCAKE_GET_SSL_CHECK_DETAILS` | Get SSL Check Details | Tool to retrieve details of a specific SSL check. Use when you need configuration and status of an SSL test by providing its ID. Example: "Get SSL check details for 123". | | `STATUSCAKE_GET_SSL_CHECKS` | Get SSL Checks | Retrieve a paginated list of SSL checks configured in your StatusCake account. Use this action to: - List all SSL certificate monitors - Check certificate statuses across your monitored domains - Review SSL check configurations and alert settings - Get pagination metadata for navigating large result sets Returns SSL check details including certificate validity dates, cipher information, security scores, and alert configuration. | | `STATUSCAKE_GET_UPTIME_TEST` | Get Uptime Test | Tool to retrieve details of a specific uptime test. Use when you need configuration and status of an uptime check by providing its ID. Example: "Get uptime test details for 7884184". | | `STATUSCAKE_LIST_PAGESPEED_MONITORING_LOCATIONS` | List PageSpeed Monitoring Locations | Retrieves all available PageSpeed monitoring server locations from StatusCake. Use when you need to list regions for PageSpeed test configuration or check server availability. | | `STATUSCAKE_LIST_PAGESPEED_TEST_HISTORY` | List Pagespeed Test History | Tool to retrieve pagespeed check history for a given test ID. Use when you need to analyze historical performance data for a specific pagespeed test. | | `STATUSCAKE_LIST_UPTIME_TEST_ALERTS` | List Uptime Test Alerts | Tool to retrieve a list of alerts for a specific uptime check. Use when you need to view historical alerts and status changes for an uptime test. | | `STATUSCAKE_LIST_UPTIME_TEST_HISTORY` | List Uptime Test History | Tool to retrieve uptime check history for a given test ID. Use when you need to view historical results of uptime monitoring checks. Supports pagination and time-based filtering. | | `STATUSCAKE_LIST_UPTIME_TEST_PERIODS` | List Uptime Test Periods | Tool to retrieve a list of uptime check periods for a specific test. Use when you need to view the historical up/down periods for an uptime check. | | `STATUSCAKE_UPDATE_CONTACT_GROUP` | Update Contact Group | Updates an existing contact group's configuration in StatusCake. Use this tool when you need to modify the name, email addresses, mobile numbers, or integrations of an existing contact group. At least one field besides contact_group_id should be provided to make meaningful changes. The API uses form-urlencoded data format and returns 204 No Content on success, so the action fetches the updated group details after a successful update. | | `STATUSCAKE_UPDATE_HEARTBEAT_TEST` | Update Heartbeat Test | Tool to update an existing heartbeat check with new parameters. Use when you need to modify the name, monitoring period, tags, contact groups, host, or pause status of a heartbeat check. | | `STATUSCAKE_UPDATE_PAGESPEED_TEST` | Update Pagespeed Test | Updates a pagespeed check with the given parameters. Use when you need to modify the configuration of an existing pagespeed monitoring test in StatusCake. At least one field besides test_id should be provided to make meaningful changes. | | `STATUSCAKE_UPDATE_SSL_TEST` | Update SSL Test | Tool to update an SSL check with new configuration parameters. Use when modifying SSL monitoring settings like check frequency, alert preferences, or contact groups. Example: "Update SSL check 123 to check every hour". | | `STATUSCAKE_UPDATE_UPTIME_TEST` | Update Uptime Test | Updates an uptime check with the given parameters. Use when you need to modify configuration of an existing uptime monitoring test such as check frequency, URL, tags, contact groups, or other settings. At least one field besides test_id should be provided to make meaningful changes. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Statuscake MCP server is an implementation of the Model Context Protocol that connects your AI agent to Statuscake. It provides structured and secure access so your agent can perform Statuscake 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 Statuscake 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 Statuscake 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 Statuscake 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 Statuscake **What's happening:** - You create a Statuscake only session through Composio - Composio returns an MCP HTTP URL that exposes Statuscake tools ```python composio_client = Composio(api_key=COMPOSIO_API_KEY) session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["statuscake"]) 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=["statuscake"], ) 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 Statuscake through Composio's Tool Router. The agent can perform Statuscake 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 Statuscake MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/statuscake/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/statuscake/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/statuscake/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/statuscake/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/statuscake/framework/codex) - [OpenClaw](https://composio.dev/toolkits/statuscake/framework/openclaw) - [Hermes](https://composio.dev/toolkits/statuscake/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/statuscake/framework/cli) - [Google ADK](https://composio.dev/toolkits/statuscake/framework/google-adk) - [LangChain](https://composio.dev/toolkits/statuscake/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/statuscake/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/statuscake/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/statuscake/framework/llama-index) ## Related Toolkits - [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. - [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. - [GitHub](https://composio.dev/toolkits/github) - GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place. - [Ably](https://composio.dev/toolkits/ably) - Ably is a real-time messaging platform for live chat and data sync in modern apps. It offers global scale and rock-solid reliability for seamless, instant experiences. - [Abuselpdb](https://composio.dev/toolkits/abuselpdb) - Abuselpdb is a central database for reporting and checking IPs linked to malicious online activity. Use it to quickly identify and report suspicious or abusive IP addresses. - [Alchemy](https://composio.dev/toolkits/alchemy) - Alchemy is a blockchain development platform offering APIs and tools for Ethereum apps. It simplifies building and scaling Web3 projects with robust infrastructure. - [Algolia](https://composio.dev/toolkits/algolia) - Algolia is a hosted search API that powers lightning-fast, relevant search experiences for web and mobile apps. It helps developers deliver instant, typo-tolerant, and scalable search without complex infrastructure. - [Anchor browser](https://composio.dev/toolkits/anchor_browser) - Anchor browser is a developer platform for AI-powered web automation. It transforms complex browser actions into easy API endpoints for streamlined web interaction. - [Apiflash](https://composio.dev/toolkits/apiflash) - Apiflash is a website screenshot API for programmatically capturing web pages. It delivers high-quality screenshots on demand for automation, monitoring, or reporting. - [Apiverve](https://composio.dev/toolkits/apiverve) - Apiverve delivers a suite of powerful APIs that simplify integration for developers. It's designed for reliability and scalability so you can build faster, smarter applications without the integration headache. - [Appcircle](https://composio.dev/toolkits/appcircle) - Appcircle is an enterprise-grade mobile CI/CD platform for building, testing, and publishing mobile apps. It streamlines mobile DevOps so teams ship faster and with more confidence. - [Appdrag](https://composio.dev/toolkits/appdrag) - Appdrag is a cloud platform for building websites, APIs, and databases with drag-and-drop tools and code editing. It accelerates development and iteration by combining hosting, database management, and low-code features in one place. - [Appveyor](https://composio.dev/toolkits/appveyor) - AppVeyor is a cloud-based continuous integration service for building, testing, and deploying applications. It helps developers automate and streamline their software delivery pipelines. - [Backendless](https://composio.dev/toolkits/backendless) - Backendless is a backend-as-a-service platform for mobile and web apps, offering database, file storage, user authentication, and APIs. It helps developers ship scalable applications faster without managing server infrastructure. - [Baserow](https://composio.dev/toolkits/baserow) - Baserow is an open-source no-code database platform for building collaborative data apps. It makes it easy for teams to organize data and automate workflows without writing code. - [Bench](https://composio.dev/toolkits/bench) - Bench is a benchmarking tool for automated performance measurement and analysis. It helps you quickly evaluate, compare, and track your systems or workflows. - [Better stack](https://composio.dev/toolkits/better_stack) - Better Stack is a monitoring, logging, and incident management solution for apps and services. It helps teams ensure application reliability and performance with real-time insights. - [Bitbucket](https://composio.dev/toolkits/bitbucket) - Bitbucket is a Git-based code hosting and collaboration platform for teams. It enables secure repository management and streamlined code reviews. - [Blazemeter](https://composio.dev/toolkits/blazemeter) - Blazemeter is a continuous testing platform for web and mobile app performance. It empowers teams to automate and analyze large-scale tests with ease. - [Blocknative](https://composio.dev/toolkits/blocknative) - Blocknative delivers real-time mempool monitoring and transaction management for public blockchains. Instantly track pending transactions and optimize blockchain interactions with live data. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Statuscake MCP? With a standalone Statuscake MCP server, the agents and LLMs can only access a fixed set of Statuscake tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Statuscake 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 Statuscake tools. ### Can I manage the permissions and scopes for Statuscake while using Tool Router? Yes, absolutely. You can configure which Statuscake 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 Statuscake data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) ยท [Composio docs](https://docs.composio.dev/llms.txt)