Havoptic AI Release Intelligence

Connect it to your AI

Claude Code

claude mcp add --transport http releases https://mcp.havoptic.com/mcp

Claude, ChatGPT, Cursor and other apps

Add it as a custom connector with this URL (Streamable HTTP):

https://mcp.havoptic.com/mcp

Cursor, VS Code and other apps (mcp.json)

{
  "mcpServers": {
    "releases": {
      "url": "https://mcp.havoptic.com/mcp"
    }
  }
}

Tools it offers

15 tools, as the server itself reported during our check on Oct 31, 2026.

• list_tracked_toolsDeprecated: use list_tools. All AI coding tools Havoptic tracks (Claude Code, OpenAI Codex CLI, Cursor, Gemini CLI, Kiro CLI, GitHub Copilot CLI, Devin Desktop/Windsurf, Antigravity CLI, Grok Build), with release counts
• latest_releasesDeprecated: use get_latest_releases. Most recent AI coding tool releases (newest first), optionally filtered to one tool. Returns summaries; use get_release for full notes. Default detail=brief omits infographic URLs.
• release_historyDeprecated: use get_latest_releases with since. Release history for one tool within an optional date window (newest first). Summaries only; use get_release for full notes. Default detail=brief omits infographic URLs.
• search_release_notesDeprecated: use search_changes. Full-text search across all tracked release notes — flags, error strings, feature names, config keys. Returns ranked matches with snippet context.
• feature_timelineDeprecated: use feature_adoption. Which tool shipped each notable cross-tool feature first (MCP support, subagents, planning mode, hooks, checkpoints, ...), follower lag in days, and copying-trend insights. Optionally fi
• list_toolsCatalog of the products Havoptic tracks (AI coding tools plus model/API platforms, agent SDKs and inference runtimes): id, name, vendor, category, release count and latest release. Use first to find valid tool ids (fuzzy
• get_latest_releasesNewest releases (newest first) across all or selected tools. Successor to latest_releases and release_history (pass since/until for a date window). Default channel=stable, detail=brief.
• whats_changed_sinceDigest of typed changes (breaking, security, features, fixes, …) since a date or relative window ('7d', '30d'), grouped by tool with breaking changes first. States how many releases in range are legacy records without ty
• search_changesSearch typed change items (title + evidence) and, unless kinds is set, legacy release notes — flags, error strings, feature names, config keys. Successor to search_release_notes. Brief mode returns snippets only.
• get_releaseOne release by id (e.g. 'claude-code-2.1.183', canonical 'claude-code@2.1.183') or by tool + version ('latest' allowed). detail=full (the default for a bare id lookup, as before) includes complete release notes; brief/st
• get_upgrade_notesEverything between two versions of one tool: breaking changes, deprecations, security fixes, features and fixes, plus an explicit coverage gap for legacy releases without typed changes. to_version defaults to latest.
• get_breaking_changesBreaking changes (and, by default, deprecations) across tools in a window (default last 30 days), newest first. Legacy releases without typed changes are counted, not guessed.
• compare_toolsCompare 2–4 AI coding tools: release cadence, feature-matrix differences, recent changes, and Havoptic's editorial verdict per pair. aspects defaults to cadence, features, verdict. Legacy inputs tool_a/tool_b still work.
• feature_adoptionWho shipped a cross-tool feature first (MCP support, subagents, planning mode, hooks, checkpoints, …), which tools followed and their lag in days. Successor to feature_timeline.
• cadence_statsHow fast tools ship: release counts over 7/30/90 days, average days between releases, and last release — for selected tools or all of them. Legacy input tool (single id) still works.

Questions