F
licenseNot graded
qualityB
maintenanceMCP server for Roku BrightScript documentation and device control, enabling doc search, device introspection, keypress/keysequence input, app launch, and sideloading.
-
roku-dev-doc-mcp
by artemisaiev
Related Servers
Alternatives to roku-dev-doc-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceProvides local cached access to PaperMC documentation with full-text search, category browsing, and update detection.-
- AlicenseAqualityBmaintenanceAll-in-one developer tool and MCP Server for Roku development, featuring ECP device control, automated channel sideloading, BrightScript debugging, and real-time log monitoring.5131MIT
- AlicenseAqualityCmaintenanceEnables Roku development workflows by creating projects, searching BrightScript APIs, validating and packaging channels, running script tests, and capturing headless SceneGraph or Draw2D previews.776 npmMIT
- FlicenseAqualityDmaintenanceScrapes, stores, and searches documentation locally, enabling AI assistants to access and query documentation via MCP.114-
- FlicenseNot gradedqualityBmaintenanceLocal documentation search server for AI models using hybrid retrieval (phrase, keyword, vector). Provides MCP tools to search and fetch documentation from bundled or custom doc sets without any external API keys.-
TDQS
A4.4/5.0
Scored across 4 tools
Disambiguation5/5
Each tool has a distinct role: search (query), get (fetch by path), list (browse tree), refresh (sync index). There is no overlap or ambiguity between them.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern with snake_case: search_, get_, list_, refresh_. The singular 'doc' for get_roku_doc is a natural contrast to the plural forms and matches the single-page return.
Tool Count5/5
Four tools is well-scoped for a documentation MCP server, covering discovery, retrieval, and maintenance without unnecessary sprawl or redundancy.
Completeness5/5
The tool surface fully covers the core workflow: browse (list), search (search), read (get), and keep the index current (refresh). There are no obvious gaps for a documentation access server.
Maintenance
ActivityMaintained
ResponsivenessNo issues