In-depth architectural comparison of the Health Export MCP and Roku Dev Studio MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Health Export MCP
Monitoring · Local stdio
Quality: 48/100 (Fair) | Auth: No auth required
Roku Dev Studio
Monitoring · Remote HTTP/SSE
Quality: 55/100 (Good) | Auth: No auth required
Verdict Summary: Choose Health Export MCP if you need specialized Monitoring tools running via a local process. Choose Roku Dev Studio if your workspace requires Monitoring integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Health Export MCP when:
You need dedicated capabilities in the Monitoring domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: HEALTH_DATA_DIR.
Primary tools included: Supports 190+ Apple Health metrics as clean JSON, Local-first, read-only access with no cloud or developer server, Zero dependencies, runs on Node.js 18 or higher.
You need dedicated capabilities in the Monitoring domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: ECP device control including keypresses, launches, and queries, Automated sideloading of development channels with Dev Password, BrightScript debugging via Telnet and RALE protocols.
Query 190 Apple Health metrics from any MCP agent — zero-dependency, read-only, local-first.
All-in-one developer tool and MCP Server for Roku development, featuring ECP device control, automated channel sideloading, BrightScript debugging, and real-time log monitoring.
Category & Scope
Tools & Capabilities Breakdown
Health Export MCP Tools (6)
Supports 190+ Apple Health metrics as clean JSON
Local-first, read-only access with no cloud or developer server
Zero dependencies, runs on Node.js 18 or higher
Compatible with multiple AI clients via MCP protocol
Includes 7 specialized MCP tools for health data queries
Works with Apple Health exports from iCloud, local folders, or LAN
Roku Dev Studio Tools (6)
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Health Export MCP is categorized under Monitoring and uses a local stdio subprocess. In contrast, Roku Dev Studio belongs to Monitoring using remote streaming HTTP/SSE transport. Select Health Export MCP when you need capabilities focused on monitoring and Roku Dev Studio when you require tools for monitoring.