How does the Status Observer MCP handle cases where the status APIs of monitored platforms have varying data formats? Does it require custom parsing logic for each platform, or is there a unified way to handle different responses?
Thanks for the question! Yes, Status Observer MCP handles varying API formats through a hybrid approach. While some platforms provide clean JSON responses, others like GCP required custom helpers in a separate backend that parse the specific data formats and normalize them before delivery to the MCP server. This lets us handle platform-specific quirks while maintaining a consistent devolution. If you have any platform suggestions you'd like to see added, please create an issue in the repository. I'd be happy to work on implementing them!