Future of staff-level engineering, MCP auth, CLI dev, new GraphQL tagline, governance by default, API vs. Tool design

GraphQL's Primary Working Group discussed the future of the API language in the AI era, including HTTP QUERY and upcoming spec releases, while industry leaders debate the role of staff engineers and the governance implications of GraphQL versus REST. Camille Lawrence, maintainer of Apollo MCP Server, shared insights on API design, tool design, and AI in recent interviews.

Is GraphQL "the API language for humans and agents?" is-graphql-the-api-language-for-humans-and-agents The GraphQL Primary Working Group's August 2026 meeting has come and gone, but some key questions remain. One of them is about GraphQL's identity in the AI era. Learn about this, HTTP QUERY, upcoming spec releases, and more: You're all staff engineers now youre-all-staff-engineers-now "Junior Staff Engineer." Is that title in our future? Maybe not literally, but in a manner of speaking, I think we need to get serious as an industry about how we're going to cultivate the judgment and high-level expertise necessary for the next generation of staff engineers. "Doing GraphQL is Governance by Default, Doing REST is Not" doing-graphql-is-governance-by-default-doing-rest-is-not Is that true? I think so, here's me yapping about why: Conversations with Camille Lawrence conversations-with-camille-lawrence Camille maintains Apollo MCP Server and has done significant work with rover CLI. So I sit up straight when she has something to say about API design, tool design, and AI. I truly enjoyed these interviews; I think you will, too