Skip to main content
Glama
onigetoc

MCP Context Master

by onigetoc

Related Servers

Alternatives to MCP Context Master

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Automatically provides AI assistants with contextual, version-specific documentation for Python project dependencies by scanning pyproject.toml files. Eliminates manual package lookup and enables more accurate coding assistance through seamless integration with AI tools.
      4
      1
      MIT
    • A
      license
      B
      quality
      F
      maintenance
      Automatically crawls documentation websites, converts them to organized markdown files, and generates condensed cheat sheets. Intelligently categorizes content into tools/APIs and provides local-first access to downloaded documentation.
      3
      GPL 3.0
    • A
      license
      A
      quality
      A
      maintenance
      Provides AI assistants with intelligent access to project documentation and API references through smart search, contextual rules, and Docset integration. Enables AI to understand project-specific conventions, patterns, and official framework documentation without token limits.
      11
      43 npm
      6
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Provides AI assistants with up-to-date documentation for popular libraries and frameworks, enabling them to generate more accurate code using less common or newly released libraries.
      5
      46 npm
      36
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Provides LLMs with up-to-date, version-specific documentation and code examples directly from library sources, eliminating outdated training data and hallucinated APIs by fetching current documentation at prompt time.
      2
      1,132,952 npm
      MIT

    TDQS

    A3.7/5.0

    Scored across 9 tools

    Disambiguation3/5

    Two listing tools (list_available_contexts and list_added_contexts_details) have overlapping descriptions, both listing knowledge files, though one includes metadata. The setup tools (initialize_context_master and setup_project_context) are sequential but clearly defined. Other tools target distinct actions, so overall ambiguity is moderate.

    Naming Consistency4/5

    Tool names consistently use snake_case verb-first pattern (search, initialize, setup, add, list, read, update). Minor inconsistencies: 'search_library_advisor' uses an agent-like noun rather than a resource, and 'list_added_contexts_details' is verbose. But the pattern is predictable and readable.

    Tool Count5/5

    9 tools is a well-scoped number for a context management server, covering setup, searching, adding, listing, reading, and updating. No redundant or excessive tools, and each earns its place.

    Completeness3/5

    The toolset covers setup, add, list, read, and update agents file, but lacks delete/remove context operations and any update mechanism for existing context entries. This creates a notable gap in lifecycle management, though the core workflow of adding and reading context is covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues