@gethmy/mcp 2.22.0 → 2.24.0

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.
package/README.md CHANGED
@@ -1,12 +1,12 @@
1
1
  # @gethmy/mcp
2
2
 
3
- MCP (Model Context Protocol) server for [Harmony](https://gethmy.com).
4
- Enables AI coding agents (Claude Code, OpenAI Codex, Cursor) to interact with your Harmony boards.
3
+ MCP (Model Context Protocol) server for [Harmony](https://gethmy.com), the shared surface for human–agent teams.
4
+ Claude Code, OpenAI Codex, Cursor, and any MCP client claim cards, report progress, and move work on your board.
5
5
 
6
6
  ## Features
7
7
 
8
- - **71 MCP Tools** for full board control, knowledge graph, and workflow plans
9
- - **7 Global Skills** — `/hmy`, `/hmy-plan`, `/hmy-cleanup`, `/hmy-standup`, `/hmy-memory-prune`, `/hmy-upgrade`, `/hmy-review`, served from the DB-backed [skill hub](../../docs/skills.md) with auto-update and admin-managed versioning
8
+ - **78 MCP Tools** for full board control, knowledge graph, and workflow plans
9
+ - **Global Skills** — installable in one command, served from the DB-backed [skill hub](../../docs/skills.md) with auto-update and admin-managed versioning
10
10
  - **Knowledge Graph Memory** — Phase 1 surface: hybrid retrieval (vector + lexical + RRF), session-scoped working memory, activity feed. See [docs/memory.md](../../docs/memory.md)
11
11
  - **GSD Workflow Plans** - plan/execute/verify/done lifecycle with auto card creation
12
12
  - **Card Linking** - create relationships between cards (blocks, relates_to, duplicates, is_part_of)
@@ -16,7 +16,7 @@ Enables AI coding agents (Claude Code, OpenAI Codex, Cursor) to interact with yo
16
16
  - **Auto-Assignment** - automatically assign cards to you when starting agent sessions
17
17
  - **Memory Sync** - bidirectional sync between local markdown files and remote database
18
18
  - **Multi-Agent Support** - works with Claude Code, Codex, Cursor, Claude.ai
19
- - **Smart Setup** - one command configures everything
19
+ - **One-Command Setup** - one command configures everything
20
20
  - **Browser Sign-In** - secure OAuth setup (loopback + PKCE), no key to copy or paste; API keys still supported for CI
21
21
 
22
22
  ## Prerequisites
@@ -32,7 +32,7 @@ Enables AI coding agents (Claude Code, OpenAI Codex, Cursor) to interact with yo
32
32
  npx @gethmy/mcp setup
33
33
  ```
34
34
 
35
- The smart setup wizard will:
35
+ The setup wizard will:
36
36
 
37
37
  - Sign you in through your browser (OAuth — no API key to copy or paste). You can also create a free account or paste an existing key from the same prompt.
38
38
  - Detect installed AI agents (Claude Code, Cursor, Codex)
@@ -89,7 +89,7 @@ If you prefer to configure manually (e.g., in Claude.ai's UI):
89
89
  1. Get an API key from [Harmony](https://gethmy.com/user/keys)
90
90
  2. In Claude.ai, add a remote MCP server with URL `https://mcp.gethmy.com/mcp`
91
91
  3. Set the Authorization header to `Bearer hmy_your_key_here`
92
- 4. All 70 Harmony tools become available in your conversation
92
+ 4. All 78 Harmony tools become available in your conversation
93
93
 
94
94
  **Session management** is automatic - sessions have a 1-hour TTL and are created/renewed transparently.
95
95
 
@@ -110,7 +110,7 @@ It detects your existing configuration and only asks for the project context.
110
110
 
111
111
  ```bash
112
112
  # Setup (recommended) — authorizes in your browser, no API key handling
113
- npx @gethmy/mcp setup # Smart setup wizard
113
+ npx @gethmy/mcp setup # Setup wizard
114
114
 
115
115
  # Setup with flags (non-interactive)
116
116
  npx @gethmy/mcp setup --global --workspace ID --project ID
@@ -150,9 +150,9 @@ npx @gethmy/mcp serve # Start MCP server
150
150
 
151
151
  ## Skills
152
152
 
153
- Seven global skills ship with the MCP server and are installed automatically by `npx @gethmy/mcp setup`. They live in the `skill_resource` Postgres table, are fetched via `GET /v1/skills/<name>`, and render-time composed with a shared auto-update preamble.
153
+ Global skills ship with the MCP server and are installed automatically by `npx @gethmy/mcp setup`. They live in the `skill_resource` Postgres table, are fetched via `GET /v1/skills/<name>`, and render-time composed.
154
154
 
155
- For the full skill hub architecture (storage, versioning, auto-update, admin management), see [docs/skills.md](../../docs/skills.md).
155
+ For the full skill list and the hub architecture (storage, versioning, auto-update, admin management), see [docs/skills.md](../../docs/skills.md).
156
156
 
157
157
  ### `/hmy` — Card Workflow
158
158
 
@@ -200,7 +200,7 @@ Generates a structured standup summary: what shipped, what's in progress, what's
200
200
 
201
201
  ### Auto-Update
202
202
 
203
- Every skill ships with an `hmy-update-check` preamble that fires on invocation. It compares local versions against `/v1/skills/version` and prompts (or silently auto-installs, if `~/.hmy/config.yaml` has `auto_upgrade: true`). Snooze levels: 24h / 48h / 7d.
203
+ The server owns auto-update. `refreshSkills()` runs at `serve` startup, calls `GET /v1/skills/version` at most once per 24h, and atomically rewrites only the installed skill files that are behind. Two knobs live in `~/.hmy/config.yaml`: `update_check` (master switch) and `pin` (freeze on the installed version).
204
204
 
205
205
  ## Available Tools
206
206
 
@@ -296,7 +296,7 @@ Sessions are automatically started when agents call card-mutating tools without
296
296
  |-----------|-------------|
297
297
  | `cardId` | Card UUID to generate prompt from |
298
298
  | `shortId` | Alternative: Card short ID (e.g., 42 for #42) |
299
- | `variant` | `analysis` (understand/plan), `draft` (design solution), `execute` (implement fully) |
299
+ | `variant` | `analysis` (understand/plan), `draft` (design the approach), `execute` (implement fully) |
300
300
  | `includeDescription` | Include card description (default: true) |
301
301
  | `includeSubtasks` | Include subtasks in prompt (default: true) |
302
302
  | `includeLinks` | Include linked cards in prompt (default: true) |
@@ -340,7 +340,7 @@ Create and manage project plans with a phased workflow: **plan** → **execute**
340
340
  - `harmony_get_plan` - Get plan by ID or card ID
341
341
  - `harmony_update_plan` - Update plan title, content, status, or phase
342
342
  - `harmony_advance_plan` - Advance to next phase with side effects:
343
- - **plan → execute:** auto-creates Kanban cards from plan tasks, sets plan active
343
+ - **plan → execute:** auto-creates board cards from plan tasks, sets plan active
344
344
  - **execute → verify:** checks card completion status
345
345
  - **verify → done:** archives plan, creates memory entities
346
346
 
@@ -349,7 +349,7 @@ Create and manage project plans with a phased workflow: **plan** → **execute**
349
349
  - `harmony_onboard` - Complete end-to-end onboarding: signup → workspace → project → API key
350
350
  - `harmony_signup` - Create a new user account
351
351
  - `harmony_create_workspace` - Create a new workspace
352
- - `harmony_create_project` - Create a new project with template columns (kanban, scrum, or simple)
352
+ - `harmony_create_project` - Create a new project with template columns (kanban, scrum, or simple) <!-- copy-guard-ignore: template enum value of the public API, not copy -->
353
353
  - `harmony_send_invitations` - Send workspace invitations to team members
354
354
  - `harmony_generate_api_key` - Generate an API key for the authenticated user
355
355