Skip to main content
Glama
mohit716

jev-docs-mcp

by mohit716
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to jev-docs-mcp

No user-submitted related servers found.

    Related Servers

    • mcp_for_agents

      chineidu
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables building local, offline MCP servers that expose open-source package documentation to AI agents, with tools to list doc sources, search docs, and retrieve doc content over stdio.
      MIT

    • MCP Framework Documentation

      QuantGeekDev
      A
      license
      A
      quality
      D
      maintenance
      Provides tools for AI agents to search, browse, and retrieve the full documentation for the mcp-framework. It enables agents to access documentation sections and page content directly within MCP-compatible environments like Claude Code and Cursor.
      3
      7 npm
      MIT

    • devdocs-mcp

      madhan-g-p
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides version-pinned, deterministic documentation sourced from DevDocs.io to AI assistants (Claude, RooCode, Cline, Copilot etc.) and also via offline mode. Not via Scraping! But using the supported downloading option from devdocs.
      49 npm
      13
      MIT

    • devdocs-mcp

      maxwhipw
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to search, install, read, and navigate DevDocs documentation offline via MCP, with token-efficient search/read/toc tools and local caching.
      6
      8 npm
      1
      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

    A4.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: list enumerates all pages, search performs full-text lookup, and read fetches full page content. The descriptions explicitly clarify how they differ, leaving no realistic ambiguity.

    Naming Consistency5/5

    All three tools follow the same predictable pattern: jev_docs_ prefix plus a consistent verb (list, search, read). There is no mixing of conventions.

    Tool Count5/5

    Three tools is a well-scoped minimal set for a documentation server: discover, search, and read. Each tool earns its place without redundancy.

    Completeness5/5

    The surface covers the full read-only documentation lifecycle: discovery via list, targeted lookup via search, and full content retrieval via read with pagination support. No obvious gaps remain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources