Skip to main content
Glama
StormXX

rive-docs-mcp

by StormXX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to rive-docs-mcp

No user-submitted related servers found.

    Related Servers

    • Godot MCP Documentation Server

      banned104
      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

    • 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

    • GovBR-DS MCP

      FelipeVergaraChico
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to access and utilize GovBR Design System documentation, including component details, accessibility guidance, and search functionality via Model Context Protocol.
      3
      6 npm
      MIT

    • neon

      universal-mcp
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides a standardized interface for interacting with Neon's tools and services through a unified API via the Model Context Protocol.
      MIT

    • Figma MCP Server

      MatthewDailey
      F
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to interact with Figma files through the ModelContextProtocol, allowing viewing, commenting, and analyzing Figma designs directly in chat interfaces.
      5
      1,634 npm
      213
      -
    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

    A4/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct documentation need: search, content retrieval, runtime listing, runtime guides, editor features, tutorials, feature support checks, and API references. No two tools appear to serve the same purpose.

    Naming Consistency5/5

    All tool names follow the same snake_case verb_noun pattern (search_, get_, list_, check_). The verbs and objects are clearly structured, making the API easy to predict.

    Tool Count5/5

    With 8 tools, the server is well-scoped for a documentation-focused MCP. Each tool covers a meaningful aspect of documentation access without redundancy or bloat.

    Completeness5/5

    The tool set covers the full documentation lifecycle: discovery (search, tutorials), detailed content (get_rive_doc_content, get_runtime_guide, get_api_reference), and reference data (list_runtimes, list_editor_features, check_feature_support). No significant gaps are apparent.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources