Skip to main content
Glama
masondelan

Selvedge

by masondelan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Selvedge

No user-submitted related servers found.

    Related Servers

    • Projectmem

      riponcm
      A
      license
      A
      quality
      A
      maintenance
      Local-first memory layer for AI coding agents — captures issues, attempts, fixes, and decisions, and warns at git commit before you repeat a mistake.
      17
      235 PyPI
      823
      MIT

    • Drift MCP Server

      lilcipherx
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables intent-driven version control on top of Git, turning commits into auditable intents with prompts, AST deltas, and signatures, and providing tools for blame, context, replay, and verification.
      4
      MIT

    • gpp

      mahabubul470
      A
      license
      B
      quality
      A
      maintenance
      Version-control-native project memory for AI agents: an encrypted knowledge graph whose beliefs are staleness-checked deterministically against repo history — belief bisect names the commit that invalidated a fact, and agents write their own evidence-anchored beliefs via propose_belief. Also exposes changeset proposals and per-changeset token cost reporting; bridges to plain Git.
      2
      9
      2
      MIT
    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.2/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have clear, distinct purposes: logging changes, querying history, searching, and finding stale decisions. However, `diff` (entity history) and `history` (filtered history across entities) overlap somewhat—both return change history, differing mainly in scope and filtering. `blame` is distinct (latest change per entity) and `prior_attempts` is distinct (outcome-focused), but the overlap between diff/history could cause occasional misselection.

    Naming Consistency3/5

    Tool names are mostly two-word lowercase verbs or nouns (log_change, prior_attempts, stale_decisions), but the pattern is inconsistent: some are verb_noun (log_change, stale_decisions), others are single nouns (diff, blame, history, changeset, search). This mix of action-oriented and entity-oriented names breaks a strict pattern, though each name is still readable and intuitive.

    Tool Count5/5

    With 8 tools, the server is well-scoped for its domain (change logging and history management). Each tool serves a distinct purpose—recording events, querying history at different granularities, searching, proactive checks, and maintenance. No tool feels redundant, and the count is within the ideal range, making the surface manageable without overwhelming an agent.

    Completeness5/5

    The tool set covers the full lifecycle: logging changes (log_change), retrieving history (diff, history, blame), reconstructing changesets, searching, checking prior attempts before editing, and flagging stale decisions for revisit. It even supports renames, rejects, reverts, and supersedes, showing thorough coverage of decision evolution. No obvious missing operations like deleting events (likely intentionally immutable), and the stale_decisions tool closes the loop on maintenance, so the surface feels complete.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources