patchlog-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PATCHLOG_API_URL | No | Base URL for the Patchlog API. Defaults to https://patchlog.io. | https://patchlog.io |
| PATCHLOG_API_TOKEN | Yes | Your Patchlog API token from Settings > API Tokens. |
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 |
|---|---|
| list_projectsA | List the Patchlog projects the API token owns, with each project id, name, slug, public changelog URL, and entry count. |
| list_entriesA | List changelog entries for a project. By default only live published entries are returned; pass status "draft" for drafts or "all" for everything including scheduled entries. |
| get_entryA | Fetch a single changelog entry by id, including its Markdown content and status. |
| create_entryA | Create a changelog entry in a project. Defaults to a draft; pass status "published" to go live immediately, or "published" with a future published_at to schedule it. Content is Markdown. |
| update_entryA | Update fields of an existing entry. Only the fields you pass are changed. Setting status back to draft unpublishes the entry. |
| publish_entryA | Publish a draft or scheduled entry right now. An entry that is already live keeps its original publish date. |
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 6 tools
The tools cleanly separate project listing from entry operations, and get/create/update have distinct roles. publish_entry overlaps slightly with update_entry's ability to change status, but its specific 'publish now' semantics are clearly differentiated.
All tools follow a consistent snake_case verb_noun pattern (list_, get_, create_, update_, publish_), making the set predictable and easy to navigate.
Six tools is appropriately scoped for a changelog management server. Each tool maps to a core operation without unnecessary redundancy.
The core entry lifecycle is covered: list, get, create, update, and publish. The only notable gap is a delete_entry tool, which would make lifecycle coverage complete.