Skip to main content
Glama
Nezeronxer

ru-docs-mcp

by Nezeronxer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ru-docs-mcp

No user-submitted related servers found.

    Related Servers

    • telegram-dev

      Kay0k1
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to search, retrieve, and manage official Telegram documentation, helping them implement accurate Telegram features and verify API capabilities.
      MIT

    • Atlas Docs MCP Server

      CartographAI
      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
      9 npm
      36
      MIT

    • context

      rkostko-ops
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides up-to-date documentation for AI agents by locally querying a community-driven registry of pre-built docs packages.
      Apache 2.0

    • DevDocs MCP Server

      JavierDevCol
      F
      license
      A
      quality
      D
      maintenance
      Provides AI models with direct access to documentation for over 600 technologies from DevDocs.io, including popular languages, frameworks, and tools. It enables comprehensive searching, content retrieval, and offline access via an intelligent local caching system.
      12
      2
      -

    • mcp-1c-its

      VoskresenskiyAU
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to search and read 1C:ITS portal subscription materials, such as development standards, platform documentation, and configuration guides, returning content as Markdown with source links.
      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

    A3.7/5.0

    Scored across 3 tools

    Disambiguation4/5

    resolve_library is clearly distinct, while get_docs and get_gotchas overlap because get_docs already returns gotchas as its first block. The descriptions clarify the difference, but an agent may still hesitate when deciding whether to call get_docs or get_gotchas for trap information.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: resolve_library, get_docs, get_gotchas. The only variation is resolve vs get, which is minor and still predictable.

    Tool Count5/5

    Three tools are well-scoped for a documentation lookup server: resolve a library, fetch documentation, and fetch gotchas. Each tool earns its place, and the count is neither thin nor excessive.

    Completeness4/5

    The core workflow of resolving a library and then retrieving docs or gotchas is covered. Minor gaps exist, such as no explicit topic listing, cross-library search, or version metadata, but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources