CrewAI
Run deployed CrewAI automations and manage CrewAI AMP SaaS control-plane resources.
Integration
- Vendor
- CrewAI
- Category
- other
- Auth
- API_KEY
- Tools
- 8
- Composio slug
crew_ai
Tools
- Get Deployment Logs
Return deployment lifecycle logs for a CrewAI deployment UUID to diagnose build or runtime deployment failures.
- Get Deployment Status
Return the current AMP deployment status for one crew UUID from the SaaS control plane.
- Get Execution Status
Return the current state, progress, result, or error for a deployed-crew execution started with a kickoff ID.
- Get Required Inputs
Return the input names required by the connected deployed CrewAI automation before starting an execution.
- List Crew Deployments
List CrewAI crew deployments visible to the selected SaaS organization and return their identifiers for status, logs, or redeployment.
- Redeploy Crew
Trigger a new deployment of an existing CrewAI automation by UUID; this irreversibly changes the live deployment and may replace its runtime URL or token.
- Resume Crew Execution
Approve or retry a human-in-the-loop task and resume its paused CrewAI execution. Resuming may continue externally effectful work.
- Start Crew Execution
Start one execution of the connected deployed CrewAI automation and return its kickoff ID for status checks. The automation may perform irreversible external actions.
Setup
- Create or open a Switchy Project.
- Open Integrations and connect CrewAI.
- Authorise through api_key. Switchy stores the connection against your org.
- Everyone in the Project can now @-mention the CrewAI tools in chat.
What teammates see: by default, memories from CrewAI are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.