Hi Tanishq, +1 for the initiative and the overall direction.
One point I would consider is keeping the HMS MCP separate from the Hive query execution MCP. HMS is already a standalone component that can be deployed and released independently of Hive, and it is used by engines beyond Hive itself, such as Spark, Trino, and Impala. Because of that, an HMS-focused MCP could provide metadata discovery capabilities as a reusable integration point for the broader ecosystem, without coupling those capabilities to HiveServer2 or query execution. The two MCP servers could still share common code or APIs where appropriate, but having independently deployable MCP endpoints seems more aligned with the existing HMS architecture and its role as a shared metadata service. Best, Denys
