# How to integrate CrowTerminal MCP with Claude Code

```json
{
  "title": "How to integrate CrowTerminal MCP with Claude Code",
  "toolkit": "CrowTerminal",
  "toolkit_slug": "crowterminal",
  "framework": "Claude Code",
  "framework_slug": "claude-code",
  "url": "https://composio.dev/toolkits/crowterminal/framework/claude-code",
  "markdown_url": "https://composio.dev/toolkits/crowterminal/framework/claude-code.md",
  "updated_at": "2026-06-18T09:22:23.948Z"
}
```

## Introduction

Manage your CrowTerminal directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.
You can do this in two different ways:
- Via [Composio Connect](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_connect&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code) - Direct and easiest approach
- Via [Composio SDK](https://docs.composio.dev/docs?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_sdk) - Programmatic approach with more control

## Also integrate CrowTerminal with

- [OpenAI Agents SDK](https://composio.dev/toolkits/crowterminal/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/crowterminal/framework/claude-agents-sdk)
- [Claude Cowork](https://composio.dev/toolkits/crowterminal/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/crowterminal/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/crowterminal/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/crowterminal/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/crowterminal/framework/cli)
- [Google ADK](https://composio.dev/toolkits/crowterminal/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/crowterminal/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/crowterminal/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/crowterminal/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/crowterminal/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/crowterminal/framework/crew-ai)

## TL;DR

- Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
- Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
- Handling Large tool responses out of LLM context to minimize context rot.
- Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

## Connect CrowTerminal to Claude Code

### Connecting CrowTerminal to Claude Code using Composio
1. Add the Composio MCP to Claude

```bash
claude mcp add --scope user --transport http composio https://connect.composio.dev/mcp
```

## What is Claude Code?

Claude Code is Anthropic's command line developer tool that lets you use Claude directly inside your terminal. Instead of switching between your editor, browser, and chat, you can stay in your project folder and ask Claude to help you build, debug, refactor, and understand code right where you're working.
Key features include:
- Terminal-Native Experience: Work with Claude directly in your command line without switching contexts
- MCP Support: Built-in support for Model Context Protocol servers to extend Claude's capabilities
- Project Context: Claude understands your project structure and can read, write, and modify files
- Interactive Development: Ask questions, debug code, and get help in real-time while coding
- Multi-Platform: Works on macOS, Linux, WSL, and Windows

## What is the CrowTerminal MCP server, and what's possible with it?

The CrowTerminal MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your CrowTerminal account. It provides structured and secure access so your agent can perform CrowTerminal operations on your behalf.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `CROWTERMINAL_ANALYZE_ENGAGEMENT` | Analyze Agent Engagement | Tool to analyze engagement correlation for every field in your agent's markdown. Use when you need to understand which agent configuration fields drive engagement and get specific recommendations for improvement. Returns similarity to best/worst performing versions and field-by-field analysis. |
| `CROWTERMINAL_COMPARE_MD` | Compare Agent Markdown | Tool to compare your agent's markdown directly with all stored versions. Returns field differences showing which values differ across versions, lists missing fields not present in your current data, and provides version counts. Use when you need to understand how your current agent configuration compares to historical versions. |
| `CROWTERMINAL_CREATE_WEBHOOK` | Create Webhook | Tool to register a new webhook for receiving real-time event notifications from CrowTerminal. Use when you need to set up asynchronous notifications for events like skill updates, data ingestion, or validation blocks. |
| `CROWTERMINAL_DELETE_WEBHOOK` | Delete Webhook | Tool to delete an existing webhook registration. Use when you need to remove a webhook that is no longer needed or should be replaced. |
| `CROWTERMINAL_GET_BYOK_PLATFORM_INTEL` | Get BYOK Platform Intelligence | Tool to get algorithm insights for TikTok, Instagram, and YouTube without client-specific context. Use when you need platform intelligence data for BYOK (Bring Your Own Key) analysis workflows. This endpoint provides raw contextual algorithm data without triggering LLM inference charges. |
| `CROWTERMINAL_GET_CLIENT_MEMORY_CHANGELOG` | Get Client Memory Changelog | Retrieve human-readable change history for a client's memory. Provides a narrative view of how the client's skill data has evolved over time. |
| `CROWTERMINAL_GET_CLIENT_MEMORY_PATTERN` | Get Client Memory Pattern | Tool to track a specific field over time for trend analysis. Use when you need to understand how a particular metric evolved across versions or time periods. |
| `CROWTERMINAL_GET_COMPONENTS_STATUS` | Get Components Status | Tool to get detailed status of each CrowTerminal service component. Returns current health status, latency, and summary statistics for all monitored components (database, cache, APIs, webhooks). Use when checking system health or diagnosing service issues. |
| `CROWTERMINAL_GET_DATA_TYPES` | Get Data Types | Tool to retrieve valid data types for ingestion across platforms. Returns available data types for TikTok, Instagram, and YouTube that can be used for data ingestion operations. |
| `CROWTERMINAL_GET_INCIDENTS` | Get Recent Incidents | Tool to retrieve list of recent incidents from CrowTerminal with duration and affected components. Use when you need to check system status, monitor service health, or investigate recent outages or degradations. |
| `CROWTERMINAL_GET_PLATFORM_INTEL` | Get Platform Intelligence | Tool to retrieve algorithm insights for TikTok, Instagram, and YouTube. Returns platform-wide intelligence about content algorithm behavior and optimization strategies. Use when you need current platform algorithm trends and recommendations. |
| `CROWTERMINAL_GET_SANDBOX_CLIENT` | Get Sandbox Client | Tool to get mock client data for testing in the sandbox environment. Use when you need to test client-related functionality without affecting real data. No authentication required for sandbox endpoints. |
| `CROWTERMINAL_GET_SANDBOX_MEMORY` | Get Sandbox Memory | Tool to retrieve mock memory/skill data for testing purposes. Use when you need to test memory retrieval without affecting real data or requiring authentication. Part of the sandbox testing environment. |
| `CROWTERMINAL_GET_STATUS` | Get Service Status | Retrieve CrowTerminal service status including overall health, component metrics, and uptime data. Use when you need to check the operational status of CrowTerminal services or monitor system health. No authentication required. |
| `CROWTERMINAL_GET_STATUS_HISTORY` | Get Status History | Tool to get 7-day uptime data points ready for visualization and charting. Use when you need historical uptime metrics for monitoring dashboards or status displays. |
| `CROWTERMINAL_GET_UPTIME` | Get Uptime Data | Tool to retrieve historical uptime data for CrowTerminal agents. Use when you need to check system reliability, view uptime percentages for 24h/7d periods, or review recent service incidents. |
| `CROWTERMINAL_INGEST_BULK_DATA` | Bulk Ingest Analytics Data | Tool to bulk ingest up to 50 analytics data points at once to CrowTerminal. Use when you need to efficiently push large amounts of platform analytics data for content creators across social media platforms. Ideal for batch uploads of retention, engagement, views, and other metrics. |
| `CROWTERMINAL_INGEST_DATA` | Ingest Analytics Data | Tool to ingest platform analytics data from TikTok Studio, Instagram Insights, or YouTube Analytics. Use when you need to push retention curves, demographics, traffic sources, or other engagement metrics for analysis. Supports both video-specific and channel-level data ingestion. |
| `CROWTERMINAL_LIST_WEBHOOKS` | List Webhooks | Tool to list all registered webhooks for the authenticated agent. Use when you need to view all webhook subscriptions and their configurations. |
| `CROWTERMINAL_PING_CROWTERMINAL` | Ping CrowTerminal Service | Tool to check CrowTerminal service availability via a simple ping endpoint. Use when you need to verify the service is online and responding. Returns a pong confirmation with a timestamp. |
| `CROWTERMINAL_READ_BULK_MEMORY` | Bulk Read Memory | Tool to read memory for multiple clients at once (up to 50). Use when you need to efficiently retrieve memory data for multiple creators in a single API call. |
| `CROWTERMINAL_REGISTER_AGENT` | Register Agent | Tool to self-register a new agent and obtain an API key. Use when you need to create a new agent identity in CrowTerminal. No authentication required for this endpoint. Rate limited to 5 requests per hour per IP address. |
| `CROWTERMINAL_RUN_SANDBOX_ENGAGEMENT_ANALYSIS` | Sandbox Engagement Analysis | Tool to run mock engagement analysis in the CrowTerminal sandbox environment. Use when you need to test the engagement analysis workflow without affecting real data or when developing and validating agent configurations. |
| `CROWTERMINAL_TEST_WEBHOOK` | Test Webhook | Tool to test a webhook URL by sending a test payload. Use when you need to verify that a webhook endpoint is properly configured and can receive requests. |
| `CROWTERMINAL_UPDATE_WEBHOOK` | Update Webhook | Tool to update an existing webhook configuration in CrowTerminal. Use when you need to modify webhook URL, change event subscriptions, or enable/disable a webhook. |
| `CROWTERMINAL_VALIDATE_PROPOSED_CHANGES` | Validate Proposed Changes | Tool to validate proposed changes against historical data before updating memory. Use when you need to check if proposed changes contradict historical patterns and receive warnings or recommendations. |
| `CROWTERMINAL_VALIDATE_SANDBOX` | Validate Sandbox | Tool to mock validation endpoint for testing in sandbox. Use when you need to test validation logic. Send 'tutorial' in proposedChanges to get a blocked response. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The CrowTerminal MCP server is an implementation of the Model Context Protocol that connects Claude Code (and other AI assistants like Claude and Cursor) directly to your CrowTerminal account. It provides structured and secure access so Claude can perform CrowTerminal operations on your behalf.
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:
- Claude Pro, Max, or API billing enabled Anthropic account
- Composio API Key
- A CrowTerminal account
- Basic knowledge of Python or TypeScript

### 1. Install Claude Code

To install Claude Code, use one of the following methods based on your operating system:
```bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd
```

### 2. Set up Claude Code

Open a terminal, go to your project folder, and start Claude Code:
- Claude Code will open in your terminal
- Follow the prompts to sign in with your Anthropic account
- Complete the authentication flow
- Once authenticated, you can start using Claude Code
```bash
cd your-project-folder
claude
```

### 3. Set up environment variables

Create a .env file in your project root with the following variables:
- COMPOSIO_API_KEY authenticates with Composio (get it from [Composio dashboard](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=api_key&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code))
- USER_ID identifies the user for session management (use any unique identifier)
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
```

### 4. Install Composio library

No description provided.
```python
pip install composio-core python-dotenv
```

```typescript
npm install @composio/core dotenv
```

### 5. Generate Composio MCP URL

No description provided.
```python
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["crowterminal"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http crowterminal-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['crowterminal'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http crowterminal-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);
```

### 6. Run the script and copy the MCP URL

No description provided.
```python
python generate_mcp_url.py
```

```typescript
node --loader ts-node/esm generate_mcp_url.ts
# or if using tsx
tsx generate_mcp_url.ts
```

### 7. Add CrowTerminal MCP to Claude Code

In your terminal, add the MCP server using the command from the previous step. The command format is:
- claude mcp add registers a new MCP server with Claude Code
- --transport http specifies that this is an HTTP-based MCP server
- The server name (crowterminal-composio) is how you'll reference it
- The URL points to your Composio Tool Router session
- --headers includes your Composio API key for authentication
After running the command, close the current Claude Code session and start a new one for the changes to take effect.
```bash
claude mcp add --transport http crowterminal-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude
```

### 8. Verify the installation

Check that your CrowTerminal MCP server is properly configured.
- This command lists all MCP servers registered with Claude Code
- You should see your crowterminal-composio entry in the list
- This confirms that Claude Code can now access CrowTerminal tools
If everything is wired up, you should see your crowterminal-composio entry listed:
```bash
claude mcp list
```

### 9. Authenticate CrowTerminal

The first time you try to use CrowTerminal tools, you'll be prompted to authenticate.
- Claude Code will detect that you need to authenticate with CrowTerminal
- It will show you an authentication link
- Open the link in your browser (or copy/paste it)
- Complete the CrowTerminal authorization flow
- Return to the terminal and start using CrowTerminal through Claude Code
Once authenticated, you can ask Claude Code to perform CrowTerminal operations in natural language. For example:
- "Debug failing Docker build command"
- "Automate repeated Git cleanup commands"
- "Recall yesterday's terminal troubleshooting notes"

## Complete Code

```python
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["crowterminal"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http crowterminal-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['crowterminal'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http crowterminal-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);
```

## Conclusion

You've successfully integrated CrowTerminal with Claude Code using Composio's MCP server. Now you can interact with CrowTerminal directly from your terminal using natural language commands.
Key features of this setup:
- Terminal-native experience without switching contexts
- Natural language commands for CrowTerminal operations
- Secure authentication through Composio's managed MCP
- Tool Router for dynamic tool discovery and execution
Next steps:
- Try asking Claude Code to perform various CrowTerminal operations
- Add more toolkits to your Tool Router session for multi-app workflows
- Integrate this setup into your development workflow for increased productivity
You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

## How to build CrowTerminal MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/crowterminal/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/crowterminal/framework/claude-agents-sdk)
- [Claude Cowork](https://composio.dev/toolkits/crowterminal/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/crowterminal/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/crowterminal/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/crowterminal/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/crowterminal/framework/cli)
- [Google ADK](https://composio.dev/toolkits/crowterminal/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/crowterminal/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/crowterminal/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/crowterminal/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/crowterminal/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/crowterminal/framework/crew-ai)

## 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.
- [1password](https://composio.dev/toolkits/_1password) - 1Password is a password manager and digital vault for storing logins, secrets, notes, and secure documents. It helps individuals and teams protect credentials, share access safely, and reduce password risk.
- [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.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and CrowTerminal MCP?

With a standalone CrowTerminal MCP server, the agents and LLMs can only access a fixed set of CrowTerminal tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from CrowTerminal and many other apps based on the task at hand, all through a single MCP endpoint.

### Can I use Tool Router MCP with Claude Code?

Yes, you can. Claude Code 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 CrowTerminal tools.

### Can I manage the permissions and scopes for CrowTerminal while using Tool Router?

Yes, absolutely. You can configure which CrowTerminal 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 CrowTerminal data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)