greptimedb-mcp-server 0.6.0 adds query_semantic_graph. Since v1.3.0 (alpha), GreptimeDB keeps entity and relationship views in greptime_private, built from trace spans and declared edges. The tool reads them directly, so an assistant asks what calls what instead of writing a self-join over span tables. The summary view answers first — which types exist and what they connect: { "type": "calls", "count": 2, "endpoints": [ { "source": "service", "destination": "service", "count": 2 } ] } Then entities or relationships when it wants the rows. On older servers the tool isn't offered at all — the server probes the views at startup and drops it from the list. github.com/GreptimeTeam/grep…