fizlog-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIZLOG_API_KEY | Yes | Your Fizlog project API key (required for publish_entry). | |
| FIZLOG_BASE_URL | No | Base URL for self-hosted Fizlog instances. | https://fizlog.com |
| FIZLOG_PUBLIC_KEY | No | Your Fizlog public key (used as default for get_public_changelog). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| publish_entryA | 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, |
| get_public_changelogA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
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.