Connect Tools and MCP
Giving crewAI agents tools and MCP servers on crewai 1.15.x: custom BaseTool with args_schema and @tool, which crewai_tools names really exist, tool caching, max_usage_count, ToolFailure, Agent(mcps=[...]) string and MCPServerStdio/HTTP/SSE forms, rewritten MCP tool names, MCPServerAdapter, timeouts, and what works on a hosted deployment. Use when writing or debugging a tool or MCP connection, when you see 'cannot import name BaseTool from crewai_tools', 'You are missing the mcp package', 'MCPConnectionError', 'Operation timed out after 30 seconds', 'reached its usage limit', 'Invalid MCP refe
Install
/plugin marketplace add crewAIInc/skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add crewAIInc/skills --skill connect-tools-and-mcpgit clone --depth 1 https://github.com/crewAIInc/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/connect-tools-and-mcp ~/.claude/skills/connect-tools-and-mcpPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Connect Tools and MCP Servers to CrewAI Agents Give an agent working tools - custom Python, prebuilt `crewai_tools`, or MCP servers - without the 0.x-era mistakes that fail silently. Verified against crewai 1.15.22 and 1.15.23 on 2026-10-01. Live-tested on CrewAI AMP and real LLMs on 2026-10-01. Run `crewai version` first; if the major/minor differs from 1.15, re-verify version-sensitive rows with the `ask-docs` skill before trusting them. --- ## 1. Pick the mechanism | You need | Use | Section | |---|---|---| | A quick Python function as a tool | `@tool` from `crewai.tools` | 3 | | A tool with config, state, or a documented input schema | `BaseTool` subclass with `args_schema` | 3 | | A prebuilt search/scrape/file tool | `crewai_tools` - but import it once to prove the name exists | 5 | | A remote MCP server | `Agent(mcps=[MCPServerHTTP(...)])` - not an `https://` string if the crew is deployed or uses `akickoff()` | 6, 8 | | An MCP server that ships with your code | `Agent(mcps=[MCPServerStdio(...)])` - also works on CrewAI AMP when the server is in the package | 6, 10 | | An integration connected in your CrewAI AMP account | `mcps=["<slug>"]` or `"<slug>#<tool>"` | 6 | | Bare MCP tool names or a manual start/stop lifecycle | `MCPServerAdapter` (needs `crewai-tools[mcp]`) | 9 | `mcp` is already a core dependency of crewai 1.15.x - native `mcps=` needs no extra install. --- ## 2. Imports | You probably wrote | Current form | What happens with the old form |
Details
- Skill name
connect-tools-and-mcp- Repository
- crewAIInc/skills
- Path
skills/connect-tools-and-mcp/SKILL.md- License
- MIT
- Repo updated
- 6 October 2026
FAQ
What does the Connect Tools and MCP skill do?
Giving crewAI agents tools and MCP servers on crewai 1.15.x: custom BaseTool with args_schema and @tool, which crewai_tools names really exist, tool caching, max_usage_count, ToolFailure, Agent(mcps=[...]) string and MCPServerStdio/HTTP/SSE forms, rewritten MCP tool names, MCPServerAdapter, timeouts, and what works on a hosted deployment. Use when writing or debugging a tool or MCP connection, when you see 'cannot import name BaseTool from crewai_tools', 'You are missing the mcp package', 'MCPConnectionError', 'Operation timed out after 30 seconds', 'reached its usage limit', 'Invalid MCP refe
How do I install the Connect Tools and MCP skill?
Claude Code plugin: /plugin marketplace add crewAIInc/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Connect Tools and MCP popular?
It lives in crewAIInc/skills, which has 49 GitHub stars and 24 forks.
Related skills
Ask Docs
49crewAIInc/skills
Query the official CrewAI documentation for answers. Use when the user has a CrewAI question that isn't fully covered by the getting-started, design-agent, design-task skills — e.g., specific API details, configuration options, advanced features, troubleshooting errors, enterprise features, tool references, or anything where the latest docs are the best source of truth.
Build Flow
49crewAIInc/skills
Building CrewAI Flows on crewai 1.15.x: structured (Pydantic) vs dict state and state.id, @start/@listen/@router wiring, or_/and_ semantics, router labels vs method names, @persist (correct import, where it stores state, restore_from_state_id), checkpointing with CheckpointConfig, @human_feedback and HumanFeedbackResult.feedback, plot(), calling crews and agents from flow methods, kickoff inputs, and the `crewai create flow` scaffold. Use when writing or debugging a Flow subclass or main.py with `from crewai.flow import ...`, when a listener never fires or fires twice, or when you see errors l
Call Deployed Crew
49crewAIInc/skills
Calling a crew or flow deployed on CrewAI AMP over HTTP: the bearer token and deployment URL, GET /inputs, POST /kickoff with the {"inputs": {...}} body, which input keys are required ({placeholder} tokens), polling GET /status/{kickoff_id} with a deadline and backoff, terminal states and where the result lives, webhooks, POST /resume, slow first calls, and writing crews that stay correct when they are kicked off repeatedly or concurrently. Use when writing a client, script, backend or frontend that calls a deployed crew, when a kickoff returns 422 "Missing inputs: ...", when a status poll nev
Design Agent
49crewAIInc/skills
CrewAI agent design and configuration. Use when creating, configuring, or debugging crewAI agents — choosing role/goal/backstory, selecting LLMs, assigning tools, tuning max_iter/max_rpm/max_execution_time, enabling planning/delegation, setting up knowledge sources, using guardrails, or configuring agents in YAML vs code.
Moltbook Hot Posts
51agentbay-ai/agentbay-skills
查询Moltbook(Agent社区)热门帖子信息。当用户想要查询Agent社区热帖、最新讨论、热门话题时使用此skill。
Getting Started
49crewAIInc/skills
CrewAI architecture decisions and project scaffolding. Use when starting a new crewAI project, choosing between LLM.call() vs Agent.kickoff() vs Crew.kickoff() vs Flow, scaffolding with 'crewai create flow', setting up YAML config (agents.yaml, tasks.yaml), wiring @CrewBase crew.py, writing Flow main.py with @start/@listen, building experimental conversational Flows with handle_turn()/chat(), or using {variable} interpolation.
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.