Skip to main content
Glama
daveangulo

Twining MCP Server

by daveangulo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Twining MCP Server

No user-submitted related servers found.

    Related Servers

    • hive

      HusseinTaha
      A
      license
      C
      quality
      B
      maintenance
      Enables Claude Code agents and sub-agents to share a persistent, compiled memory of project state, decisions, tasks, and facts across sessions instead of re-reading transcripts. Provides token-efficient bootstrap, search, commit, leased task claiming, and task-specific context compilation so parallel agents can coordinate without clobbering each other.
      5
      292 npm
      MIT

    • engram

      devinmlowe
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code and other LLM agents to capture, consolidate, and retrieve memories from conversation history, building a local-first knowledge graph with semantic search and dream-state consolidation.
      1
      MIT

    • synco-mcp

      ijustseen
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables multiple AI coding agents to coordinate on a shared software project by registering, claiming tasks, declaring file intents, publishing structured change reports, and handing off context, with a local dashboard showing state in near real time.
      -

    • teamhub-mcp

      imortis
      A
      license
      A
      quality
      B
      maintenance
      Enables teams to share structured, git-synced context among AI coding agents working on the same repository, including living plans, task declarations, handoff briefs, file-provenance history, and conflict detection.
      12
      909 npm
      2
      MIT

    • context-atlas

      moelomda
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to query a local, versioned knowledge graph of a software project, retrieving overviews, context packs, evidence, and explanations to make informed changes.
      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

    A3.6/5.0

    Scored across 15 tools

    Disambiguation3/5

    Most tools have clear individual purposes, but several pairs overlap: twining_record and twining_post both handle status/finding posts, twining_archive and twining_archive_stale both archive items, and twining_housekeeping already includes orphan pruning alongside twining_prune_graph. The detailed descriptions help, but the repeated archive/record concepts plus references to absent twining_decide and twining_dismiss add ambiguity.

    Naming Consistency3/5

    All tools share the twining_ prefix, but conventions vary: bare verbs (record, post, resolve, why), verb_noun (prune_graph, add_entity, archive_stale), nouns (neighbors, status, housekeeping), and one reversed object-verb (graph_query). Readable, but not a consistent verb_noun pattern.

    Tool Count4/5

    At 15 tools the server is at the high end of a reasonable scope, and most tools cover a distinct maintenance/query/archive task. A few are arguably redundant (prune_graph vs. housekeeping, archive vs. archive_stale), so it is slightly over-packed but not bloated.

    Completeness2/5

    The server references twining_decide and twining_dismiss as the correct tools for decision creation and noise dismissal, but neither is exposed, leaving agents with a dead end. There are also no explicit delete/remove operations for entities or relations, only orphan pruning; combined with the archival asymmetry this creates significant gaps in the lifecycle.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources