CrewAI Enterprise MCP Server
OfficialRelated Servers
Alternatives to CrewAI Enterprise MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityFmaintenanceA lightweight Python-based server designed to run, manage and create CrewAI workflows using the Model Context Protocol for communicating with LLMs and tools like Claude Desktop or Cursor IDE.36-
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables seamless integration between Claude AI and development tools like VSCode, Augment, Vercel, Airtable, and Square.7MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that allows integration with Claude Desktop by creating and managing custom tools that can be executed through the MCP framework.25 npm-
- AlicenseNot gradedqualityDmaintenanceA complete Model Context Protocol server that enables Claude to create, manage, and execute n8n workflows through conversational AI.1MIT
- AlicenseNot gradedqualityDmaintenanceA production-ready Model Context Protocol server that provides comprehensive file system management capabilities for seamless integration with Claude Desktop.1MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server that provides a bridge to Anthropic's Claude CLI. It allows MCP-compliant clients like Claude Desktop or Gemini to start new chat sessions or continue existing ones.262 npmISC
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one starts a new crew task (kickoff_crew) and the other checks the status of an existing task (get_crew_status). There is no overlap or ambiguity between these operations.
Both tools follow a consistent verb_noun pattern (kickoff_crew, get_crew_status) with clear action-oriented verbs and the same noun root. The naming is predictable and follows the same convention throughout.
With only two tools, the server feels severely under-equipped for an 'Enterprise MCP Server' that presumably manages crew tasks. There are likely missing operations like listing crews, updating tasks, or handling errors that would be needed for complete workflow coverage.
The tool surface is significantly incomplete for crew task management. While it covers starting and checking status, there are obvious gaps: no way to list existing crews, update tasks, cancel tasks, or retrieve results beyond status. This will cause agent failures in many scenarios.