All plugins

davidmosiah

GitHub profile5 plugins in the catalog3

Plugins by davidmosiah

5 plugins by davidmosiah in the catalog, most-starred first.

davidmosiahapple-health-mcpRead the user's Apple Health export (workouts, steps, heart rate, HRV, sleep, cycle tracking) through the local apple-health MCP server. Portable Agent Plugins v1 package (mcp.json + skills/). Disclosure — Runs the `apple-health-mcp-unofficial@0.8.0` npm package locally over stdio through `npx` (Node.js 20+ required); the package and its dependencies are downloaded from npm on first start. Data source: no network service: it parses the user's own Apple Health export on disk (the connector's `setup --auto-import` looks for exports in ~/Downloads, ~/Desktop and ~/Documents and copies them under `~/.apple-health-mcp/`). It also keeps a wellness profile shared with the author's other connectors at `~/.delx-wellness/profile.json`, and its connection-status tool reads `~/.hermes/config.yaml` to check for an MCP block. Tools that change state: apple_health_profile_update (local profile only); apple_health_reimport (re-reads the local export); apple_health_clear_incremental_cache (clears the local parsed cache). No live sync: data is as fresh as the last export the user imported. The tool set comes from the pinned npm version, not from this repository's source tree.Communitytools3davidmosiahdelx-recoveryFree recovery and continuity for agents through the hosted Delx Protocol MCP server (Streamable HTTP, no API key, no OAuth, no payment), with the delx-recovery-first-hour workflow skill bundled: triage an error loop or lost context, resume a prior session, capture state and context memory, seal a Continuity Capsule (goal/done/next/blockers/refuted) before compaction so the next session resumes warm, and turn failures into a recovery plan. Portable Agent Plugins v1 package (mcp.json + skills/); Hermes runs no code from it. Disclosure — hosted-only connector: every tool call, including the free-text problem description sent by public triage, goes to the remote server at api.delx.ai. Public triage needs no credential; private continuity uses a free agent credential returned at registration and passed as a tool argument. What the agent chooses to store (state, memory, capsules) is retained by Delx under its privacy policy, so do not send secrets. Requests carry ?src=plugin for channel attribution. The tool set is served by the remote server at runtime and is not covered by the pinned sha. The hooks/ shell scripts in the directory are opt-in Claude Code hooks that Hermes does not load.Communitytoolsdavidmosiahfitbit-mcpRead the user's Fitbit activity, heart rate, sleep and body data through the local fitbit MCP server. Portable Agent Plugins v1 package (mcp.json + skills/). Disclosure — Unofficial connector, not affiliated with Fitbit. Runs the `fitbit-mcp-unofficial@0.7.0` npm package locally over stdio through `npx` (Node.js 20+ required); the package and its dependencies are downloaded from npm on first start. Data source: the official Fitbit Web API. The user creates their own Fitbit developer app; its client ID and secret and the OAuth tokens are created by the connector's own `setup`/`auth` commands in the user's terminal, stored under `~/.fitbit-mcp/` and refreshed by the connector itself, and sent only to Fitbit's API; the plugin declares no environment variables and reads no Hermes credentials. It also keeps a wellness profile shared with the author's other connectors at `~/.delx-wellness/profile.json` (first run copies an existing `~/.hermes/profiles/delx-wellness/wellness-profile.json` there), and its connection-status tool reads `~/.hermes/config.yaml` to check for an MCP block. Tools that change state: fitbit_profile_update (local profile only); fitbit_exchange_code (stores OAuth tokens locally); fitbit_revoke_access (revokes the Fitbit grant and deletes local tokens). The tool set comes from the pinned npm version, not from this repository's source tree.Communitytoolsdavidmosiahoura-mcpRead the user's Oura Ring readiness, sleep, HRV and activity through the local oura MCP server. Portable Agent Plugins v1 package (mcp.json + skills/). Disclosure — Unofficial connector, not affiliated with Oura. Runs the `oura-mcp-unofficial@0.8.0` npm package locally over stdio through `npx` (Node.js 20+ required); the package and its dependencies are downloaded from npm on first start. Data source: the official Oura Cloud API v2. The user creates their own Oura developer app; its client ID and secret and the OAuth tokens are created by the connector's own `setup`/`auth` commands in the user's terminal, stored under `~/.oura-mcp/` and refreshed by the connector itself, and sent only to Oura's API; the plugin declares no environment variables and reads no Hermes credentials. It also keeps a wellness profile shared with the author's other connectors at `~/.delx-wellness/profile.json` (first run copies an existing `~/.hermes/profiles/delx-wellness/wellness-profile.json` there), and its connection-status tool reads `~/.hermes/config.yaml` to check for an MCP block. Tools that change state: oura_profile_update (local profile only); oura_exchange_code (stores OAuth tokens locally); oura_revoke_access (revokes the Oura grant and deletes local tokens). The tool set comes from the pinned npm version, not from this repository's source tree.Communitytoolsdavidmosiahwhoop-mcpRead the user's WHOOP recovery, HRV, sleep and strain through the local whoop MCP server. Portable Agent Plugins v1 package (mcp.json + skills/). Disclosure — Unofficial connector, not affiliated with WHOOP. Runs the `whoop-mcp-unofficial@0.7.0` npm package locally over stdio through `npx` (Node.js 20+ required); the package and its dependencies are downloaded from npm on first start. Data source: the official WHOOP OAuth API (v2). The user creates their own WHOOP developer app; its client ID and secret and the OAuth tokens are created by the connector's own `setup`/`auth` commands in the user's terminal, stored under `~/.whoop-mcp/` and refreshed by the connector itself, and sent only to WHOOP's API; the plugin declares no environment variables and reads no Hermes credentials. It also keeps a wellness profile shared with the author's other connectors at `~/.delx-wellness/profile.json` (first run copies an existing `~/.hermes/profiles/delx-wellness/wellness-profile.json` there), and its connection-status tool reads `~/.hermes/config.yaml` to check for an MCP block. Tools that change state: whoop_profile_update (local profile only); whoop_exchange_code (stores OAuth tokens locally); whoop_revoke_access (revokes the WHOOP grant and deletes local tokens). The tool set comes from the pinned npm version, not from this repository's source tree.Communitytools