@vheins/local-memory-mcp 0.9.9 → 0.9.11
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/dist/{chunk-UB4KAJYE.js → chunk-DII7QPRT.js} +51 -7
- package/dist/dashboard/server.js +1 -1
- package/dist/mcp/server.js +1 -1
- package/dist/prompts/create-task.md +7 -1
- package/dist/prompts/project-briefing.md +2 -1
- package/dist/prompts/review-and-audit.md +1 -0
- package/dist/prompts/session-planner.md +2 -1
- package/dist/prompts/task-management-guidelines.md +1 -0
- package/dist/prompts/task-memory-executor.md +2 -1
- package/package.json +1 -1
|
@@ -3,8 +3,8 @@ import { fileURLToPath } from "url";
|
|
|
3
3
|
import path from "path";
|
|
4
4
|
var __dirname = path.dirname(fileURLToPath(import.meta.url));
|
|
5
5
|
var pkgVersion = "0.1.0";
|
|
6
|
-
if ("0.9.
|
|
7
|
-
pkgVersion = "0.9.
|
|
6
|
+
if ("0.9.11") {
|
|
7
|
+
pkgVersion = "0.9.11";
|
|
8
8
|
} else {
|
|
9
9
|
let searchDir = __dirname;
|
|
10
10
|
for (let i = 0; i < 5; i++) {
|
|
@@ -23,10 +23,54 @@ if ("0.9.9") {
|
|
|
23
23
|
}
|
|
24
24
|
}
|
|
25
25
|
var MCP_PROTOCOL_VERSION = "2025-03-26";
|
|
26
|
+
var SERVER_INSTRUCTIONS = `
|
|
27
|
+
Local Memory MCP \u2014 persistent memory, task coordination, and coding standards for AI agents.
|
|
28
|
+
|
|
29
|
+
## When to use this server
|
|
30
|
+
Use at the START of every session and before any implementation work:
|
|
31
|
+
1. Call \`task-list\` to sync active/pending tasks for the current repository.
|
|
32
|
+
2. Call \`handoff-list\` to check pending context transfers. Close stale handoffs with \`handoff-update\`.
|
|
33
|
+
3. Call \`memory-search\` and \`memory-synthesize\` to hydrate architectural context before coding.
|
|
34
|
+
4. Call \`standard-search\` when implementation may be governed by language/stack conventions.
|
|
35
|
+
|
|
36
|
+
## Core Workflows
|
|
37
|
+
|
|
38
|
+
**Memory**: \`memory-search\` \u2192 \`memory-detail\` \u2192 \`memory-store\` / \`memory-update\`
|
|
39
|
+
- Store only durable knowledge (architecture, patterns, decisions, fixes).
|
|
40
|
+
- Use \`memory-acknowledge\` after generating code from memory results.
|
|
41
|
+
- Global scope only for cross-repo rules; prefer repo-specific scope.
|
|
42
|
+
|
|
43
|
+
**Tasks**: \`task-list\` \u2192 \`task-claim\` \u2192 \`task-update\` (in_progress \u2192 completed)
|
|
44
|
+
- Register planned steps via \`task-create\` before execution.
|
|
45
|
+
- Never skip intermediate \`in_progress\` state before \`completed\`.
|
|
46
|
+
- Completing a task auto-releases claims and expires linked handoffs.
|
|
47
|
+
|
|
48
|
+
**Standards**: \`standard-search\` \u2192 \`standard-store\`
|
|
49
|
+
- One rule per entry. Treat as normative implementation contracts, not docs summaries.
|
|
50
|
+
|
|
51
|
+
**Handoffs/Claims**: \`handoff-list\` \u2192 \`handoff-create\` / \`handoff-update\` | \`task-claim\` / \`claim-release\`
|
|
52
|
+
- Create handoffs only for unfinished work with concrete next owner or next steps.
|
|
53
|
+
- Do NOT create handoffs as completion summaries \u2014 put those on \`task-update\` comments.
|
|
54
|
+
|
|
55
|
+
## Available Prompts (invoke as slash commands)
|
|
56
|
+
- \`session-planner\` \u2014 orient and plan at session start
|
|
57
|
+
- \`task-memory-executor\` \u2014 execute tasks with memory and standard enforcement
|
|
58
|
+
- \`senior-code-review\` \u2014 full code review against stored standards
|
|
59
|
+
- \`memory-guided-review\` \u2014 review using project memory as context
|
|
60
|
+
- \`architecture-design\` \u2014 architectural planning and ADR generation
|
|
61
|
+
- \`technical-planning\` \u2014 feature planning with task decomposition
|
|
62
|
+
- \`root-cause-analysis\` \u2014 structured bug / incident investigation
|
|
63
|
+
- \`fix-suggestion\` \u2014 propose and validate fixes
|
|
64
|
+
- \`security-triage\` \u2014 security risk assessment
|
|
65
|
+
- \`learning-retrospective\` \u2014 capture lessons and update memory
|
|
66
|
+
- \`documentation-sync\` \u2014 sync docs with current codebase state
|
|
67
|
+
- \`project-briefing\` \u2014 generate repository briefing from memory
|
|
68
|
+
`.trim();
|
|
26
69
|
var CAPABILITIES = {
|
|
27
70
|
serverInfo: {
|
|
28
71
|
name: "mcp-memory-local",
|
|
29
|
-
version: pkgVersion
|
|
72
|
+
version: pkgVersion,
|
|
73
|
+
instructions: SERVER_INSTRUCTIONS
|
|
30
74
|
},
|
|
31
75
|
capabilities: {
|
|
32
76
|
completions: {},
|
|
@@ -3486,7 +3530,7 @@ var TOOL_DEFINITIONS = [
|
|
|
3486
3530
|
title: { type: "string", minLength: 3, maxLength: 100 },
|
|
3487
3531
|
description: { type: "string", minLength: 1 },
|
|
3488
3532
|
status: { type: "string", enum: ["backlog", "pending"], default: "backlog" },
|
|
3489
|
-
priority: { type: "number", minimum: 1, maximum: 5, default: 3 },
|
|
3533
|
+
priority: { type: "number", minimum: 1, maximum: 5, default: 3, description: "Task priority where 1=Low, 2=Normal, 3=Medium, 4=High, 5=Critical." },
|
|
3490
3534
|
agent: { type: "string" },
|
|
3491
3535
|
role: { type: "string" },
|
|
3492
3536
|
doc_path: { type: "string" },
|
|
@@ -4022,7 +4066,7 @@ var TOOL_DEFINITIONS = [
|
|
|
4022
4066
|
default: "backlog",
|
|
4023
4067
|
description: "New tasks MUST start in 'backlog' if there are already 10 pending tasks. Otherwise can start in 'pending'."
|
|
4024
4068
|
},
|
|
4025
|
-
priority: { type: "number", minimum: 1, maximum: 5, default: 3 },
|
|
4069
|
+
priority: { type: "number", minimum: 1, maximum: 5, default: 3, description: "Task priority where 1=Low, 2=Normal, 3=Medium, 4=High, 5=Critical." },
|
|
4026
4070
|
agent: { type: "string" },
|
|
4027
4071
|
role: { type: "string" },
|
|
4028
4072
|
doc_path: { type: "string" },
|
|
@@ -4041,7 +4085,7 @@ var TOOL_DEFINITIONS = [
|
|
|
4041
4085
|
title: { type: "string", minLength: 3, maxLength: 100 },
|
|
4042
4086
|
description: { type: "string" },
|
|
4043
4087
|
status: { type: "string", enum: ["backlog", "pending"], default: "backlog" },
|
|
4044
|
-
priority: { type: "number", minimum: 1, maximum: 5, default: 3 },
|
|
4088
|
+
priority: { type: "number", minimum: 1, maximum: 5, default: 3, description: "Task priority where 1=Low, 2=Normal, 3=Medium, 4=High, 5=Critical." },
|
|
4045
4089
|
agent: { type: "string" },
|
|
4046
4090
|
role: { type: "string" },
|
|
4047
4091
|
doc_path: { type: "string" },
|
|
@@ -4100,7 +4144,7 @@ var TOOL_DEFINITIONS = [
|
|
|
4100
4144
|
enum: ["backlog", "pending", "in_progress", "completed", "canceled", "blocked"],
|
|
4101
4145
|
description: "New status. Transitions from 'backlog', 'pending' or 'blocked' to 'completed' are NOT allowed."
|
|
4102
4146
|
},
|
|
4103
|
-
priority: { type: "number", minimum: 1, maximum: 5 },
|
|
4147
|
+
priority: { type: "number", minimum: 1, maximum: 5, description: "Task priority where 1=Low, 2=Normal, 3=Medium, 4=High, 5=Critical." },
|
|
4104
4148
|
agent: { type: "string" },
|
|
4105
4149
|
role: { type: "string" },
|
|
4106
4150
|
model: { type: "string" },
|
package/dist/dashboard/server.js
CHANGED
package/dist/mcp/server.js
CHANGED
|
@@ -32,7 +32,13 @@ ONLY call MCP tools. No prose, no code, no plans outside MCP.
|
|
|
32
32
|
## 3. ATTRIBUTES & FORMAT
|
|
33
33
|
- `task_code`: FEAT/FIX/REFACTOR-XXX.
|
|
34
34
|
- `phase`: Discovery/Implementation/Testing.
|
|
35
|
-
- `priority`: 1-5
|
|
35
|
+
- `priority`: 1-5 using this exact scale:
|
|
36
|
+
- `1 = Low`
|
|
37
|
+
- `2 = Normal`
|
|
38
|
+
- `3 = Medium`
|
|
39
|
+
- `4 = High`
|
|
40
|
+
- `5 = Critical`
|
|
41
|
+
- `priority` is ascending by urgency. `5` is the highest urgency and `1` is the lowest. Never encode `Critical` as `1`.
|
|
36
42
|
- `description` (STRICT FORMAT):
|
|
37
43
|
### 1. Context & Analysis
|
|
38
44
|
- **Trigger**: Instruction/finding.
|
|
@@ -13,4 +13,5 @@ Briefing Steps:
|
|
|
13
13
|
4. **Memory**: Call `memory-search` or `memory-recap` for recent decisions, patterns, and mistakes; hydrate important entries with `memory-detail`.
|
|
14
14
|
5. **Standards**: Call `standard-search` with current repo/stack when implementation guidance is needed.
|
|
15
15
|
6. **Core Context**: Summarize active task, pending handoffs, applicable standards, and top architectural decisions.
|
|
16
|
-
7. **
|
|
16
|
+
7. **Priority Reminder**: Treat task priority with MCP semantics: `1=Low`, `2=Normal`, `3=Medium`, `4=High`, `5=Critical`.
|
|
17
|
+
8. **Action**: Propose next steps based on the active queue.
|
|
@@ -31,6 +31,7 @@ ONLY call MCP tools. No prose, code, or external plans.
|
|
|
31
31
|
## 3. TASK DESIGN & FORMAT
|
|
32
32
|
- **Atomic**: One change per task.
|
|
33
33
|
- **Attributes**: `task_code`, `phase`, `priority`, `agent`, `model`.
|
|
34
|
+
- **Priority Scale**: Use MCP ordering exactly: `1=Low`, `2=Normal`, `3=Medium`, `4=High`, `5=Critical`. `5` is the highest urgency.
|
|
34
35
|
- **Description** (STRICT FORMAT):
|
|
35
36
|
### 1. Context & Analysis
|
|
36
37
|
- **Finding**: Gap trigger.
|
|
@@ -16,6 +16,7 @@ Steps:
|
|
|
16
16
|
4. **Analyze**: Break into 3-7 atomic, verifiable tasks.
|
|
17
17
|
5. **Phase**: Group into `research`, `implementation`, and `validation`.
|
|
18
18
|
6. **Hierarchy**: Use `parent_id` / `depends_on` for sequencing.
|
|
19
|
-
7. **
|
|
19
|
+
7. **Priority Scale**: When creating tasks, use the exact MCP scale `1=Low`, `2=Normal`, `3=Medium`, `4=High`, `5=Critical`. Higher number means higher urgency.
|
|
20
|
+
8. **Create**: Use `task-create` in current repo with stable `task_code`, tags, and acceptance criteria.
|
|
20
21
|
|
|
21
22
|
Display final plan to user.
|
|
@@ -9,6 +9,7 @@ agent: Project Manager
|
|
|
9
9
|
## 1. NAVIGATION (`task-list`)
|
|
10
10
|
- **Sync**: Call `task-list` at every session start (default: `in_progress,pending`).
|
|
11
11
|
- **Format**: Compact pointer table: `id`, `task_code`, `title`, `status`, `priority`, `updated_at`, `comments_count`. Use `query` for keyword search.
|
|
12
|
+
- **Priority Scale**: Interpret `priority` with MCP semantics: `1=Low`, `2=Normal`, `3=Medium`, `4=High`, `5=Critical`.
|
|
12
13
|
- **Retrieve**: Fetch full context via `task-detail` AFTER selecting a task. The hydrated task includes current coordination state such as active claims and pending handoffs.
|
|
13
14
|
- **Coordination**: Check active ownership with task coordination metadata, `task-claim`, and `claim-list`. NEVER work on tasks claimed by others. Focus on ONE task at a time.
|
|
14
15
|
|
|
@@ -51,7 +51,8 @@ agent: Task Executor
|
|
|
51
51
|
## 3. BACKLOG MAINTENANCE
|
|
52
52
|
If active queue is empty:
|
|
53
53
|
1. Call `task-list` (status: `backlog`).
|
|
54
|
-
2. Move up to 20
|
|
54
|
+
2. Move up to 20 highest-priority tasks to `pending` via `task-update`.
|
|
55
|
+
3. Interpret priority using MCP ordering: `5=Critical`, `4=High`, `3=Medium`, `2=Normal`, `1=Low`.
|
|
55
56
|
|
|
56
57
|
## 4. REPORT
|
|
57
58
|
Provide progress summary.
|