kickoff_crew
Kick off your deployed CrewAI Enterprise crew
Two tools: start a deployed CrewAI Enterprise crew, and check what it did.
LABSCO SUMMARY
There is a temptation to expose a whole orchestration platform over MCP. Two tools is better: the crew's logic lives where it was built and tested, and the caller gets to trigger it and read the outcome. That keeps the failure surface tiny. The gap is documentation — no parameter schemas in the README means the shape of a kickoff call has to be discovered from the live server.
CrewAI's enterprise server, pointed at your own deployment rather than a shared address. The surface is deliberately two tools — this is a remote control for crews you have already built and deployed.
A CrewAI Enterprise deployment and a bearer token for it. Parameter schemas are not documented in the README.
Follow the published steps
USE CASES
Start the deployed crew from whatever conversation or agent needs it.
Poll the run rather than holding a connection open while a crew works.
Listed in project docs. Your client may show a different list.
kickoff_crewKick off your deployed CrewAI Enterprise crew
get_crew_statusInspect status / results of the crew run
BEFORE YOU INSTALL
2 tools named in the project's documentation.
A bearer token (MCP_CREWAI_ENTERPRISE_BEARER_TOKEN) against your own CrewAI Enterprise server URL
INSTALLATION
Get your crew's two values from the CrewAI AMP dashboard at app.crewai.com. Open the deployed crew's detail page: its URL (each crew has its own, in the form https://<YOUR_CREW_NAME>.crewai.com) is MCP_CREWAI_ENTERPRISE_SERVER_URL, and the Bearer Token on its Status tab is MCP_CREWAI_ENTERPRISE_BEARER_TOKEN.
Clone the repository
Install mcp and mcp[cli] locally. Needs uv.
git clone https://github.com/crewAIInc/enterprise-mcp-server.gitIn Claude Desktop, open Settings > Developer Settings and add this server
<YOUR_FILEPATH_CLONED_REPO> is the full path of the enterprise-mcp-server folder; the crew URL and Bearer Token come from the dashboard. The vendor's README splits that file path across two arguments; it is joined here so the command runs.
{
"mcpServers": {
"crewai_enterprise_server": {
"command": "uv",
"args": [
"run",
"--with",
"mcp[cli]",
"mcp",
"run",
"<YOUR_FILEPATH_CLONED_REPO>/crewai_enterprise_server.py"
],
"env": {
"MCP_CREWAI_ENTERPRISE_SERVER_URL": "<YOUR_MCP_CREWAI_ENTERPRISE_SERVER_URL>",
"MCP_CREWAI_ENTERPRISE_BEARER_TOKEN": "<YOUR_MCP_CREWAI_ENTERPRISE_BEARER_TOKEN>"
}
}
}
}