Skip to main content
Glama
alekspetrov

MCP Documentation Service

by alekspetrov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to MCP Documentation Service

No user-submitted related servers found.

    Related Servers

    • DevDocs MCP

      llmian-space
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol implementation that enables AI-powered access to documentation resources, featuring URI-based navigation, template matching, and structured documentation management.
      9
      MIT

    • Document MCP Server

      mparth14
      F
      license
      B
      quality
      D
      maintenance
      Provides tools and resources for managing in-memory documents, allowing users to read, edit, and list document contents via the Model Context Protocol. It includes features for formatting documents to Markdown and accessing document-specific resources.
      3
      -

    • MCP Notes Server

      sixbenzene
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to manage Markdown notes via the Model Context Protocol, supporting creation, editing, searching, and conflict detection.
      MIT

    • Memory Bank MCP

      hoppo-chan
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol plugin that helps AI assistants maintain persistent project context through structured markdown files, providing a systematic approach to tracking project goals, decisions, progress, and patterns.
      3
      43 npm
      16
      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.5/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool has a distinct purpose with clear boundaries: health checking, creation, editing, listing, moving, reading, renaming, searching, updating navigation, and validation. No tools appear to overlap in functionality, making it easy for an agent to select the correct one.

    Naming Consistency5/5

    All tools follow a consistent verb_noun naming pattern (e.g., check_documentation_health, create_documentation_section, edit_document). This uniformity enhances readability and predictability for agents.

    Tool Count5/5

    With 14 tools, the server is well-scoped for documentation management, covering a comprehensive range of operations from CRUD to validation and navigation. Each tool serves a specific, necessary function without redundancy.

    Completeness5/5

    The tool set provides complete coverage for documentation lifecycle management, including creation, reading, updating, deletion (via move/rename/overwrite), validation, and navigation. There are no obvious gaps that would hinder agent workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources