Skip to main content
Glama
miroslawfranek

Open-E JovianDSS REST API Documentation MCP Server

Related Servers

Alternatives to Open-E JovianDSS REST API Documentation MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Exposes Swagger/OpenAPI API documentation to AI models, enabling exploration, search, and interaction with endpoints, schemas, and execution of API calls.
      14
      8 npm
      2
      MIT
    • A
      license
      D
      quality
      D
      maintenance
      A Model Context Protocol server that enables LLMs to explore and interact with API specifications by providing tools for loading, browsing, and getting detailed information about API endpoints.
      4
      15 npm
      14
      ISC
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides STORES API documentation to AI clients, enabling natural language queries about endpoints, authentication, and more.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI tools to search and explore API documentation from Apidog projects or OpenAPI/Swagger specifications, providing endpoint details, schemas, and project statistics through natural language queries.
      735 npm
      1
      ISC
    • A
      license
      A
      quality
      D
      maintenance
      Provides AI assistants with direct access to the complete Godot Engine documentation, including classes, tutorials, and features. It enables developers to retrieve and analyze official documentation through natural language interfaces using the Model Context Protocol.
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that fetches detailed API documentation from a local platform using a document ID. It enables language models to retrieve specific endpoint specifications to assist with tasks like code generation and API integration.
      35 npm
      ISC

    TDQS

    A3.5/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct action on documentation: discovering, downloading, retrieving, searching, analyzing endpoints, and comparing versions. No two tools have overlapping purposes.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with underscores (e.g., discover_documentation_links, download_edss_documentation). No deviations or mixed conventions.

    Tool Count5/5

    7 tools is well-scoped for a documentation retrieval and analysis server. Each tool serves a clear need without unnecessary duplication.

    Completeness4/5

    Covers core documentation lifecycle: discovery, download, retrieval, search, analysis, and comparison. A minor gap is the absence of a tool for direct endpoint viewing, but search and analysis effectively address this.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues