Last updated: July 5, 2026
Use MCP in Chat and Automations
MCP (Model Context Protocol) is an open standard for connecting AI models to external tools and data sources. In Agent0, MCP servers are connectors — each one exposes a set of tools that Agent0 can call on your behalf. You never invoke these tools yourself.
The MCP integration is available in both Chat and Automations. MCP servers provide tools only, not trigger conditions for automations. Any MCP-compatible server can be connected to Agent0. The tools it exposes are discovered automatically and become available once the connector is enabled. See Set Up MCP Integration for configuration steps.
What Agent0 Uses MCP For
MCP extends what Agent0 can do beyond Dash0's built-in observability tools. Depending on which MCP servers are connected, Agent0 can:
- Interact with your IDE — read files, search code, run configurations, inspect problems in open projects
- Query external data sources — financial data, third-party APIs, internal tooling
- Extend project management — access additional capabilities beyond the built-in Linear and GitHub connectors
- Integrate with custom systems — any tool your organization exposes as an MCP server
Use MCP in Chat
In Chat, Agent0 uses MCP tools interactively during investigations. You can ask Agent0 to:
- Access files and code in your IDE
- Query external data sources relevant to your investigation
- Interact with custom internal tools exposed via MCP servers
Example Chat Requests
| You ask | What Agent0 does |
|---|---|
| "What files are open in my IDE right now?" | Calls the connected IDE MCP server to list open files |
| "Run the test configuration for this service" | Calls the IDE MCP server to execute a run configuration |
| "Are there any problems in this file?" | Calls the IDE MCP server to fetch diagnostics for the file |
| "Search for this function across the project" | Calls the IDE MCP server to search by text or symbol |
Use MCP in Automations
In Automations, Agent0 can use MCP tools as part of event-driven workflows. MCP servers provide tools only — they do not provide trigger conditions. You can configure automations to:
- Call MCP tools in response to Dash0 or integration triggers
- Query external systems during automated investigations
- Integrate custom tooling into automation workflows
Example Automation Use Cases
- Failed check queries custom tool — automation triggers on failed check, uses MCP tool to query internal deployment system, and correlates with telemetry
- Alert enrichment with external data — automation triggers on alert, calls MCP tool to fetch related business metrics, and includes them in the response
- IDE integration for code context — automation triggers on error spike, uses IDE MCP server to search for error handler implementations, and suggests fixes
Further Reading
- Set Up MCP Integration — Configure MCP servers
- Model Context Protocol — Official MCP specification and documentation
- Investigation & Analysis — How Agent0 uses tools during investigations
- Key Concepts — Reference terminology and mental model