Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@fizlog-mcp publish a changelog entry for the CSV export I just shipped"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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."
Tool | What it does |
| Publishes (or schedules / saves as draft) an entry — shows up in your in-app widget, public changelog page and RSS. Optional subscriber email. |
| Reads your latest published entries, so the assistant can avoid duplicates or summarize releases. |
Related MCP server: Claude Synergy
In Fizlog, open your project and copy the API key (and the public key from the embed snippet).
Add the server to your MCP client:
Claude Code
claude mcp add fizlog -e FIZLOG_API_KEY=fz_xxx -e FIZLOG_PUBLIC_KEY=your_public_key -- npx -y fizlog-mcpClaude Desktop (claude_desktop_config.json) / Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"fizlog": {
"command": "npx",
"args": ["-y", "fizlog-mcp"],
"env": { "FIZLOG_API_KEY": "fz_xxx", "FIZLOG_PUBLIC_KEY": "your_public_key" }
}
}
}Env var | Required | Default |
| for | — |
| no (default for | — |
| no (self-hosted Fizlog) |
|
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.
npm install
npm run build
FIZLOG_BASE_URL=http://localhost:8888/fizlog FIZLOG_API_KEY=... FIZLOG_PUBLIC_KEY=demo npm run smokeThe smoke test creates one draft entry in the target project — run it against a local/test instance.
MIT © Lemony Apps
Read the latest published entries of a Fizlog project by its public key (the key in the embed snippet / public page URL). Useful to avoid duplicate announcements or to summarize recent releases.
Inputs: limit, public_key.
Publish a new entry to the project's Fizlog changelog (in-app widget, public page and RSS). Use it after shipping a feature or fix. Write for end users, not developers: a short benefit-focused title and 1–3 sentences of Markdown (bold, italic, code, links, '- ' lists). Set draft=true to save without publishing, or published_at to schedule.
Inputs: title (required), body, type, draft, +2 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 2 tools
The two tools have clearly distinct purposes: read public changelog entries vs. publish a new entry. An agent can easily tell which to use for a given request, with no overlap.
Both names use snake_case with a leading verb (get_, publish_), which is consistent. However, get_public_changelog inserts an adjective and refers to 'changelog' while publish_entry refers to 'entry', a minor noun mismatch.
Two tools for a changelog service is borderline thin. While the core read/publish workflow is covered, basic management operations like updating or deleting entries would require more tools.
The surface lacks update, delete, and list-own-drafts operations, which are standard for a changelog domain. An agent asked to edit a published entry or manage drafts would hit a dead end.
Publish and update your startup on BetaFinds from an AI agent — listings, changelog, releases.
Release notes and changelogs from across the web, indexed for agents. Also via CLI and REST API.
Changelogs for coding agents: versions, breaking changes, migrations. Free changelog-to-JSON.
Publish blog posts, send newsletters and emails from Claude, Claude Code, Codex and ChatGPT.
