Skip to main content
Glama
foundryside-dev

plainweave

by foundryside-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to plainweave

No user-submitted related servers found.

    Related Servers

    • Cordyceps Search

      ghassenTn
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables developer agents to perform semantic codebase search, dependency and impact analysis, cross-file refactoring, and full-stack API tracing through a unified query DSL over a high-performance graph engine.
      -

    • Codebase Knowledge Graph MCP

      jigneshsuvariya
      A
      license
      A
      quality
      D
      maintenance
      Enables storing and querying structured information about software code entities (classes, functions, files) and their relationships (calls, imports) along with qualitative observations like design decisions and change rationale.
      9
      3 npm
      5
      MIT

    • vibeframe

      jubayertalha
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables agentic coding tools to maintain a living, in-repo model of intent, architecture, and code, with deterministic indexing, bidirectional linking, and continuous drift detection for task-scoped context and reconciliation.
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    B3.4/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose within its domain (baselines, intents, requirements, etc.). Even similar-sounding tools like 'plainweave_verification_status_get' and 'plainweave_verification_status_list' are unambiguously differentiated by 'get' vs. 'list'.

    Naming Consistency5/5

    All tool names follow the consistent pattern 'plainweave_<area>_<action>[_<qualifier>]' using snake_case. Verbs like 'get', 'list', 'search', 'trace' are used predictably across areas.

    Tool Count4/5

    19 tools is slightly above the typical ideal range, but the domain covers multiple distinct sub-domains (baselines, intents, requirements, etc.), so the count is still reasonable and each tool serves a specific purpose.

    Completeness4/5

    The tool set is comprehensive for read operations: listing and getting baselines, intents, requirements, verification status, etc. However, it lacks write/create/update tools, which may be intentional for a read-only server, leaving minor gaps like intent search beyond corpus.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources