Hi all, Initiating discussion on APE 36, an MCP gateway for AsterixDB.
Feature: MCP Gateway The gateway lets agent clients talk to a cluster over MCP instead of being handed /query/service and a prompt. It exposes the catalog, dataset schemas, optimizer and Hyracks plans, ADVISE index recommendations and cluster diagnostics as MCP tools, with results bounded so a SELECT * doesn't fill the model's context. It runs as a standalone sidecar, not inside the CC: MCP to the client, plain HTTP to the CC, no cluster state and no caching. It also never decides for itself whether a statement mutates — it sets readonly=true and lets the engine reject, rather than keeping a deny-list that would drift from the grammar. Inside AsterixDB the change is small: function_metadata() (21483) so the gateway reads the live function registry, and an optional /mcp proxy plus dashboard panel (21492), off by default. APE: https://cwiki.apache.org/confluence/spaces/ASTERIXDB/pages/449286300/APE+36+AsterixDB+MCP Thanks, Vivek
