Interfacing with the DevOps Agent
AWS DevOps Agent supports five access methods: the web app console, Model Context Protocol (MCP) integration, Agent Client Protocol (ACP) integration, webhooks for event-driven automation, and direct API access. Choose the method that best fits your workflow and technical requirements.
The following diagram illustrates these access methods and how they connect to the DevOps Agent service.
DevOps Agent web app
The web app is the primary interface for DevOps Agent. Use conversational chat to investigate incidents, query your infrastructure, and manage recommendations. For more information, see What is a DevOps Agent Web App?.
Model Context Protocol (MCP) integration
You can access AWS DevOps Agent capabilities directly from MCP-compatible clients and IDEs. Use the AWS MCP Server to connect. You can investigate incidents, optimize costs, review architecture, and map topology without leaving your development environment.
For Kiro
For Claude Code
Agent Client Protocol (ACP) integration
You can invoke AWS DevOps Agent programmatically using the Agent Client Protocol (ACP)
Webhooks
Webhooks allow external systems to automatically trigger AWS DevOps Agent investigations. External systems such as ticketing platforms and monitoring tools can send HTTP requests when incidents occur. For more information, see Invoking DevOps Agent through Webhook.
AWS DevOps Agent API
AWS DevOps Agent provides APIs for programmatic access to agent capabilities. You can create and manage Agent Spaces, trigger investigations, and retrieve findings. For more information, see the AWS DevOps Agent API Reference.