Pemanfaatan Model Context Protocol untuk Otomatisasi Root Cause Analysis pada Microservices Berbasis Docker

Muhammad Silmy Firdaus (Universitas Gadjah Mada, Daerah Istimewa Yogyakarta)
Sahirul Alam (Universitas Gadjah Mada, Daerah Istimewa Yogyakarta)

TIN: TERAPAN INFORMATIKA NUSANTARA
Vol 7 No 5 (2026): October 2026

Microservices architecture deployed in Docker container environments offers high scalability, yet generates large and segmented telemetry data that prevents conventional monitoring methods from supporting rapid root cause analysis. Administrators must manually trace hundreds of metrics and logs through complex dashboards, while existing chatbot approaches remain rule-based and limited to presenting raw data without deep analysis. This study designs and implements a monitoring system that integrates a Large Language Model (LLM) through the Model Context Protocol (MCP) to automate disruption analysis on Docker-based microservices. A custom MCP Server was developed by modifying the open-source Prometheus-MCP-Server repository to bridge two telemetry sources: container metrics collected by Prometheus via cAdvisor, and container logs retrieved from the Docker Daemon via the Docker SDK, combined with a natural-language interface provided by the LLM through Cursor as the MCP Client. The research object consisted of eight e-commerce microservice containers running on a Virtual Private Server. Telemetry accuracy validation yielded a mean MAE of 0.1071 MB and a mean MAPE of 0.29% across all containers. Response-time testing showed the system responding within 3-23 seconds, with the LLM reasoning component dominating 98.72%-99.81% of total response time, while the MCP Server contributed only 0.044 seconds of overhead. Scalability testing with 1-10 concurrent users showed elastic CPU usage and stable RAM consumption within 165.7-169.3 MB. These findings demonstrate the technical feasibility of MCP-based LLM integration for supporting microservices incident analysis through unified access to container metrics and logs, while highlighting limitations in RCA diagnostic accuracy evaluation and production-scale scalability testing.