Skip to main content
Glama
Shawn Core MCP

Shawn Core MCP

by nawnie

Related Servers

Alternatives to Shawn Core MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables local-first document versioning with content-addressable storage, word-level AST diffs, and AI-compliance auditing for LLM agents.
      6
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables coding agents to maintain local-first project memory, coordinate task ownership across Git worktrees, and verify completion against project-defined checks with durable evidence stored in the repository.
      Apache 2.0
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to read a project's kickoff card, acceptance criteria, AGENTS rules, handoff package, progress, Git trail, and next step, then append validated, audited, idempotent progress events that are recorded as a matching Git commit. This keeps project truth in Git so work stays visible, resumable, and safely handable between humans and agents through scoped, short-lived credentials.
      -

    TDQS

    A3.5/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a clearly distinct function: orchestration context vs routing, git snapshot vs commit, changelog intake vs finalize, plus audit and continuity recording. There is no meaningful overlap or ambiguity between the tools.

    Naming Consistency3/5

    All names use snake_case with useful domain prefixes, but the second element mixes nouns and verbs: orchestrator_context, changelog_intake, and personal_git_snapshot are noun-style, while orchestrator_route and changelog_finalize are verb-style. The pattern is readable but not consistently verb_noun.

    Tool Count5/5

    Eight tools is a well-scoped size for the apparent domain of personal orchestration, git snapshots/commits, changelog handling, and continuity tracking. Each tool represents a meaningful capability without excessive fragmentation.

    Completeness4/5

    The main workflows are covered: routing and context for orchestration, git snapshot and commit for local changes, changelog intake and finalize for task closure, and a continuity record. Minor gaps exist around updating/reading registry or continuity artifacts, but core workflows have no dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues