MCP.so
ログイン
サーバー

🚀 CrewAI Enterprise MCP Server

@samehjarour

CrewAI Enterprise MCP Server Actor for Apify platform - provides AI agent orchestration via Model Context Protocol

概要

What is 🚀 CrewAI Enterprise MCP Server?

A Model Context Protocol (MCP) server that provides access to the CrewAI Enterprise API for AI agent orchestration and task execution. Deployed on the Apify platform, it enables developers to connect to a CrewAI Enterprise server, start crew tasks with custom inputs, monitor task status and results, and monetize the server using Apify’s Pay Per Event model.

How to use 🚀 CrewAI Enterprise MCP Server?

Configure the Actor with your CrewAI Enterprise server URL and bearer token (via Actor input or environment variables), deploy it on Apify with standby mode enabled, then connect an MCP client to the Actor’s SSE endpoint. Once connected, use the kickoff_crew and get_crew_status tools to start and monitor tasks.

Key features of 🚀 CrewAI Enterprise MCP Server

  • Direct integration with CrewAI Enterprise API endpoints
  • Built-in Pay Per Event monetization (startup, tool calls, listing)
  • Simple configuration via Actor input or environment variables
  • SSE transport for real-time communication
  • Secure credential handling through Apify’s secret management

Use cases of 🚀 CrewAI Enterprise MCP Server

  • Start and monitor AI agent crew tasks from any MCP client
  • Automate complex research and analysis workflows on CrewAI Enterprise
  • Build monetized MCP servers for task orchestration using Apify’s pricing model

FAQ from 🚀 CrewAI Enterprise MCP Server

What configuration is required to use the server?

You must provide a CrewAI Enterprise server URL and a bearer token for authentication, either through Actor input fields or environment variables.

How does pricing work?

The Actor uses Apify’s Pay Per Event model: $0.01 per server startup, $0.05 per tool execution (kickoff_crew or get_crew_status), and $0.001 per tool listing operation.

What transport does the server use?

The server exposes the MCP interface via Server-Sent Events (SSE) for real-time communication.

How are credentials secured?

Bearer tokens are handled securely through Apify’s secret management; all API communications use HTTPS, and no sensitive data is logged or stored.

Are there any runtime dependencies?

The server runs on the Apify platform and requires a running CrewAI Enterprise server with a valid API endpoint and bearer token.

タグ

「その他」の他のコンテンツ