Skip to main content
Glama
nawnie

Shawn Core MCP

by nawnie
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Shawn Core MCP

No user-submitted related servers found.

    Related Servers

    • doc-version-mcp

      hjamet
      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

    • ContextCord MCP Server

      Yvniverse
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to keep project state, evidence, and decisions bound to the repository, and to resume work across sessions and hosts by receiving a bounded, revalidated context packet instead of a full transcript. It also lets agents record checkpoints, handoffs, and closeouts while keeping deterministic decision and routing authority in code.
      2
      Apache 2.0

    • Continuity

      cubiix3
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to maintain persistent project context locally, with source-backed memory and structured handoffs for seamless handover between interchangeable agents.
      Apache 2.0
    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.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

    ActivityMaintained
    ResponsivenessNo issues

    Resources