Fizlog-mcp Server

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

Local serverstdioMIT

What is the Fizlog-mcp Server?

fizlog-mcp is an MCP project maintained in the firmalemony/fizlog-mcp repository. The maintainer describes its purpose as “MCP server for Fizlog — the changelog widget for indie SaaS. Let Claude, Cursor or any MCP client announce what you just shipped”. Read the project documentation for the complete scope.

Installation

The documented npm package is fizlog-mcp. The configuration below comes from the maintainer’s example; adapt its paths and account values to your environment.

Configuration values

The example declares FIZLOG_API_KEY, FIZLOG_PUBLIC_KEY. Secret-looking values have been replaced with placeholders. Required and optional labels are shown only when the documentation states them.

Source

Project documentation · Repository · Discovery listing. This profile records the public documentation checked on 2026-10-08.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

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

How to install the Fizlog-mcp Server

{
  "mcpServers": {
    "fizlog": {
      "command": "npx",
      "args": [
        "-y",
        "fizlog-mcp"
      ],
      "env": {
        "FIZLOG_API_KEY": "YOUR_FIZLOG_API_KEY",
        "FIZLOG_PUBLIC_KEY": "YOUR_FIZLOG_PUBLIC_KEY"
      }
    }
  }
}

From the project documentation. Replace placeholders and example paths before connecting.

Configuration

Variable	Description	Required
FIZLOG_API_KEY	Declared in the maintainer’s client configuration.	Check documentation
FIZLOG_PUBLIC_KEY	Declared in the maintainer’s client configuration.	Check documentation