Filesystem vs RokuMCP
A side-by-side look at the Filesystem and RokuMCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Filesystem for file systems work as a local process; choose RokuMCP for home automation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Filesystem when
- You need dedicated capabilities in the File Systems domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
path, head, tail.
Choose RokuMCP when
- You need dedicated capabilities in the Home Automation domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
ROKU_DEVICE_HOST, ROKU_DEVICE_PASSWORD. - You want tools like
roku_deploy, roku_delete_dev_channel, roku_discover.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | File Systems | Home Automation |
| Quality signal | 85/100 · Excellent | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | ROKU_DEVICE_HOSTROKU_DEVICE_PASSWORD |
| Verified owner | Verified | Community listing |
| GitHub stars | 91,540 | 4 |
| Directory activity | 11 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 17 | 42 |
| Full listing | View Filesystem | View RokuMCP |
Tools & capabilities
Filesystem tools 17
pathheadtailpathscontenteditsoldTextnewTextdryRunsortBysourcedestination- +5 more on the listing page
RokuMCP tools 42
roku_deploySideload (deploy) a Roku application to the device. Packages all files in the project directory and uploads them. A dev channel must not already be running, or it will be replaced.roku_delete_dev_channelDelete the currently sideloaded developer channel from the Roku device.roku_discoverScan the local network for Roku devices using SSDP discovery. Returns a list of all found devices with their IP addresses.roku_keypressSend a single key press to the Roku device via ECP. Common keys: Home, Rev, Fwd, Play, Select, Left, Right, Down, Up, Back, InstantReplay, Info, Backspace, Search, Enter, Lit_<character>roku_keypress_sequenceSend a sequence of key presses to the Roku device with an optional delay between each press.roku_launchLaunch or deep-link into a channel on the Roku device. Use appId "dev" for the sideloaded developer channel.roku_query_device_infoQuery the Roku device for its info: model, firmware version, serial number, network info, etc.roku_query_active_appQuery the currently active (foreground) app on the Roku device.roku_query_app_uiGet the current app UI tree as XML. Only works when a sideloaded dev channel is running.roku_query_sg_nodesQuery SceneGraph nodes on the Roku device. Use type "all" for all nodes, "roots" for root nodes, or "node" with a nodeId to inspect a specific node.roku_type_textType a text string into the currently focused text field on the Roku device. Each character is sent as an individual Lit_ keypress. Use this for search fields, email inputs, password fields, etc.roku_query_media_playerQuery the media player state on the Roku device. Returns playback state (play, pause, buffer, stop, none), position, duration, and error info. Use this to verify video playback in tests.- +30 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Filesystem
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem"
]
}
}
}
RokuMCP
{
"mcpServers": {
"rokumcp": {
"command": "npx",
"args": [
"-y",
"roku-mcp"
],
"env": {
"ROKU_DEVICE_HOST": "YOUR_ROKU_DEVICE_HOST_HERE",
"ROKU_DEVICE_PASSWORD": "YOUR_ROKU_DEVICE_PASSWORD_HERE"
}
}
}
}
Frequently asked questions
Filesystem is categorized under File Systems and uses a local stdio subprocess. RokuMCP belongs to Home Automation and uses a local stdio subprocess. Pick Filesystem for file systems work and RokuMCP for home automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Filesystem is listed as free. Auth: no auth required. RokuMCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add filesystem and rokumcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Filesystem has a quality signal of 85/100 (Excellent) with 11 views, 0 installs and 91,540 GitHub stars. RokuMCP has 63/100 (Good) with 1 views, 0 installs and 4 GitHub stars.