What is the key difference between Health Export Mcp and Repowise?

Health Export Mcp belongs to the Developer Tools category with local stdio execution, while Repowise belongs to the Developer Tools category with local stdio execution.

How do I install Health Export Mcp or Repowise in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Health Export Mcp and Repowise free or paid?

Health Export Mcp operates under a Free / Open Source model (No auth required). Repowise operates under a Freemium model (No auth required).

Which MCP server has more tools and community activity?

Health Export Mcp lists 6 tools with 3 views and 2 GitHub stars. Repowise lists 6 tools with 2 views and 4,929 GitHub stars.

Can I use both Health Export Mcp and Repowise together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

How do I install Health Export Mcp or Repowise in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are Health Export Mcp and Repowise free to use, or do they require API keys?

Health Export Mcp is listed under a Free / Open Source model with No auth required . Repowise operates under a Freemium model with No auth required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both Health Export Mcp and Repowise at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both io-github-philipad-health-export-mcp and repowise-dev-repowise as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Health Export Mcp has a Quality Score of 35 /100 ( Fair ) with 3 views, 0 installs, and 2 GitHub stars. Repowise holds a Quality Score of 55 /100 ( Good ) with 2 views, 0 installs, and 4,929 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Health Export Mcp vs Repowise

In-depth architectural comparison of the Health Export Mcp and Repowise 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

Developer Tools · Local stdio

Quality: 35/100 (Fair) | Auth: No auth required

Repowise

Developer Tools · Local stdio

Quality: 55/100 (Good) | Auth: No auth required

Verdict Summary: Choose Health Export Mcp if you need specialized Developer Tools tools running via a local process. Choose Repowise if your workspace requires Developer Tools integration with local subprocess execution. 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 Developer Tools 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.

Explore Health Export Mcp Details

Choose Repowise when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Freemium).
Primary tools included: Nine task-shaped MCP tools across 15 programming languages, Precomputes answers to common codebase questions with zero LLM calls, Defect-risk scoring validated on multiple repos and languages.

Feature & Specification Comparison

Specification	Health Export Mcp io.github.PhilipAD Developer Tools	Repowise repowise-dev Developer Tools
Summary	Query 190 Apple Health metrics from any MCP agent — zero-dependency, read-only, local-first.	Codebase intelligence for AI coding agents. Indexes a repo into a dependency graph, git history, defect-risk code health, auto-generated docs, and architectural decisions, served as 9 task-shaped MCP tools across 15 languages. Runs 100% local; hosted option available.
Category & Scope	Developer Tools

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

Repowise 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 Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "io-github-philipad-health-export-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "io-github-philipad-health-export-mcp"
      ],
      "env": {
        "HEALTH_DATA_DIR": "YOUR_HEALTH_DATA_DIR_HERE"
      }
    }
  }
}

Repowise Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "repowise-dev-repowise": {
      "command": "npx",
      "args": [
        "-y",
        "repowise-dev-repowise"
      ]
    }
  }
}

Frequently Asked Questions

Health Export Mcp is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Repowise belongs to Developer Tools using local stdio subprocess. Select Health Export Mcp when you need capabilities focused on developer tools and Repowise when you require tools for developer tools.

More alternatives to Health Export Mcp More alternatives to Repowise Developer Tools category hub