Skip to main content
Glama
willermo

diataxis-mcp-server

by willermo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to diataxis-mcp-server

No user-submitted related servers found.

    Related Servers

    • mcp-docs-tools

      rog0x
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides documentation generation and analysis tools for AI agents, including JSDoc generation, README analysis, changelog generation, API documentation, and code comment analysis.
      44 npm
      MIT

    • repo-ready

      temmeik
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes tools that scan a repository's manifests, CI workflows and layout to generate truthful AGENTS.md/CLAUDE.md agent instructions, then audit those docs for drift such as dead commands, undocumented scripts and CI mismatches. Enables agents to keep their own onboarding documentation accurate and CI-verifiable instead of hand-written and rotting.
      1
      MIT

    • MCP Docs Server

      Unlock-MCP
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides direct access to local documentation files through simple search and overview tools, enabling LLMs to query project-specific markdown documentation without requiring vector databases or RAG pipelines.
      MIT

    • project-lore-mcp

      tamas-fm
      A
      license
      Not graded
      quality
      A
      maintenance
      Routes coding agents to the most relevant project documentation (decisions, intent, constraints) with provenance and freshness, providing tools for task routing, knowledge search, and document context.
      35 npm
      MIT
    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

    B3.3/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a distinct purpose: auditing single pages, auditing multiple pages, classifying requests, planning sets, and suggesting refactorings. No two tools overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (audit_doc_page, audit_doc_tree, classify_doc_request, plan_doc_set, suggest_doc_refactor), making the naming predictable and clear.

    Tool Count5/5

    Five tools is an appropriate number for a focused documentation assistant covering audit, classification, planning, and refactoring. It is neither too few nor too many.

    Completeness5/5

    The tool set covers the core workflows for Diataxis documentation: auditing (single and tree), classification, initial planning, and refactoring. No obvious gaps are present for the intended domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources