Summary

The marketing/popup info on https://contextstream.io/ links to the MCP release notes via a "View all releases on GitHub" button pointing at https://github.com/contextstream/mcp/releases, but that URL returns a 404 (the repository contextstream/mcp does not exist or is not publicly accessible). Users/agents following that link cannot find release history.

Additionally, there is currently no programmatic way for an agent to discover what changed between MCP server versions. I'd like to propose a release-notes tool so agents can self-surface "what's new / breaking changes" after an update.

Problem 1 — broken releases link

• Source page: https://contextstream.io/
• Link label: "View all releases on GitHub"
• Link target: https://github.com/contextstream/mcp/releases
• Result: 404 (repository not found / not public)

Expected: the link should point to the actual releases location for the MCP server (e.g. contextstream/mcp-server/releases or wherever the canonical repo lives), or the contextstream/mcp repo should be created/published.

Problem 2 — no machine-readable release-notes access for agents

When the MCP server updates (e.g. the Windows client 0.3.4 → 0.3.5, or ContextCode 0.5.1), agents have no built-in way to learn what changed. This leads to confusion like the indexing issue in #69, where behavior changed but wasn't discoverable.

Proposed tool: release_notes

Add an MCP tool (and/or a help(action="version") enhancement) that exposes release history to agents, for example:

release_notes(action="list", limit=10)
release_notes(action="get", version="0.3.5")
release_notes(action="latest")
release_notes(action="since", version="0.3.4")   # what changed since a given version

Return shape (suggested):

{
  "version": "0.3.5",
  "date": "2026-07-10",
  "summary": "Windows client indexing fixes",
  "breaking_changes": [],
  "features": ["..."],
  "fixes": ["..."],
  "notes_url": "https://github.com/contextstream/mcp-server/releases/tag/0.3.5"
}

Why this helps

• Agents can call release_notes(action="since", version=<current>) on startup and surface a [VERSION_NOTICE]-style summary of what changed.
• Reduces support load from behavior changes that aren't discoverable.
• Lets the existing [VERSION_NOTICE] / [VERSION_CRITICAL] mechanism be driven by real release data instead of manual checks.

Source of truth

The release notes should be sourced from the canonical GitHub releases (the same place the popup should link to), so the popup link and the agent tool stay consistent.

Suggested fix order

1. Fix the popup link on https://contextstream.io/ to point at the real releases URL (and/or publish contextstream/mcp).
2. Add the release_notes MCP tool backed by the same releases source.