@tday-com/mcp 0.4.7 → 0.4.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +1 -1
  2. package/dist/cli.js +230 -196
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -109,7 +109,7 @@ Run any of them with `npx -y @tday-com/mcp@latest <command>`.
109
109
  }
110
110
  ```
111
111
 
112
- `--prefix` keeps npx from reading the repo's `package.json`: the agent starts the server in your repo, and a repo whose `overrides` pin one of this package's dependencies would otherwise fail the start (`EOVERRIDE`). `install` writes this entry pinned to its own version, so your agent never picks up a new release on its own. Run `install` again to update. Pin the version in an entry you write by hand too. If you add the entry yourself, run `npx -y @tday-com/mcp@latest install` once afterwards, so the browser sign-in can link the server to your tday account.
112
+ `--prefix` keeps npx from reading the repo's `package.json`: the agent starts the server in your repo, and a repo whose `overrides` pin one of this package's dependencies would otherwise fail the start (`EOVERRIDE`). `install` writes this entry pinned to its own version. When tday releases a newer version, the server re-pins its own entries to it as it starts (only to a version tday names and that npm shows tday's release workflow published; Codex's TOML is never edited), so your agent runs it from its next start; `TDAY_MCP_AUTO_UPDATE=0` keeps the version you have. By hand: `npx --prefix ~ -y @tday-com/mcp@latest update`. Pin the version in an entry you write by hand too: an `@latest` entry is never rewritten. If you add the entry yourself, run `npx -y @tday-com/mcp@latest install` once afterwards, so the browser sign-in can link the server to your tday account.
113
113
 
114
114
  For Gemini CLI, put the same `mcpServers.tday` object in `~/.gemini/settings.json`. VS Code's user `mcp.json` keys entries by `servers` and names the transport: `{ "servers": { "tday": { "type": "stdio", "command": "npx", "args": ["--prefix", "<your home directory>", "-y", "@tday-com/mcp@<version>", "serve"] } } }`.
115
115