io.github.garlicKim21/ratatosk-mcp (MCP)

This MCP server provides CNCF release intelligence by extracting typed facts from release notes. It also supports local version comparisons: the check_stack function compares versions on the local system to help determine update status against release information.

🛠️ Key Features

CNCF release intelligence
Typed facts extracted from release notes
Local version comparison via check_stack

🚀 Use Cases

Determine what release information applies to a given CNCF component
Compare locally installed versions against release notes expectations

⚡ Developer Benefits

Structured, typed release-note facts for downstream processing
Local check_stack comparisons without requiring remote version data

⚠️ Limitations

Description provided does not include supported CNCF project list, tool names beyond check_stack, or configuration details.

What it feels like

You: "We run envoy v1.36.8 and istio 1.30.1. Anything we must do before upgrading?"

Your agent calls check_stack and answers from facts: the CVEs fixed after your version, the APIs removed on your upgrade path, the defaults that changed. Each fact carries a verbatim quote from the release notes as evidence.

Tools

Tool

What it does

list_facts

Incremental fact feed. Filter by project, type, severity; poll with the since cursor

facts_by_entity

Reverse index: every fact touching one identifier (CVE id, CRD, feature gate, flag, config field, dependency)

list_projects

The tracked-project roster — resolve slugs here first, never guess

get_release

One reviewed release: coverage, assessment, source, and all its facts. Omit version for the latest reviewed release of the project. facts: [] with coverage: full_reviewed means the release was read and is routine. include_raw adds the original note body (raw_notes) — automatic when the review is not the full story

list_releases

The newest N reviewed releases of one project as light summaries (fact counts by severity, max advisory-group severity), newest first — the tool for "recent releases of X". Drill into a row with get_release

check_stack

Takes the component versions you run, returns a briefing on your upgrade path: critical/high facts in full, one line each for the rest, the same advisory across release branches folded into one entry. detail: "full" for everything verbatim, target_version for one upgrade hop, severity_min to filter

Your versions stay on your side

check_stack sends only project slugs to the server and compares version keys locally, inside this process. What you run never reaches ratatosk.io. The server publishes facts; your agent decides what applies. The version normalizer is bundled (internal/version), so range comparison happens client-side too.

This holds for upgrade questions as well: the upstream API has a convenience endpoint (/v1/upgrade) that receives caller-supplied versions — check_stack never calls it and never will. Upgrade-path comparison stays in this process, guaranteed by code you can read, not by configuration.

Install & usage — local stdio · in-cluster (Helm) · kagent

한국어 · 日本語

Helm chart — values, kagent toggle

한국어 · 日本語

kagent example — manifests + ratatosk-agent

한국어 · 日本語

Contributing · Security policy

Data & terms

The data is served by ratatosk.io free of charge (subject to change, with advance notice) under its terms of service. Analyses are AI-generated reference information with no warranty — check the original release notes before acting, especially when an agent acts on your behalf. Original notes belong to their respective projects; responses that carry a full note include an attribution notice (raw_notes_notice).

io.github.garlicKim21/ratatosk-mcp