Convert public release-note URLs into ordered, source-cited upgrade tasks.
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.
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
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:
Malformed URLs, non-HTTPS URLs, local/private destinations, unsupported pages, missing release bodies, oversized responses, and unsafe redirects return explicit errors.
release_url_to_tasks with a real public release URL.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.
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.
The parser and fetcher boundaries can later support authenticated private-source connectors. This release contains no payment, Stripe, private-source, or hosted-service dependency.
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.
MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y release-to-tasks-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-apomt-release-to-tasks": {
"command": "npx",
"args": [
"-y",
"release-to-tasks-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencerelease-to-tasks-mcpnpmio.github.apomt/release-to-tasks works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.