MCP Crew AI Server

Created By
adam-patersona year ago
MCP Crew AI Server is a lightweight Python-based server designed to run, manage and create CrewAI workflows.
Overview

What is MCP Crew AI Server?

MCP Crew AI Server is a lightweight Python-based server designed to run, manage, and create CrewAI workflows, leveraging the Model Context Protocol (MCP) to communicate with Large Language Models (LLMs) and tools like Claude Desktop or Cursor IDE.

How to use MCP Crew AI Server?

To use the server, clone the repository, install the required dependencies, and run the server with default or custom configuration files using command line arguments.

Key features of MCP Crew AI Server?

  • Automatic configuration loading from YAML files for agents and tasks.
  • Command line flexibility to specify custom paths for configuration files.
  • Seamless execution of pre-configured workflows through the MCP run_workflow tool.
  • Local development capability in STDIO mode for testing and development.

Use cases of MCP Crew AI Server?

  1. Orchestrating multi-agent workflows for various applications.
  2. Automating tasks in a development environment.
  3. Managing complex workflows involving multiple agents and tasks.

FAQ from MCP Crew AI Server?

  • Can I customize the agents and tasks?

Yes! You can define your agents and tasks in the agents.yml and tasks.yml files respectively.

  • Is there a specific Python version required?

Yes, Python 3.10 or higher is required to run this server.

  • How do I contribute to the project?

Contributions are welcome! You can open issues or submit pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
adam-paterson
Star
0
Language
Python
License
-
Tags

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago
Voyei

6 hours ago