Skip to main content
Glama
Kyoungwoong

Local DevLog MCP

by Kyoungwoong
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Local DevLog MCP

No user-submitted related servers found.

    Related Servers

    • Code Doctor

      PresentJay
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables reading agent-made changes in context by capturing Git diffs with verified task context, ordering every change into reading blocks, and recording versioned feedback so corrections can be steered with a short instruction. Exposes these capabilities as MCP tools alongside an optional loopback-only web review viewer.
      Apache 2.0
    • commit-check-mcp by commit-check

      commit-check-mcpofficial

      commit-check
      A
      license
      A
      quality
      A
      maintenance
      Enables validation of commit messages, branch names, author info, push safety, and repository state using commit-check rules, accessible as MCP tools.
      8
      46 PyPI
      1
      MIT

    • standup-pulse

      SanjoyDat1
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables generating AI-powered standups from git activity, with risk flags and markdown digests, via MCP tools.
      -
    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.8/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool targets a distinct action and resource: draft lifecycle, Notion publication, Calendar publication, and connectivity. The parallel Notion and Calendar tools are clearly separated by platform, and draft read/list/save/update/approve/preview/publish boundaries are explicit.

    Naming Consistency5/5

    Nearly all tools follow a predictable snake_case verb_noun pattern, with parallel naming for Notion and Calendar workflows. The only outlier is the simple connectivity tool `ping`, which is conventional and does not disrupt the pattern.

    Tool Count5/5

    Fifteen tools are well scoped for a local devlog workflow involving draft revisions, approval, Notion publication, and Calendar publication. Each tool appears to earn its place by covering a distinct lifecycle step or integration check.

    Completeness4/5

    The surface covers the core daily-draft lifecycle and mirrors publication pipelines for both Notion and Calendar with validation, preview, publish, and status tools. A minor gap is the lack of explicit task selection/discovery tools despite preview referencing selected Tasks, and retry handling is only implied through status.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources