Havoptic AI Release Intelligence

Release intelligence for AI coding tools: releases, typed changes, breaking changes, cadence.

Install

Remote server: your requests and data go to mcp.havoptic.com. Claude Code: claude mcp add --transport http havoptic-ai-release-intelligence https://mcp.havoptic.com/mcp · Claude app: Settings → Connectors → Add custom connector.

What it can do

The tools this server listed when we connected to it, in its own words.

• list_tracked_tools — Deprecated: use list_tools. All AI coding tools Havoptic tracks (Claude Code, OpenAI Codex CLI, Cursor, Gemini CLI, Kiro CLI, GitHub Copilot
• latest_releases — Deprecated: use get_latest_releases. Most recent AI coding tool releases (newest first), optionally filtered to one tool. Returns summaries;
• release_history — Deprecated: use get_latest_releases with since. Release history for one tool within an optional date window (newest first). Summaries only;
• search_release_notes — Deprecated: use search_changes. Full-text search across all tracked release notes — flags, error strings, feature names, config keys. Return
• feature_timeline — Deprecated: use feature_adoption. Which tool shipped each notable cross-tool feature first (MCP support, subagents, planning mode, hooks, ch
• list_tools — Catalog of the products Havoptic tracks (AI coding tools plus model/API platforms, agent SDKs and inference runtimes): id, name, vendor, cat
• get_latest_releases — Newest releases (newest first) across all or selected tools. Successor to latest_releases and release_history (pass since/until for a date w
• whats_changed_since — Digest of typed changes (breaking, security, features, fixes, …) since a date or relative window ('7d', '30d'), grouped by tool with breakin
• search_changes — Search typed change items (title + evidence) and, unless kinds is set, legacy release notes — flags, error strings, feature names, config ke
• get_release — One release by id (e.g. 'claude-code-2.1.183', canonical '[email protected]') or by tool + version ('latest' allowed). detail=full (the de
• get_upgrade_notes — Everything between two versions of one tool: breaking changes, deprecations, security fixes, features and fixes, plus an explicit coverage g
• get_breaking_changes — Breaking changes (and, by default, deprecations) across tools in a window (default last 30 days), newest first. Legacy releases without type
• compare_tools — Compare 2–4 AI coding tools: release cadence, feature-matrix differences, recent changes, and Havoptic's editorial verdict per pair. aspects
• feature_adoption — Who shipped a cross-tool feature first (MCP support, subagents, planning mode, hooks, checkpoints, …), which tools followed and their lag in
• cadence_stats — How fast tools ship: release counts over 7/30/90 days, average days between releases, and last release — for selected tools or all of them.

KitScout test notes

Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.

Similar tools

• grill-with-docs 323,337 ★
  A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
• research 323,337 ★
  Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the r
• documentation-and-adrs 117,221 ★
  Records decisions and documentation, and detects when documentation has drifted from the code it describes. Us
• doc-maintenance 113,505 ★
  Audit README and PRODUCT docs against recent git history for drift and make minimal PR-ready edits. Use when a
• doc-maintenance 113,505 ★
  Keep project docs aligned with recent code and feature changes — detect drift, update affected pages, and add