Skip to main content
Glama
crewAIInc

CrewAI Enterprise MCP Server

Official
by crewAIInc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
kickoff_crewC

Start a new crew task

Args:
    inputs: Dictionary containing the query and other input parameters

Returns:
    Dictionary containing the crew task response. The response will contain the crew id which needs to be returned to check the status of the crew.
get_crew_statusC

Get the status of a crew task

Args:
    crew_id: The ID of the crew task to check

Returns:
    Dictionary containing the crew task status

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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.1/5.0

Scored across 2 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness2/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources