aimharder-mcp 0.1.0 → 0.1.1

package/README.md

@@ -1,8 +1,6 @@
 # aimharder-mcp
 
-Ask about your AimHarder classes, workouts, bookings and activity from a desktop AI client. This is a local, read-only [MCP server](https://modelcontextprotocol.io/) and an independent project, neither affiliated with nor endorsed by AimHarder.
-
-**Release status:** `aimharder-mcp@0.1.0` is not on npm yet. The `npx` example below will work after publication. A [local package archive has been tested](https://github.com/rudeayelo/aimharder-mcp/blob/main/docs/validation.md).
+Ask about your AimHarder classes, workouts, bookings and activity from an AI client. This is a local, read-only [MCP server](https://modelcontextprotocol.io/) and an independent project, neither affiliated with nor endorsed by AimHarder.
 
 **Data limits:** Live checks used one account at one location (9NBC). Other gyms may differ. Workout and booking views can be incomplete, so an empty result may not mean there is nothing to show. [Details](docs/tools.md#coverage-and-interpretation)
 
@@ -17,7 +15,7 @@ Ask about your AimHarder classes, workouts, bookings and activity from a desktop
      "mcpServers": {
        "aimharder": {
          "command": "npx",
-         "args": ["--yes", "aimharder-mcp@0.1.0"]
+         "args": ["--yes", "aimharder-mcp@0.1.1"]
        }
      }
    }
@@ -25,14 +23,15 @@ Ask about your AimHarder classes, workouts, bookings and activity from a desktop
 
 4. Ask your client an AimHarder question, such as “What is tomorrow's WOD?” The first valid tool call signs in. See the guide for your client below for its configuration format and credential options.
 
-## Desktop clients
+## Desktop and CLI clients
 
 - [ChatGPT desktop](docs/clients/chatgpt-desktop.md)
+- [Codex](docs/clients/codex.md)
 - [Claude Desktop](docs/clients/claude-desktop.md)
 - [Hermes](docs/clients/hermes.md)
 - [OpenClaw](docs/clients/openclaw.md)
 
-Hermes has been tested with a local package archive. The ChatGPT desktop STDIO form has been observed; package connections in ChatGPT, Claude Desktop and OpenClaw have not been verified. Mobile apps are outside the current setup guides.
+Hermes and Codex CLI have called the account tool through the published package. The ChatGPT desktop STDIO form has been observed; package connections in ChatGPT desktop, Claude Desktop and OpenClaw have not been verified. Mobile apps are outside the current setup guides.
 
 ## Tools
 

package/docs/clients/chatgpt-desktop.md

@@ -2,13 +2,13 @@
 
 Use this guide if your ChatGPT desktop app offers **Connect to a custom MCP → Type: STDIO**. The user observed this form on 2026-09-24; a connection with this package has **not been tested**. If the local STDIO option is absent, see your app's [remote MCP documentation](https://developers.openai.com/plugins/deploy/connect-chatgpt).
 
-`aimharder-mcp@0.1.0` is not yet published. First set up [Node 24+ and your account environment](../configuration.md).
+First set up [Node 24+ and your account environment](../configuration.md).
 
 ## Add the server
 
 1. Open **Settings → Plugins → MCPs → Add server**. Set **Name** to `aimharder` and **Type** to **STDIO**.
 2. Set **Command to launch** to `npx`.
-3. Add two separate **Arguments**: `--yes` and `aimharder-mcp@0.1.0`, in that order.
+3. Add two separate **Arguments**: `--yes` and `aimharder-mcp@0.1.1`, in that order.
 4. Under **Environment variable passthrough**, add the names `AIMHARDER_USERNAME` and `AIMHARDER_PASSWORD`. The app must already receive their values. Also pass `AIMHARDER_GYM_TIME_ZONES` or `AIMHARDER_DEFAULT_GYM` if configured. Keep credential values out of the form's **Environment variables** fields.
 5. Leave **Working directory** empty unless your desktop build requires one. Save the server.
 
@@ -16,4 +16,4 @@ If the app cannot receive those variables, use the [private-file setup](../confi
 
 ## Check the connection
 
-After publication, check that the [tools](../tools.md) appear and ask an AimHarder question. Tool discovery does not authenticate; the first valid call does. `get_account_context` with `{}` is an optional way to check the gym and assumed or configured zone. The package connection remains unverified in this client.
+Check that the [tools](../tools.md) appear and ask an AimHarder question. Tool discovery does not authenticate; the first valid call does. `get_account_context` with `{}` is an optional way to check the gym and assumed or configured zone. The package connection remains unverified in this client.

package/docs/clients/claude-desktop.md

@@ -1,6 +1,6 @@
 # Connect Claude Desktop
 
-Claude Desktop configures local stdio servers in `mcpServers` JSON. Its [official guide](https://modelcontextprotocol.io/docs/develop/connect-local-servers) uses `npx`. This package has **not been tested** in Claude Desktop, and `aimharder-mcp@0.1.0` is not yet published.
+Claude Desktop configures local stdio servers in `mcpServers` JSON. Its [official guide](https://modelcontextprotocol.io/docs/develop/connect-local-servers) uses `npx`. This package has **not been tested** in Claude Desktop.
 
 ## Run the published package with `npx`
 
@@ -13,7 +13,7 @@ Claude Desktop configures local stdio servers in `mcpServers` JSON. Its [officia
      "mcpServers": {
        "aimharder": {
          "command": "npx",
-         "args": ["--yes", "aimharder-mcp@0.1.0"]
+         "args": ["--yes", "aimharder-mcp@0.1.1"]
        }
      }
    }

package/docs/clients/codex.md

@@ -0,0 +1,38 @@
+# Connect Codex CLI
+
+Codex configures local stdio servers in `~/.codex/config.toml`. Its [MCP guide](https://developers.openai.com/codex/mcp) describes the configuration shared by the CLI and IDE extension. The published package authenticated a read-only account query in Codex CLI; see [validation](https://github.com/rudeayelo/aimharder-mcp/blob/main/docs/validation.md). A connection in the Codex desktop app has not been separately checked.
+
+Install [Node 24+ and configure credentials](../configuration.md). Keep secret values out of `config.toml`.
+
+## Add the pinned package
+
+If Codex receives the required environment variables from your local environment, add:
+
+```toml
+[mcp_servers.aimharder]
+command = "npx"
+args = ["--yes", "aimharder-mcp@0.1.1"]
+env_vars = ["AIMHARDER_USERNAME", "AIMHARDER_PASSWORD"]
+```
+
+You can instead run `codex mcp add aimharder -- npx --yes aimharder-mcp@0.1.1`, then add the `env_vars` line to the created table. Also forward `AIMHARDER_GYM_TIME_ZONES` or `AIMHARDER_DEFAULT_GYM` if configured. Restart Codex after editing the configuration.
+
+## Private-file option
+
+If Codex does not receive those variables, use a [private environment file](../configuration.md#private-file-and-local-installation). This still runs the pinned package through `npx` while Node loads the private file:
+
+```toml
+[mcp_servers.aimharder]
+command = "/absolute/path/to/node"
+args = [
+  "--env-file=/absolute/path/to/private.env",
+  "/absolute/path/to/npm/bin/npx-cli.js",
+  "--yes",
+  "--prefix=/absolute/path/to/empty-npx-directory",
+  "aimharder-mcp@0.1.1",
+]
+```
+
+Create the empty directory first. The prefix makes `npx` resolve the public version even when Codex starts inside a checkout of `aimharder-mcp`. Find the npm CLI bundled with your Node installation; the path is installation-specific. Keep both the private file and empty directory outside the repository.
+
+Run `codex mcp get aimharder` to inspect the saved command. In a new Codex session, call `get_account_context` with `{}` to authenticate and inspect the gym and zone. Tool listing alone does not authenticate. The server is local and read-only.

package/docs/clients/hermes.md

@@ -1,6 +1,6 @@
 # Connect Hermes
 
-Hermes configures local stdio servers in `mcp_servers`. A local archive connected, exposed six tools and answered a future-WOD question; see [validation](https://github.com/rudeayelo/aimharder-mcp/blob/main/docs/validation.md). The npm version is not yet published or tested in Hermes.
+Hermes configures local stdio servers in `mcp_servers`. The published package connected, exposed six tools and authenticated an account query in Hermes; a prior local archive answered a future-WOD question. See [validation](https://github.com/rudeayelo/aimharder-mcp/blob/main/docs/validation.md).
 
 Set up [Node 24+ and credentials](../configuration.md). Hermes forwards configured `env` values, but does not pass every process variable to child servers. `${VAR}` resolves from the active profile's secrets or environment. See the [Hermes guide](https://github.com/NousResearch/hermes-agent/blob/main/website/docs/user-guide/features/mcp.md) and [config reference](https://github.com/NousResearch/hermes-agent/blob/main/website/docs/reference/mcp-config-reference.md).
 
@@ -14,7 +14,7 @@ mcp_servers:
     command: npx
     args:
       - --yes
-      - aimharder-mcp@0.1.0
+      - aimharder-mcp@0.1.1
     env:
       AIMHARDER_USERNAME: "${AIMHARDER_USERNAME}"
       AIMHARDER_PASSWORD: "${AIMHARDER_PASSWORD}"
@@ -25,8 +25,21 @@ mcp_servers:
 
 Keep literal credentials out of YAML and check that the references resolve. If the assumed zone is wrong, confirm the gym zone and add `AIMHARDER_GYM_TIME_ZONES: "${AIMHARDER_GYM_TIME_ZONES}"` under `env`. Add `AIMHARDER_DEFAULT_GYM` the same way for multiple gyms. Define optional variables before referencing them; unresolved references can cause errors.
 
+For a private environment file instead of profile variables, run the `npx` CLI under Node's `--env-file` option. Point `command` to your absolute Node 24+ executable and use these arguments:
+
+```yaml
+args:
+  - --env-file=/absolute/path/to/private.env
+  - /absolute/path/to/npm/bin/npx-cli.js
+  - --yes
+  - --prefix=/absolute/path/to/empty-npx-directory
+  - aimharder-mcp@0.1.1
+```
+
+Create the empty directory first. The prefix prevents `npx` from mistaking a checkout of this same package for the published executable. The private file and paths stay outside the repository. This form was used for the published-package Hermes check.
+
 ## Verify and reload
 
 Run `hermes mcp test aimharder`, or `hermes -p <profile> mcp test aimharder` for a named profile. This checks tool discovery, not AimHarder authentication. Run `/reload-mcp` and ask a question; the first valid tool call authenticates. `get_account_context` with `{}` is an optional gym check.
 
-`/reload-mcp` restarts the server; it does not reinstall it. Reinstall an updated archive or release before reloading.
+`/reload-mcp` restarts the server. Change the pinned version before reloading for a later release.

package/docs/clients/openclaw.md

@@ -1,6 +1,6 @@
 # Connect OpenClaw
 
-OpenClaw stores local stdio servers under `mcp.servers`; see its [MCP guide](https://docs.openclaw.ai/cli/mcp/registry) and [environment references](https://docs.openclaw.ai/gateway/config-secrets-env). This package has **not been tested** in OpenClaw, and `aimharder-mcp@0.1.0` is not yet published.
+OpenClaw stores local stdio servers under `mcp.servers`; see its [MCP guide](https://docs.openclaw.ai/cli/mcp/registry) and [environment references](https://docs.openclaw.ai/gateway/config-secrets-env). This package has **not been tested** in OpenClaw.
 
 Install Node 24+ and make `AIMHARDER_USERNAME` and `AIMHARDER_PASSWORD` available through OpenClaw's environment or secrets source. Keep literal values out of commands and saved definitions. See [configuration](../configuration.md).
 
@@ -11,7 +11,7 @@ Set `mcp.servers.aimharder` to this definition:
 ```json
 {
   "command": "npx",
-  "args": ["--yes", "aimharder-mcp@0.1.0"],
+  "args": ["--yes", "aimharder-mcp@0.1.1"],
   "env": {
     "AIMHARDER_USERNAME": "${AIMHARDER_USERNAME}",
     "AIMHARDER_PASSWORD": "${AIMHARDER_PASSWORD}"
@@ -22,7 +22,7 @@ Set `mcp.servers.aimharder` to this definition:
 Save the definition with the CLI:
 
 ```sh
-openclaw mcp set aimharder '{"command":"npx","args":["--yes","aimharder-mcp@0.1.0"],"env":{"AIMHARDER_USERNAME":"${AIMHARDER_USERNAME}","AIMHARDER_PASSWORD":"${AIMHARDER_PASSWORD}"}}'
+openclaw mcp set aimharder '{"command":"npx","args":["--yes","aimharder-mcp@0.1.1"],"env":{"AIMHARDER_USERNAME":"${AIMHARDER_USERNAME}","AIMHARDER_PASSWORD":"${AIMHARDER_PASSWORD}"}}'
 ```
 
 Keep the outer single quotes: they prevent the shell from inserting secret values into saved config. You can also edit `mcp.servers.aimharder` directly. If `Europe/Madrid` is wrong, confirm the gym zone, define `AIMHARDER_GYM_TIME_ZONES`, and add `"AIMHARDER_GYM_TIME_ZONES": "${AIMHARDER_GYM_TIME_ZONES}"` under `env`. Add a default gym only if configured.

package/docs/configuration.md

@@ -1,6 +1,6 @@
 # Configure a local AimHarder MCP server
 
-Your MCP client runs the server locally over stdio, using one AimHarder account per process. Install Node.js 24 or newer. **`aimharder-mcp@0.1.0` is not yet published to npm.**
+Your MCP client runs the server locally over stdio, using one AimHarder account per process. Install Node.js 24 or newer. The current verified npm version is `aimharder-mcp@0.1.1`.
 
 ## Environment variables
 
@@ -11,7 +11,7 @@ Your MCP client runs the server locally over stdio, using one AimHarder account
 | `AIMHARDER_GYM_TIME_ZONES` | Optional JSON object from discovered gym IDs to IANA zones, such as `{"sample-gym":"Atlantic/Canary"}`. Unmapped gyms use an explicitly assumed `Europe/Madrid` zone. Configure the actual zone when the assumption is wrong. |
 | `AIMHARDER_DEFAULT_GYM` | Optional for one accessible gym; required when the account has several. Use a discovered gym ID, not a URL. |
 
-Supply credentials through the client process environment or a secrets manager; forwarding rules differ by [client](../README.md#desktop-clients). Keep values out of shared config, issues and logs. The server holds its session in memory.
+Supply credentials through the client process environment or a secrets manager; forwarding rules differ by [client](../README.md#desktop-and-cli-clients). Keep values out of shared config, issues and logs. The server holds its session in memory.
 
 ## Discover your gym and check its time zone
 
@@ -23,11 +23,11 @@ Date inputs use `YYYY-MM-DD` in the reported gym zone. An assumed zone can make
 
 ## Version-pinned startup
 
-After npm publication, a client that forwards the required variables can start the pinned release with:
+A client that forwards the required variables can start the pinned release with:
 
 ```text
 command: npx
-arguments: --yes, aimharder-mcp@0.1.0
+arguments: --yes, aimharder-mcp@0.1.1
 ```
 
 If `npx` cannot start, check the app's access to Node and npm; GUI apps may have a different `PATH` from your terminal. The [private-file setup](#private-file-and-local-installation) runs Node directly. The server queries AimHarder on demand, without a persistent cache.
@@ -43,10 +43,10 @@ AIMHARDER_PASSWORD=your-account-password
 
 If needed, add `AIMHARDER_GYM_TIME_ZONES={"sample-gym":"Atlantic/Canary"}`, replacing the ID and zone. Restrict file and directory access with `chmod 600 /absolute/path/to/private.env` and `chmod 700 /absolute/path/to/private-directory`, or use a secrets-manager mount. The server does **not** load the file automatically.
 
-Once `0.1.0` is published, install the exact package into a private local directory:
+Alternatively, install the exact package into a private local directory:
 
 ```sh
-npm install --prefix /absolute/path/to/installation --ignore-scripts --omit=dev aimharder-mcp@0.1.0
+npm install --prefix /absolute/path/to/installation --ignore-scripts --omit=dev aimharder-mcp@0.1.1
 ```
 
 Point a stdio client at Node 24 or newer with these arguments, in this order:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "aimharder-mcp",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Local read-only AimHarder MCP server",
   "license": "MIT",
   "type": "module",