Skip to main content
Glama

Related Servers

Alternatives to MCP Document Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      An MCP (Model Context Protocol) server for efficiently managing Markdown documents in Cursor AI IDE, supporting CRUD operations, search, and metadata management.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that semantically searches Markdown context files and extension context links, providing tools for context_search, context_read, and context_status.
      -
    • A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that provides a local-first RAG engine for your markdown documents. It uses a file-based Milvus vector database to index your notes, enabling LLMs to perform semantic search and retrieve relevant content from your local files.
      3
      61
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      A local dashboard and Model Context Protocol server for managing a multi-project portfolio whose entire state lives in markdown files.
      MIT

    TDQS

    D1.2/5.0

    Scored across 2 tools

    Disambiguation2/5

    The two tools 'add' and 'test_docs_path' have no descriptions, making their purposes unclear. 'add' is extremely vague and could refer to many operations, while 'test_docs_path' suggests a testing function, but without descriptions, it's impossible to determine if they overlap or serve distinct roles. The lack of clarity creates significant ambiguity.

    Naming Consistency2/5

    The tool names show inconsistency: 'add' uses a simple verb with no noun, while 'test_docs_path' uses a snake_case pattern with a verb-noun structure. This mixing of conventions (simple verb vs. descriptive snake_case) makes the naming unpredictable and chaotic, lacking a coherent pattern across the set.

    Tool Count2/5

    With only 2 tools and no descriptions, it's difficult to assess the server's purpose, but based on the server name 'MCP Document Server', this count feels too thin for a document management domain. A document server typically requires more operations (e.g., create, read, update, delete, search), making 2 tools insufficient and poorly scoped.

    Completeness1/5

    Inferred from the server name, a document server should cover basic CRUD operations and document lifecycle management. With only vague tools like 'add' and 'test_docs_path', there are severe gaps—no clear ways to retrieve, update, delete, or search documents. This surface is highly incomplete and will likely cause agent failures in handling document-related tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues