Server Everything vs RokuMCP

A side-by-side look at the Server Everything and RokuMCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Server Everything logoServer EverythingOther Tools and Integrations · Local subprocess (stdio)MCP server that exercises all the features of the MCP protocol73GreatAuth: no auth requiredRokuMCP logoRokuMCPHome Automation · Local subprocess (stdio)MCP server for Roku device automation — deploy, ECP control, screenshots, and debug console63GoodAuth: not declared

Verdict: choose Server Everything for other tools and integrations 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?

Server Everything logoChoose Server Everything when

  • You need dedicated capabilities in the Other Tools and Integrations domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like echo, get-annotated-message, get-env.
Explore Server Everything

RokuMCP logoChoose 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.
Explore RokuMCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecServer Everything logoServer EverythingRokuMCP logoRokuMCP
CategoryOther Tools and IntegrationsHome Automation
Quality signal73/100 · Great63/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedROKU_DEVICE_HOSTROKU_DEVICE_PASSWORD
Verified ownerCommunity listingCommunity listing
GitHub stars91,5254
Directory activity 9 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools1642

Tools & capabilities

Server Everything tools 16

  • echoEchoes back the input string
  • get-annotated-messageDemonstrates how annotations can be used to provide metadata about content.
  • get-envReturns all environment variables, helpful for debugging MCP server configuration
  • get-header-paramsReturns its region argument and the Mcp-Param-Region HTTP header it arrived in. Demonstrates x-mcp-header (a 2026-07-28 Streamable HTTP client mirrors the argument into the header) and JSON Schema 2020-12 input and output schemas.
  • get-resource-linksReturns up to ten resource links that reference different types of resources
  • get-resource-referenceReturns a resource reference that can be used by MCP clients
  • get-structured-contentReturns structured content along with an output schema for client data validation
  • get-sumReturns the sum of two numbers
  • get-tiny-imageReturns a tiny MCP logo image.
  • gzip-file-as-resourceCompresses a single file using gzip compression. Depending upon the selected output type, returns either the compressed data as a gzipped resource or a resource link, allowing it to be downloaded in a subsequent request: during the current session for a 2025-era client, or for ten minutes at a minted URI on protocol version 2026-07-28.
  • trigger-list-changedSends a notifications/<list>/list_changed for the tool, prompt or resource list. On protocol version 2026-07-28 it is delivered on each subscriptions/listen stream that asked for that list; a 2025-era client receives it unsolicited.
  • trigger-log-messagesSends one log message at each logging level during the call. On protocol version 2026-07-28 only the messages at or above the level the request names in _meta (io.modelcontextprotocol/logLevel) are sent, and none if it names no level; a 2025-era client gets those at or above the level it set with logging/setLevel. Deprecated: logging is deprecated as of protocol version 2026-07-28.
  • +4 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.

Server Everything

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "modelcontextprotocol-server-everything": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-everything"
      ]
    }
  }
}

RokuMCP

mcpServers (Claude Desktop / Cursor)
{
  "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

Server Everything is categorized under Other Tools and Integrations and uses a local stdio subprocess. RokuMCP belongs to Home Automation and uses a local stdio subprocess. Pick Server Everything for other tools and integrations 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.

Server Everything 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 modelcontextprotocol-server-everything and rokumcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Server Everything has a quality signal of 73/100 (Great) with 9 views, 0 installs and 91,525 GitHub stars. RokuMCP has 63/100 (Good) with 1 views, 0 installs and 4 GitHub stars.