Skip to main content
Glama
rive-docs-mcp
by StormXX

Rive Docs MCP - Rive Documentation Model Context Protocol Server

License: MIT

Rive Documentation MCP Server - Access Rive's animation documentation, runtime guides, editor features, and tutorials through Model Context Protocol. Search animations, state machines, runtime implementations, and editor capabilities across web, mobile, and game platforms. Get instant access to React, Flutter, Unity integration guides, and complete API references directly in Claude, Cursor, or any MCP-compatible AI assistant.

✨ Features

  • šŸ” Smart Search: Intelligent search across Rive documentation for animations, runtimes, editor features, and guides

  • šŸ“š Complete Documentation Access: Full access to Rive's documentation for all runtime platforms

  • šŸŽ® Multi-Platform Support: Web, React, Flutter, iOS, Android, Unity, Unreal Engine, and more

  • šŸŽØ Editor Features: Browse animation tools, constraints, state machines, bones, and timeline features

  • šŸ“‹ Runtime Guides: Comprehensive implementation guides for all supported platforms

  • šŸŽÆ Tutorial Access: Find and access tutorials by topic, difficulty, or runtime platform

  • šŸ”§ API References: Complete API documentation for runtime-specific implementations

  • ⚔ High Performance: Optimized with caching and concurrent request handling

  • 🌐 Feature Support Matrix: Check feature compatibility across different runtime platforms

  • šŸš€ Developer Friendly: Built for AI-powered development workflows

Related MCP server: Godot MCP Documentation Server

šŸš€ Quick Start

Add this to your Claude Desktop configuration:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\\Claude\\claude_desktop_config.json

{
  "mcpServers": {
    "rive-docs": {
      "command": "node",
      "args": ["path/to/rive-docs-mcp/dist/index.js"]
    }
  }
}

Local Development

  1. Clone and build the project:

git clone <repository-url>
cd rive-docs-mcp
npm install
npm run build
  1. Test the server:

npm start

šŸ“¦ Installation

Claude Code

# Add as MCP server
claude mcp add rive-docs -- node path/to/rive-docs-mcp/dist/index.js

Cursor

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "rive-docs": {
      "command": "node",
      "args": ["path/to/rive-docs-mcp/dist/index.js"]
    }
  }
}

Other MCP Clients

The server works with any MCP-compatible client. Use the command:

node path/to/rive-docs-mcp/dist/index.js

šŸ› ļø Available Tools

šŸ” search_rive_docs

Search Rive documentation across all categories.

Parameters:

  • query (required): Search terms (e.g., "React runtime", "state machine events")

  • category: Filter by category (all, runtimes, editor, game-runtimes, tutorials)

  • runtime: Filter by specific runtime platform

  • limit: Max results (default: 10, max: 50)

Example:

search_rive_docs query="React animation setup" category="runtimes" limit=5

šŸ“– get_rive_doc_content

Get detailed content from a specific Rive documentation page.

Parameters:

  • url (required): Full Rive documentation URL

  • includeCode: Include code examples (default: true)

  • includeLinks: Include related links (default: false)

  • maxLength: Max content length (default: 10000)

Example:

get_rive_doc_content url="https://rive.app/docs/runtimes/react/getting-started"

šŸƒ list_runtimes

List all available Rive runtime platforms.

Parameters:

  • platform: Filter by platform type (all, web, mobile, game)

  • status: Filter by status (all, stable, beta, community)

  • includeDetails: Include detailed information (default: true)

šŸ“‹ get_runtime_guide

Get comprehensive implementation guide for a specific runtime.

Parameters:

  • runtime (required): Runtime platform (web, react, flutter, unity, etc.)

  • section: Specific section (getting-started, setup, api-reference)

  • includeExamples: Include code examples (default: true)

šŸŽØ list_editor_features

Browse Rive editor features and capabilities.

Parameters:

  • category: Feature category (all, animation, constraints, state-machines)

  • includeDetails: Include detailed descriptions (default: true)

šŸŽ“ get_tutorials

Find tutorials by topic, difficulty, or runtime.

Parameters:

  • topic: Tutorial topic or search term

  • difficulty: Filter by difficulty (all, beginner, intermediate, advanced)

  • runtime: Filter by runtime platform

  • limit: Max tutorials to return (default: 10)

āœ… check_feature_support

Check feature support across runtime platforms.

Parameters:

  • feature (required): Feature to check (e.g., "state machines", "bones")

  • runtime: Specific runtime to check (optional)

šŸ“š get_api_reference

Get API reference for a specific runtime.

Parameters:

  • runtime (required): Runtime platform

  • className: Specific class/component name (optional)

  • includeExamples: Include usage examples (default: true)

šŸ’” Usage Examples

Search for React Integration

search_rive_docs query="React component setup" category="runtimes" runtime="react"

Get Flutter Getting Started Guide

get_runtime_guide runtime="flutter" section="getting-started"

Find State Machine Tutorials

get_tutorials topic="state machine" difficulty="beginner"

Check Unity Feature Support

check_feature_support feature="timeline events" runtime="unity"

Browse Animation Features

list_editor_features category="animation"

šŸŽÆ Supported Runtimes

App Runtimes

  • Web (JavaScript) - Browser-based animations

  • React - React component integration

  • React Native - Mobile React applications

  • Flutter - Cross-platform mobile apps

  • iOS - Native iOS applications (Swift)

  • Android - Native Android applications (Kotlin/Java)

Game Runtimes

  • Unity - Unity game engine (C#)

  • Unreal Engine - Unreal Engine (C++)

  • Defold - Defold game engine (Lua)

Community Runtimes

  • C# - .NET applications

  • Qt/QtQuick - Qt applications

šŸ”§ Development

Build Commands

# Install dependencies
npm install

# Build TypeScript
npm run build

# Development mode (watch)
npm run dev

# Run tests
npm test

# Lint code
npm run lint

# Clean build
npm run clean

Project Structure

src/
ā”œā”€ā”€ index.ts              # Main MCP server
ā”œā”€ā”€ tools/                # Tool implementations
│   ā”œā”€ā”€ definitions.ts    # Tool definitions
│   ā”œā”€ā”€ handlers.ts       # Tool handlers
│   ā”œā”€ā”€ search.ts         # Search functionality
│   └── doc-fetcher.ts    # Document fetching
ā”œā”€ā”€ utils/                # Utilities
│   ā”œā”€ā”€ constants.ts      # Configuration constants
│   ā”œā”€ā”€ http-client.ts    # HTTP client
│   ā”œā”€ā”€ cache.ts          # Caching system
│   ā”œā”€ā”€ logger.ts         # Logging utility
│   ā”œā”€ā”€ error-handler.ts  # Error handling
│   ā”œā”€ā”€ content-extractor.ts  # Content extraction
│   └── navigation-crawler.ts # Navigation discovery
└── types/                # TypeScript types
    └── index.ts          # Type definitions

šŸ“ˆ Performance

  • Caching: TTL-based caching for documentation content, search results, and navigation

  • Rate Limiting: Built-in rate limiting to respect Rive's servers

  • Concurrent Requests: Limited concurrent requests for optimal performance

  • Error Handling: Comprehensive error handling with retry logic

  • Memory Management: Efficient memory usage with cache size limits

šŸ¤ Contributing

  1. Fork the repository

  2. Create a feature branch (git checkout -b feature/amazing-feature)

  3. Commit your changes (git commit -m 'Add amazing feature')

  4. Push to the branch (git push origin feature/amazing-feature)

  5. Open a Pull Request

šŸ“„ License

This project is licensed under the MIT License - see the LICENSE file for details.

šŸ™ Acknowledgments

  • Rive for creating an amazing animation platform

  • Anthropic for the Model Context Protocol

  • The Rive community for excellent documentation and resources


Made with ā¤ļø for the Rive animation community

Available Tools

8 tools
check_feature_supportA

Check which Rive features are supported across different runtime platforms. Useful for planning cross-platform implementations.

Inputs: feature (required), runtime.

get_api_referenceB

Get API reference documentation for a specific Rive runtime. Shows available classes, methods, properties, and usage examples.

Inputs: runtime (required), className, includeExamples.

get_rive_doc_contentA

Get detailed content from a specific Rive documentation page. Use this after search_rive_docs to get complete implementation details, code examples, and step-by-step guides.

Inputs: url (required), maxLength, includeCode, includeLinks.

get_runtime_guideA

Get comprehensive implementation guide for a specific Rive runtime. Includes setup instructions, code examples, and best practices.

Inputs: runtime (required), section, includeExamples.

get_tutorialsA

Find and access Rive tutorials by topic, difficulty, or runtime. Great for learning specific features or implementation patterns.

Inputs: limit, topic, runtime, difficulty.

list_editor_featuresB

Browse Rive editor features and capabilities. Shows tools, constraints, animation features, and design capabilities available in the Rive editor.

Inputs: category, includeDetails.

list_runtimesA

List all available Rive runtime platforms with their details, status, and links. Essential for discovering which runtimes are available and their current support status.

Inputs: status, platform, includeDetails.

search_rive_docsA

Search Rive documentation for animations, runtimes, editor features, and guides. Best for finding specific features, implementation details, or troubleshooting. Use specific terms like "state machine", "timeline", "React runtime", or "bone constraints".

Inputs: query (required), limit, runtime, category.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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 recent community issues

    Related MCP Connectors

    Related MCP Servers

    • 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
    • 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
      Provides a standardized interface for interacting with Neon's tools and services through a unified API via the Model Context Protocol.
      MIT