Back to blog
Product

ChartQuery MCP now supports the 2026-07-28 spec

Josselin Liebe
Josselin Liebe

Anthropic shipped MCP 2026-07-28, a major update to the Model Context Protocol. The big change is a stateless core: request/response over HTTP instead of a bidirectional stateful session. That makes MCP servers easier to run on serverless and edge infrastructure.

We updated the ChartQuery MCP server to match.

What changed for you

Nothing in your config. The endpoint stays the same:

https://mcp.chartquery.com/

Same API key header, same tools for charts, diagrams, barcodes, QR codes and labels. If you already have ChartQuery wired into Claude Code, Cursor or another MCP client, you are on the new protocol.

Under the hood, the server now speaks the 2026-07-28 protocol. That keeps us aligned with Claude's rollout and with other clients adopting the new spec.

Why it matters

The previous MCP model required session state. Fine for a long-lived process, awkward for an HTTP API. The new core fits how ChartQuery already works: send a payload, get a rendered image back, done.

If you are connecting ChartQuery for the first time, the MCP setup guide still applies. Full docs are at docs.chartquery.com/mcp.