RokuMCP vs Tapo MCP
A side-by-side look at the RokuMCP and Tapo MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose RokuMCP for home automation work as a local process; choose Tapo MCP 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 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.
Choose Tapo MCP when
- You need dedicated capabilities in the Home Automation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You have the keys it needs:
TAPO_USERNAME, TAPO_PASSWORD, IP_ADDRESS.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Home Automation | Home Automation |
| Quality signal | 53/100 · Good | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | other |
| Pricing | Not declared | Free |
| Required env vars | ROKU_DEVICE_HOSTROKU_DEVICE_PASSWORD | TAPO_USERNAMETAPO_PASSWORDIP_ADDRESS |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 855 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 38 | Not listed |
| Full listing | View RokuMCP | View Tapo MCP |
Tools & capabilities
RokuMCP tools 38
roku_deploySideload (deploy) a Roku app to the deviceroku_delete_dev_channelDelete the currently sideloaded developer channelroku_discoverScan the local network for Roku devices via SSDProku_keypressSend a single key press (Home, Select, Up, Down, Left, Right, Back, etc.)roku_keypress_sequenceSend multiple key presses in sequence with configurable delayroku_type_textType a text string into the focused field (e.g. email, password, search)roku_launchLaunch or deep-link into a channelroku_query_device_infoGet device model, firmware, serial number, network inforoku_query_active_appGet the currently running approku_query_media_playerGet media player state (play/pause/buffer/stop), position, and durationroku_query_app_uiGet the current app UI tree as XMLroku_query_sg_nodesQuery SceneGraph nodes (all, roots, or by node ID)- +26 more on the listing page
Tapo MCP tools
No tool names declared yet. Check the project README from 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.
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"
}
}
}
}
Tapo MCP
{
"mcpServers": {
"tapo-mcp": {
"command": "uvx",
"args": [
"tapo"
],
"env": {
"TAPO_USERNAME": "YOUR_TAPO_USERNAME_HERE",
"TAPO_PASSWORD": "YOUR_TAPO_PASSWORD_HERE",
"IP_ADDRESS": "YOUR_IP_ADDRESS_HERE"
}
}
}
}
Frequently asked questions
RokuMCP is categorized under Home Automation and uses a local stdio subprocess. Tapo MCP belongs to Home Automation and uses a local stdio subprocess. Pick RokuMCP for home automation work and Tapo MCP 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.
RokuMCP has no declared pricing — check the project's own site. Tapo MCP is listed as free. Auth: other. 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 rokumcp and tapo-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, RokuMCP has a quality signal of 53/100 (Good) with 0 views, 0 installs and 3 GitHub stars. Tapo MCP has 49/100 (Fair) with 3 views, 0 installs and 855 GitHub stars.