Skip to main content
Glama
dwsmorg

@dwsm/changelog-mcp

by dwsmorg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to @dwsm/changelog-mcp

No user-submitted related servers found.

    Related Servers

    • changelog-mcp

      smartsys
      A
      license
      A
      quality
      C
      maintenance
      A universal MCP server that enables AI assistants to safely manage changelog files by writing structured records to a JSONL store and deterministically generating markdown changelogs.
      15
      MIT

    • MCP Memory Server

      keleshteri
      A
      license
      B
      quality
      D
      maintenance
      Gives AI coding assistants persistent memory, safety controls, and project awareness by tracking coding sessions, protecting critical files from modifications, and managing approval workflows with automatic changelog generation.
      19
      21 npm
      MIT
    • fizlog-mcp by firmalemony

      fizlog-mcpofficial

      firmalemony
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants like Claude and Cursor to publish, schedule, or save changelog entries as drafts, delivering them to an in-app widget, public changelog page, and RSS feed with optional subscriber email. It can also read recent published entries so assistants can summarize releases or avoid duplicates.
      2
      28 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.7/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: adding entries, configuration, version reading, entry retrieval, next version calculation, initialization, preview, and search. No two tools overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (e.g., add_entry, get_config, search_changelog), making them predictable and easy to understand.

    Tool Count5/5

    With 8 tools, the server covers all core changelog operations (init, add, read, search, version management) without being bloated or too minimal. The count is well-scoped for its purpose.

    Completeness4/5

    The tool set covers essential workflows (init, add, read, preview, search, version handling). It intentionally omits update/delete (append-only design). A minor gap is the lack of a list-all-versions tool, but search can compensate.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources