rive-docs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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". |
| 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. |
| 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. |
| get_runtime_guideA | Get comprehensive implementation guide for a specific Rive runtime. Includes setup instructions, code examples, and best practices. |
| list_editor_featuresB | Browse Rive editor features and capabilities. Shows tools, constraints, animation features, and design capabilities available in the Rive editor. |
| get_tutorialsA | Find and access Rive tutorials by topic, difficulty, or runtime. Great for learning specific features or implementation patterns. |
| check_feature_supportA | Check which Rive features are supported across different runtime platforms. Useful for planning cross-platform implementations. |
| get_api_referenceB | Get API reference documentation for a specific Rive runtime. Shows available classes, methods, properties, and usage examples. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
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.
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.
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.
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.