π CrewAI Enterprise MCP Server
RemoteAbout π CrewAI Enterprise MCP Server
An Apify-hosted MCP server that connects clients to the CrewAI Enterprise API for starting crew tasks and checking their status and results. It uses SSE transport and supports Pay Per Event charging.
Key features
- 01Start crew tasks with custom inputs
- 02Check task status and results
- 03Configure server URL and bearer token
- 04SSE transport
- 05Apify Pay Per Event charging
Use cases
- 01Launch a CrewAI Enterprise task from an MCP client
- 02Check progress and results for a crew task
MCP support
Exposes `kickoff_crew` and `get_crew_status` tools to MCP clients over SSE, backed by the CrewAI Enterprise API.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://your-actor.apify.actor/sseclaude mcp add --transport http crewai-enterprise-mcp-actor https://your-actor.apify.actor/sse{"mcpServers":{"crewai-enterprise-mcp-actor":{"type":"http","url":"https://your-actor.apify.actor/sse"}}}Open in Cursor{"servers":{"crewai-enterprise-mcp-actor":{"type":"http","url":"https://your-actor.apify.actor/sse"}}}Open in VS Code{"mcpServers":{"crewai-enterprise-mcp-actor":{"type":"http","url":"https://your-actor.apify.actor/sse"}}}{"mcpServers":{"crewai-enterprise-mcp-actor":{"serverUrl":"https://your-actor.apify.actor/sse"}}}Run commands in a terminal; paste JSON into the clientβs MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEπ CrewAI Enterprise MCP Server
A Model Context Protocol (MCP) server that provides access to CrewAI Enterprise API for AI agent orchestration and task execution, deployed on the Apify platform.
This Actor enables you to:
- Connect to your CrewAI Enterprise server via MCP
- Start crew tasks with custom inputs
- Monitor crew task status and results
- Monetize your server using Apify's Pay Per Event (PPE) model
β¨ Features
- CrewAI Integration: Direct access to CrewAI Enterprise API endpoints
- Built-in charging: Integrated Pay Per Event (PPE) for:
- Server startup
- Tool calls (kickoff_crew, get_crew_status)
- Tool listing
- Easy configuration: Simple setup through Actor input or environment variables
- SSE Transport: Exposes MCP server via Server-Sent Events for real-time communication
π Available Tools
kickoff_crew
Start a new crew task with the provided inputs.
Parameters:
inputs(object): Dictionary containing the query and other input parameters for the crew
Returns: Dictionary containing the crew task response, including the crew ID needed to check status.
get_crew_status
Get the status of a crew task by its ID.
Parameters:
crew_id(string): The ID of the crew task to check
Returns: Dictionary containing the crew task status and results.
π Quick Start
1. Configure the Actor
Set up your CrewAI Enterprise server details either through:
Actor Input (Recommended):
crewaiServerUrl: Your CrewAI Enterprise server URL (e.g.,https://your-crewai-server.com/api)bearerToken: Bearer token for authenticating with the CrewAI Enterprise API
Environment Variables:
MCP_CREWAI_ENTERPRISE_SERVER_URL: CrewAI Enterprise server URLMCP_CREWAI_ENTERPRISE_BEARER_TOKEN: Bearer token for authentication
2. Deploy and Enable Standby Mode
- Deploy the Actor to Apify
- Enable standby mode for the Actor
- Note the Actor's standby URL
3. Connect Using an MCP Client
Add the following configuration to your MCP client:
{
"mcpServers": {
"crewai-enterprise": {
"url": "https://your-actor.apify.actor/sse"
}
}
}
4. Use the Tools
Once connected, you can use the CrewAI tools in your MCP client:
// Start a crew task
const result = await mcpClient.callTool("kickoff_crew", {
inputs: {
query: "Analyze market trends for Q1 2024",
additional_context: "Focus on technology sector"
}
});
// Check crew status
const status = await mcpClient.callTool("get_crew_status", {
crew_id: result.crew_id
});
π° Pricing
This Actor uses the Pay Per Event (PPE) monetization model:
- Server startup: $0.01 per startup
- Tool calls: $0.05 per tool execution (kickoff_crew, get_crew_status)
- Tool listing: $0.001 per list operation
π§ Configuration
Required Configuration
You must provide either through Actor input or environment variables:
- CrewAI Server URL: The endpoint URL of your CrewAI Enterprise server
- Bearer Token: Authentication token for your CrewAI Enterprise API
Optional Configuration
The Actor automatically handles:
- SSE transport setup
- Error handling and retries
- Charging for operations
- Standby mode configuration
π Example Usage
Starting a Crew Task
# Example crew inputs
crew_inputs = {
"task": "Research and analyze competitor pricing strategies",
"context": {
"industry": "SaaS",
"company_size": "startup",
"target_market": "SMB"
},
"agents": ["researcher", "analyst", "writer"]
}
# Start the crew
result = await kickoff_crew(crew_inputs)
crew_id = result["crew_id"]
Monitoring Task Progress
# Check status periodically
status = await get_crew_status(crew_id)
if status["status"] == "completed":
print("Task completed!")
print("Results:", status["results"])
elif status["status"] == "running":
print("Task still running...")
print("Progress:", status.get("progress", "Unknown"))
else:
print("Task status:", status["status"])
π Related Resources
- CrewAI Enterprise Documentation
- Model Context Protocol Documentation
- Apify MCP Documentation
- What is Anthropic's Model Context Protocol?
π Deployment
Using Apify CLI
- Install Apify CLI:
npm install -g apify-cli - Login:
apify login - Deploy:
apify push
Using Git Integration
- Connect your Git repository to Apify
- Push changes to trigger automatic deployment
- Configure environment variables in Apify Console
π‘οΈ Security
- Bearer tokens are handled securely through Apify's secret management
- All API communications use HTTPS
- The Actor runs in an isolated container environment
- No sensitive data is logged or stored
π Support
For issues related to:
- CrewAI Enterprise: Contact CrewAI support
- Apify Platform: Check Apify documentation or Discord community
- MCP Protocol: See MCP documentation
π License
This Actor is provided as-is under standard Apify terms. CrewAI Enterprise is a separate service with its own licensing terms.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.