CrewAI MCP Server

Created By
rafaelcc14ga year ago
MCP 서버로 CrewAI와 Claude를 연결하는 통합 서비스
Overview

what is CrewAI MCP Server?

CrewAI MCP Server is an integration service that connects CrewAI with Claude, enabling seamless communication and task management.

how to use CrewAI MCP Server?

To use the CrewAI MCP Server, install it via pip or clone the GitHub repository. Configure the claude_desktop_config.json file to integrate with Claude Desktop.

key features of CrewAI MCP Server?

  • Creation and management of CrewAI agents, tasks, and crews.
  • Support for bidirectional communication between Claude and CrewAI.
  • Document analysis and insight generation.
  • Execution of complex multi-agent workflows.

use cases of CrewAI MCP Server?

  1. Managing tasks and agents in a collaborative environment.
  2. Analyzing documents for insights in real-time.
  3. Orchestrating multi-agent workflows for complex projects.

FAQ from CrewAI MCP Server?

  • What programming language is CrewAI MCP Server written in?

The CrewAI MCP Server is written in Python.

  • Is there a license for CrewAI MCP Server?

Yes, it is licensed under the MIT License.

  • How can I contribute to the project?

You can contribute by submitting issues or pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
rafaelcc14g
Star
0
Language
-
License
-

Recommend Servers

View All
Payai X402 Tools

6 hours 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.

a day ago