MCP server

Connect Claude Code, Claude Desktop, Cursor or any MCP client to Havoptic: remote streamable HTTP server, tools, resources, prompts, and a stdio bridge for clients that only launch local servers.

The remote MCP server at https://mcp.havoptic.com/mcp gives agents current, cited facts about AI coding tool releases. It is stateless, read-only and needs no authentication. It is listed in the official MCP Registry as com.havoptic/releases.

Connect a client

Claude Code

# Remote (preferred, no local process)
claude mcp add --transport http havoptic https://mcp.havoptic.com/mcp

# Or via the stdio bridge
claude mcp add havoptic -- npx -y havoptic mcp

Claude Desktop

// ~/Library/Application Support/Claude/claude_desktop_config.json (macOS)
// %APPDATA%\Claude\claude_desktop_config.json (Windows)
{
  "mcpServers": {
    "havoptic": {
      "command": "npx",
      "args": ["-y", "havoptic", "mcp"]
    }
  }
}

Cursor

// ~/.cursor/mcp.json or .cursor/mcp.json
{ "mcpServers": { "havoptic": { "url": "https://mcp.havoptic.com/mcp" } } }

Restart the client, then ask "What changed in Claude Code this week?" and check that it calls a havoptic tool.

stdio bridge

npx -y havoptic mcp starts a local stdio server that forwards every JSON-RPC message unchanged to the remote server, so it always exposes exactly the same tools. Diagnostics go to stderr. Use --url to point it at another endpoint.

Tools

Tool	Purpose
`whats_changed_since(since, tools?, kinds?)`	Typed-change digest, breaking first.
`get_upgrade_notes(tool, from_version, to_version?)`	Upgrade report with legacy coverage gap.
`get_breaking_changes(tools?, since?, include_deprecations?)`	Breaking and deprecation feed.
`search_changes(query, tools?, kinds?)`	Change items and release-note matches.
`get_latest_releases(tools?, limit?, channel?)`	Newest releases.
`get_release(id \| tool + version, include_raw_notes?)`	One release.
`compare_tools(tools[2..4], since?, aspects?)`	Cadence, feature differences, recent changes, verdicts.
`feature_adoption(feature)`	First-to-ship timeline for one feature.
`cadence_stats(tools?)`	Ship velocity.
`list_tools(category?, vendor?, query?)`	Product catalog.

Tools return markdown text plus structuredContent with dataset_updated_at, freshness_note, truncated and next_cursor. Most accept max_tokens (default 1500) and detail to control output size. Tool ids are matched fuzzily, with suggestions on a miss.

The original tool names (list_tracked_tools, latest_releases, release_history, search_release_notes, feature_timeline, plus the legacy argument forms of cadence_stats and compare_tools) keep working until at least 2027-11-01 and are marked deprecated with a successor.

Resources

havoptic://tools and havoptic://tools/{id}
havoptic://releases/{id}
havoptic://tools/{id}/changelog{?since}
havoptic://schema/{name}
havoptic://docs/api

Prompts

weekly_ai_tools_brief(tools?, audience?)
upgrade_check(tool, current_version)
compare_for_team(tools, priorities)
release_announcement(release_id, channel)

Discovery

Server card: /.well-known/mcp.json (SEP-2127 card at /.well-known/mcp/server-card.json). Errors inside tool results use the same problem shape as the REST API, with isError: true.

Developer docs · API reference · OpenAPI · Havoptic