CrewAI's tool shed has moved

What it does

This repository once housed the official tool collection for CrewAI agents: pre-built Python utilities for reading files, scraping websites, querying Postgres and MySQL, searching vector stores, and calling external APIs. It also shipped a BaseTool class and a @tool decorator for authoring custom capabilities. A prominent banner now warns that the code is deprecated and active development continues inside the main CrewAI monorepo.

The interesting bit

The MCP bridge is the most unusual feature. MCPServerAdapter consumes external Model Context Protocol servers—via STDIO or SSE—and repackages their tools as native CrewAI instruments. The README candidly admits the integration is narrow: it ignores prompts and resources, and it surfaces only the first text chunk from each tool call.

Key highlights

• Pre-built integrations for file I/O, web scraping (ScrapeWebsiteTool, SeleniumScrapingTool), relational databases (PGSearchTool, MySQLSearchTool), and vector stores (MongoDB, Qdrant, Weaviate)
• Custom tool authoring through BaseTool subclassing or a lightweight @tool decorator
• MCP adapter that maps third-party server tools one-to-one with CrewAI tools
• Explicit security warning that STDIO MCP servers execute local code and that SSE servers can inject malicious input

Caveats

• The repository is officially deprecated; the maintained version now lives at crewAI/tree/main/lib/crewai-tools
• MCP support is limited to tool primitives only—no prompts, no resources—and returns only the first text output
• Marketing language in the README claims stability and performance without offering benchmarks or architecture details

Verdict

Current CrewAI users should treat this repository as a signpost and migrate to the monorepo. Developers researching agent tool patterns may still find the plugin model illustrative, but starting a new project here would be rowing upstream.