MCP server
LogPulse
By lovable
Changelogs for coding agents: versions, breaking changes, migrations. Free changelog-to-JSON.
Listed on
First seen 30 Oct 2026. One server, whatever directories list it: each directory listing keeps its own page and history.
1
Directories
Collected by InvokeRank
12
Tools
From an anonymous probe
-
ToolBench grade
Not graded by Arcade
-
GitHub stars
No repository data
Tools
| Tool | Description | Behaviour |
|---|---|---|
| commits_to_changelog | Turn git log output or commit messages into a Keep a Changelog 2.0.0 section (Added, Changed, Deprecated, Removed, Fixed, Security) with breaking changes flagged and their migration steps, plus plain-language release notes. Reads Conventional Commits (feat:, fix:, ! and BREAKING CHANGE: footers) and plain subjects; leaves out merges, release commits and chores; stops at the previous release's tag and suggests the next version. Deterministic, nothing stored. Run `git log <last-tag>..HEAD --no-merges` and pass its output as log. | Read-only |
| compare_versions | Answer “what changed between two versions, and what do I need to change?”: breaking changes with migration steps, deprecations and every release after `from` up to `to`. | Read-only |
| convert_changelog | Turn any project's CHANGELOG.md text, or a GitHub release, releases page, repository or changelog file URL, into a machine-readable changelog: versions, dates, breaking changes with migration steps, and deprecations. Works for projects that aren't on LogPulse. Returns an llms.txt-style summary plus structured JSON. | Read-only |
| generate_release_notes | Write release notes from a public GitHub repository's commits and merged pull requests: since the last tag by default, between two tags (from/to), or between two dates (since/until). Breaking changes are marked and grouped. Returns Markdown or a Keep a Changelog section ready for CHANGELOG.md, plus a suggested next version. No AI, no sign-in. | Read-only |
| get_changelog | Get a changelog's name, repository, packages, latest version and feed links. | Read-only |
| get_release | Get one release by version (2.0.0 or v2.0.0) or URL slug, with full notes, breaking changes and deprecations. | Read-only |
| get_roadmap | Get the public roadmap: items under review, planned, in progress and shipped, with vote counts. | Read-only |
| list_releases | List published releases, newest first, with versions, breaking changes, migration steps and deprecations. | Read-only |
| post_roadmap_update | Add an item to your LogPulse roadmap, or update one by id — move it to in progress or shipped, change its ETA, or link the release that shipped it. Needs a LogPulse API key with the “Update roadmap” permission, sent as the Authorization header. | Changes data |
| publish_release | Publish a release note to your LogPulse changelog right after shipping — with version, breaking changes, migration steps and deprecations. Needs a LogPulse API key with the “Publish releases” permission, sent as the Authorization header. | Changes data |
| search_changelogs | Find a public LogPulse changelog by package name, repository, product name or slug. Returns slugs to use with the other tools. | Read-only |
| validate_changelog | Check a CHANGELOG.md against Keep a Changelog 2.0.0: version headings, YYYY-MM-DD dates, newest-first order, the six types of change, breaking-change markers, Unreleased, reference links. Returns each problem with its line number and fix, plus a corrected copy with the safe fixes applied. Pass the text, or a public GitHub repository or changelog file URL. | Read-only |
| Directory | Listing | Tier | First seen |
|---|---|---|---|
| Official MCP Registry | LogPulse | - | 30 Oct 2026 |