brs-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 |
|---|---|
| list_templatesA | List every template bundled with this server. Returns metadata only; fetch a template's schema with get_template_schema. |
| get_template_schemaA | Return the JSON Schema (Draft 7) for a registered template's AppSpec, plus a minimal example spec. |
| generate_appB | Render a Roku channel project from a validated AppSpec and write it to output_dir. Set zip: true to also produce a sideload-ready archive at .zip. Set sideload: { device_ip, dev_password } to install the zip on a Roku device in developer mode (this implies zip: true). |
| package_appA | Zip an already-generated Roku project directory into a sideload-ready archive. Validates that project_dir contains a top-level |
| sideload_appA | Install a zip on a Roku device in developer mode via HTTP Digest-authenticated multipart POST to /plugin_install. Returns the parsed device response. dev_password is never logged or echoed. |
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 5 tools
Each tool has a clearly distinct purpose: generating a project, fetching schema, listing templates, packaging, and sideloading. No overlap exists.
All tool names follow a consistent verb_noun pattern in lowercase snake_case (generate_app, get_template_schema, list_templates, package_app, sideload_app), making the set predictable.
With 5 tools covering the core workflow of generating, packaging, and deploying Roku channels, the count is well-scoped and appropriate for the domain.
The tool surface covers the main lifecycle: template discovery, schema retrieval, project generation, packaging, and sideloading. A minor gap is the lack of a standalone validation tool, but generate_app implicitly validates the AppSpec.