Apple Watch Health MCP Server

Welcome! This repository contains the complete and final source code for the blog post, "Unlock Your LLM's Potential: Building an MCP Server with Elasticsearch for Real Health Data". Exposed over MCP by the apple watch health mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration

You will need one environment variable: ES_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you begin, ensure you have the following installed and running: * Python 3.10+ * Elasticsearch: An instance of Elasticsearch 8.x running locally at http://localhost:9200. * Claude Desktop: The MCP client we will use to interact with the server. * uv : For managing Python packages.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by salgado; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Apple Watch Health MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the apple watch health mcp mcp server does with a few real requests.