Skip to main content
Glama
ssolis-ti

CrewAI MCP Orchestrator

by ssolis-ti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to CrewAI MCP Orchestrator

No user-submitted related servers found.

    Related Servers

    • all-agents-mcp

      Dokkabei97
      A
      license
      B
      quality
      F
      maintenance
      Enables orchestrating multiple AI CLI agents (Claude Code, Codex, Gemini CLI, Copilot CLI) through a unified MCP interface for task delegation, cross-agent comparison, and specialized tools like code review and debugging.
      14
      4 npm
      14
      MIT

    • Code-MCP

      millsydotdev
      F
      license
      B
      quality
      Not graded
      maintenance
      Turns AI assistants into full-stack software engineers with 36 tools for cognitive reasoning, code validation, project scaffolding, and AI/IDE configuration generation across 130+ programming languages, databases, and frameworks.
      35
      8 npm
      -

    • ML Lab MCP

      PushPullCommitPush
      A
      license
      Not graded
      quality
      D
      maintenance
      Transforms AI assistants into a full ML engineering environment for training and fine-tuning models across multiple backends (local GPU, Mistral, Together AI, OpenAI) and cloud providers (Lambda Labs, RunPod, SSH-accessible VPS), with dataset management, experiment tracking, cost estimation, and deployment to Ollama/Open WebUI.
      3
      PolyForm Noncommercial 1.0.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes. Potential confusion between crewai_kickoff (for crews) and crewai_flow_run (for flows) is mitigated by naming. Two tools lack descriptions, which could cause ambiguity, but names are descriptive enough.

    Naming Consistency5/5

    All tools follow a consistent 'crewai_verb_noun' pattern in snake_case, e.g., create_project, define_agent, flow_run. No mixing of conventions, making it predictable for an agent.

    Tool Count5/5

    14 tools is well within the ideal range for a server covering project creation, component definition, running, testing, training, memory management, and debugging. Each tool serves a distinct purpose.

    Completeness4/5

    Covers core lifecycle: create, define, run, test, train, and debug. Missing delete or rename operations for projects or components, but the surface is comprehensive enough for typical workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources