Skip to main content
Glama
michaelyousrie

patchlog-mcp

by michaelyousrie
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to patchlog-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

    • logbook-mcp

      aether-technologies
      A
      license
      Not graded
      quality
      D
      maintenance
      A local MCP server for AI agents to log activities, query logs, and leave notes for each other, featuring a web UI and REST API.
      MIT

    • project-memory-mcp

      kaaustubh
      A
      license
      A
      quality
      A
      maintenance
      Local MCP server giving AI coding agents (Claude Code, Cursor, VS Code/JetBrains Copilot) a shared, persistent memory of your projects and every bug/issue faced during development. Stateless, plain-file storage (AGENTS.md + issues.jsonl) — no database.
      16
      37 npm
      1
      MIT

    • Minehut MCP

      Tobralla
      F
      license
      A
      quality
      B
      maintenance
      MCP server that lets AI agents fully manage Minehut Minecraft servers via Playwright browser automation and REST API tools, including server control, console commands, logs, and UI interactions.
      19
      1
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 6 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern (list_, get_, create_, update_, publish_), making the set predictable and easy to navigate.

    Tool Count5/5

    Six tools is appropriately scoped for a changelog management server. Each tool maps to a core operation without unnecessary redundancy.

    Completeness4/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources