Fizlog Mcp

io.github.firmalemonyv0.1.0Updated Oct 5, 2026

Publish changelog entries to Fizlog (in-app widget, public page, RSS) from any MCP client.

VerifiedSTDIODesktop onlyProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Lets an assistant publish, schedule, or draft Fizlog changelog entries and read the public changelog.

What it does
A local MCP server for Fizlog, a changelog widget for indie SaaS. Its publish_entry tool publishes, schedules, or saves an entry as a draft, which then appears in the in-app widget, the public changelog page, and RSS, with an optional subscriber email. Its get_public_changelog tool reads the latest published entries so the assistant can avoid duplicates or summarize releases.
When to use it
Useful when you want an assistant to announce what you just shipped without leaving your editor or chat client, for example publishing a changelog entry for a finished feature. Also handy for checking recent releases before writing a new entry.
Requirements
Runs locally over stdio, typically via npx with the npm package fizlog-mcp, so Node.js is needed. FIZLOG_API_KEY is required for publishing; FIZLOG_PUBLIC_KEY is optional and used as the default for reading the public changelog. FIZLOG_BASE_URL is optional for self-hosted Fizlog and defaults to the hosted service. Network access to Fizlog is required.
Before you install
FIZLOG_API_KEY is a project API key that authorizes publishing to your changelog; store it in the client configuration rather than sharing it. Publishing can make content publicly visible on the changelog page and RSS, and can optionally send subscriber email, so review entries before publishing. The documented smoke test creates a draft entry in the target project, so run it against a local or test instance.

Installation

In SourceWeft

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

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

fizlog-mcp

MCP server for Fizlog — the changelog widget for indie SaaS. Let Claude, Cursor or any MCP client announce what you just shipped:

"Publish a changelog entry for the CSV export I just finished."

Tools

ToolWhat it does
publish_entryPublishes (or schedules / saves as draft) an entry — shows up in your in-app widget, public changelog page and RSS. Optional subscriber email.
get_public_changelogReads your latest published entries, so the assistant can avoid duplicates or summarize releases.

Setup

  1. In Fizlog, open your project and copy the API key (and the public key from the embed snippet).
  2. Add the server to your MCP client:

Claude Code

bash
claude mcp add fizlog -e FIZLOG_API_KEY=fz_xxx -e FIZLOG_PUBLIC_KEY=your_public_key -- npx -y fizlog-mcp

Claude Desktop (claude_desktop_config.json) / Cursor (~/.cursor/mcp.json)

json
{  "mcpServers": {    "fizlog": {      "command": "npx",      "args": ["-y", "fizlog-mcp"],      "env": { "FIZLOG_API_KEY": "fz_xxx", "FIZLOG_PUBLIC_KEY": "your_public_key" }    }  }}
Env varRequiredDefault
FIZLOG_API_KEYfor publish_entry—
FIZLOG_PUBLIC_KEYno (default for get_public_changelog)—
FIZLOG_BASE_URLno (self-hosted Fizlog)https://fizlog.com

Related

  • publish-to-fizlog — GitHub Action that posts a Fizlog entry for every GitHub release.
  • Fizlog migration guides — move your changelog from Beamer, Headway, AnnounceKit, Canny and others.
  • Listed in the official MCP Registry as io.github.firmalemony/fizlog-mcp.

Development

bash
npm installnpm run buildFIZLOG_BASE_URL=http://localhost:8888/fizlog FIZLOG_API_KEY=... FIZLOG_PUBLIC_KEY=demo npm run smoke

The smoke test creates one draft entry in the target project — run it against a local/test instance.

MIT © Lemony Apps

Source: README.md at commit 8143520

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v0.1.0LatestOct 5, 2026