Release To Tasks

io.github.apomtPublished by GitHub account apomtv0.1.0Updated Oct 24, 2026

Convert public release-note URLs into ordered, source-cited upgrade tasks.

VerifiedSTDIODesktop onlyProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

Turns a public release-note URL into ordered, source-cited upgrade tasks an assistant can review and act on.

What you can do
Exposes one tool, release_url_to_tasks, which takes a public release URL and returns a source format, release title, ordered tasks, and warnings. Each task keeps the exact source URL and anchor plus a short source excerpt, and low-confidence entries are flagged as needing human impact assessment. Supported inputs include GitHub release pages and API URLs, GitLab release pages, public Markdown or plain-text changelogs, and public HTML release-note pages. The server only reads and parses release text; it does not execute release text or project code.
When to use it
Useful when planning a dependency or platform upgrade and you want the release notes converted into a checklist that stays traceable to its source. It fits assistants that help triage changelogs, breaking changes, and migration steps before someone applies an upgrade.
Requirements
Runs locally over stdio, typically started with npx from the npm package release-to-tasks-mcp. Node.js 22.14 or newer is required. No accounts, API keys, environment variables, or headers are declared; network access is needed to fetch the public release pages.
Before you install
It fetches public URLs, so the release URL you pass is sent to the source site and, for GitHub pages, resolved through the public GitHub API. Malformed, non-HTTPS, local or private destinations, unsupported pages, missing release bodies, oversized responses, and unsafe redirects return explicit errors. Tasks are proposals only: check each task against its source excerpt and URL before applying an upgrade, and treat low-confidence entries as needing human assessment. Telemetry is off by default…

Installation

In SourceWeft

  1. Open Release To Tasks in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

release-to-tasks-mcp

Turn one public release-note URL into ordered upgrade tasks that retain a source excerpt, anchor, confidence, and uncertainty. The MCP server never executes release text or project code.

Install

Node.js 22.14 or newer is required.

json
{  "mcpServers": {    "release-to-tasks": {      "command": "npx",      "args": ["-y", "[email protected]"]    }  }}

For a clean local invocation before npm publication:

sh
npm cinpm testnode dist/index.js

Tool

release_url_to_tasks

json
{  "release_url": "https://github.com/modelcontextprotocol/python-sdk/releases/tag/v2.1.1"}

The result contains sourceFormat, releaseTitle, ordered tasks, and warnings. Every task includes the exact source URL/anchor and a short source excerpt. Low-confidence entries explicitly require human impact assessment.

Supported sources:

  1. GitHub release pages (resolved through the public GitHub API)
  2. GitHub release API URLs
  3. GitLab release pages
  4. Public Markdown/plain-text changelogs
  5. Public HTML release-note pages

Malformed URLs, non-HTTPS URLs, local/private destinations, unsupported pages, missing release bodies, oversized responses, and unsafe redirects return explicit errors.

Demo

  1. Configure the server in an MCP client.
  2. Call release_url_to_tasks with a real public release URL.
  3. Check each proposed task against its source.excerpt and source.url before applying an upgrade.

The repository includes a non-fabricated sample response shape. The sample deliberately contains no tasks because release content can change; tests contain deterministic source fixtures.

Privacy and security

Telemetry is disabled by default and there is no hosted collector. Optional local aggregate telemetry never includes URLs or release contents. See PRIVACY.md and SECURITY.md.

Future extension points

The parser and fetcher boundaries can later support authenticated private-source connectors. This release contains no payment, Stripe, private-source, or hosted-service dependency.

Development

sh
npm cinpm testnpm pack --dry-run

Internal tests and owner traffic are technical signals only; they never count as external adoption. LEVEL 2 requires three unrelated external users to install the public package and successfully process real release URLs.

License

MIT

Source: README.md at commit 01cf846

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts