Patchlog

io.github.michaelyousriePublished by GitHub account michaelyousriev0.1.0Updated Oct 25, 2026

Create, update, and publish changelog entries on your Patchlog changelog from any MCP client.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

Patchlog MCP server that lets an assistant draft, update, schedule and publish changelog entries on a Patchlog changelog.

What you can do
List projects and their public changelog URLs, and list entries filtered by status and type, or fetch one entry with its full Markdown content. Create entries as drafts, published immediately, or scheduled for a future date. Update any field of an existing entry. Publish a draft or scheduled entry live right away.
When to use it
Useful when you keep a public changelog on Patchlog and want an assistant to turn shipped features or release branches into entries, or to schedule announcements such as pricing changes, without leaving the editor.
Requirements
A Patchlog account on the Pro plan, since the API is a Pro feature. An API token from the account's API Tokens settings, supplied as the PATCHLOG_API_TOKEN environment variable or as a bearer token for the remote endpoint. Node.js 18 or newer for the local npm package; the remote endpoint needs no Node. PATCHLOG_API_URL optionally overrides the API base URL.
Before you install
The token grants write access to your changelog, so keep it out of shared config files. Creating, updating and publishing entries changes public content; entries can go live immediately or on a schedule, so review drafts before publishing.

Installation

In SourceWeft

  1. Open Patchlog in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. 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.michaelyousrie%2Fpatchlog/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "patchlog": {
      "type": "http",
      "url": "https://patchlog.io/mcp"
    }
  }
}

README

patchlog-mcp

MCP server for Patchlog. Write, update, and publish your changelog straight from Claude Code, Claude Desktop, Cursor, or any other MCP client. Ship a feature, then tell your agent "add a changelog entry for this" and it lands on your public changelog.

Requirements

Setup

Claude Code

bash
claude mcp add patchlog -e PATCHLOG_API_TOKEN=your-token-here -- npx -y patchlog-mcp

Claude Desktop

Add this to your claude_desktop_config.json:

json
{    "mcpServers": {        "patchlog": {            "command": "npx",            "args": ["-y", "patchlog-mcp"],            "env": {                "PATCHLOG_API_TOKEN": "your-token-here"            }        }    }}

Cursor

Add the same block to .cursor/mcp.json in your project, or to ~/.cursor/mcp.json globally:

json
{    "mcpServers": {        "patchlog": {            "command": "npx",            "args": ["-y", "patchlog-mcp"],            "env": {                "PATCHLOG_API_TOKEN": "your-token-here"            }        }    }}

Remote server (no Node required)

Patchlog also serves this same tool set as a remote MCP endpoint. Point your client at https://patchlog.io/mcp with your API token as a bearer token:

bash
claude mcp add --transport http patchlog https://patchlog.io/mcp --header "Authorization: Bearer your-token-here"

Tools

ToolWhat it does
list_projectsList your projects with their public changelog URLs
list_entriesList entries for a project, filterable by status and type
get_entryFetch one entry with its full Markdown content
create_entryCreate an entry (draft by default, or publish immediately, or schedule with a future date)
update_entryChange any field of an existing entry
publish_entryPush a draft or scheduled entry live right now

Configuration

Environment variableRequiredDefault
PATCHLOG_API_TOKENYesnone
PATCHLOG_API_URLNohttps://patchlog.io

Example prompts

  • "Add a changelog entry for the export feature we just shipped and publish it."
  • "Draft changelog entries for everything in this release branch, I will review them in Patchlog."
  • "Schedule a changelog entry about the pricing change for next Monday 9am."

Development

bash
npm installnpm testnpm run build

License

MIT

Source: README.md at commit 448f2bf

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

85% 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 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