Changelog Hq

io.github.therealMrFunGuyPublished by GitHub account therealMrFunGuyv1.0.0Updated Oct 24, 2026

Auto-generate changelogs from GitHub PRs with AI-powered categorization and rewriting.

VerifiedSSEWeb executableDeveloper Tools

Overview

AI-generated overview

Generates changelogs from GitHub pull requests, using AI to categorize and rewrite entries.

What you can do
This remote MCP server connects an assistant to a changelog generation service. According to its description, it takes GitHub pull requests and produces changelog entries, with AI-powered categorization and rewriting of the text. No individual tools are listed in the available manifest, so the exact operations are not documented here.
When to use it
Consider it when you maintain a GitHub project and want release notes or changelog entries drafted from merged pull requests instead of writing them by hand. It is a remote service, so it suits assistants that can reach an external endpoint.
Requirements
A remote MCP connection over SSE to the provider's endpoint. An API key is sent in the X-API-Key header, obtained from the provider's dashboard. No environment variables or local packages are declared. Network access to the endpoint is required.
Before you install
The server is remote, so pull request data is sent to a third party for processing. It requires an API key (X-API-Key) from the provider's dashboard; treat that credential as a secret. The manifest declares no authentication beyond the header, and no tools are listed, so review what the service does with your repository data before connecting it to private projects.

Installation

In SourceWeft

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

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.therealMrFunGuy%2Fchangelog-hq/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "changelog-hq": {
      "type": "sse",
      "url": "https://changelog.rjctdlabs.xyz/sse"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.