io.github.apomt/release-to-tasks

Official registry Productivity

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

What can you do with io.github.apomt/release-to-tasks?

  • GitHub release pages (resolved through the public GitHub API)
  • GitHub release API URLs
  • GitLab release pages
  • Public Markdown/plain-text changelogs
  • Public HTML release-note pages

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package release-to-tasks-mcp
Claude Code
claude mcp add release-to-tasks -- npx -y release-to-tasks-mcp@0.1.0
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "release-to-tasks": {
            "command": "npx",
            "args": [
                "-y",
                "release-to-tasks-mcp@0.1.0"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. release-to-tasks-mcp
  2. Install
  3. Tool
  4. Demo
  5. Privacy and security
  6. Future extension points
  7. Development
  8. License

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.

{
  "mcpServers": {
    "release-to-tasks": {
      "command": "npx",
      "args": ["-y", "release-to-tasks-mcp@0.1.0"]
    }
  }
}

For a clean local invocation before npm publication:

npm ci
npm test
node dist/index.js

Tool

release_url_to_tasks

{
  "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

npm ci
npm test
npm 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

Frequently asked questions

What is io.github.apomt/release-to-tasks?

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

How do I install io.github.apomt/release-to-tasks?

It runs on your machine. In Claude Code: claude mcp add release-to-tasks -- npx -y release-to-tasks-mcp@0.1.0. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.apomt/release-to-tasks need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is io.github.apomt/release-to-tasks open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains io.github.apomt/release-to-tasks?

It is published by apomt. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.