MCP (Model Context Protocol) servers extend what the agent can do — access external APIs, connect to databases, search documentation, run specialized tools. Each server provides a set of tools the agent can call during conversations.
Open Agent Capabilities → Integrations (MCP). The panel shows all configured servers with their status (connected, error, unknown) and lets you:
Crew ships with two managed servers that are always available:
| Server | Tools it provides |
|---|---|
| kirocrew-core | Spawn subagents, learn lessons, run tasks, register hooks, send messages, search knowledge |
| kirocrew-cron | Schedule, list, pause, resume, trigger, remove cron jobs |
These load automatically — no configuration needed.
Click Discover & Sync in the Integrations panel. Crew scans your MCP configuration files and adds any new servers it finds. Then click Probe All to verify each server responds to the MCP handshake.
Common servers to add:
slack-mcp — Slack API accessplaywright — headless browser automationOnce a server is enabled, its tools appear in the agent's tool list automatically. The agent decides when to call them based on the conversation. You don't need to tell the agent which tool to use — it reads the tool descriptions and picks the right one.
Tool calls from MCP servers go through the same approval pipeline as built-in tools: interactive approval prompts (or auto-approved in Autopilot mode), with denied commands and security controls still applying.
Integrations (MCP)