paput-mcp 2.7.0 → 2.8.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.
Files changed (74) hide show
  1. package/README.md +18 -0
  2. package/dist/cli/setup-ai.js +43 -0
  3. package/dist/cli/setup-ai.js.map +1 -1
  4. package/dist/handlers/create-goal/handler.js +68 -0
  5. package/dist/handlers/create-goal/handler.js.map +1 -0
  6. package/dist/handlers/create-goal/index.js +3 -0
  7. package/dist/handlers/create-goal/index.js.map +1 -0
  8. package/dist/handlers/create-goal/tool.js +13 -0
  9. package/dist/handlers/create-goal/tool.js.map +1 -0
  10. package/dist/handlers/delete-goal/handler.js +37 -0
  11. package/dist/handlers/delete-goal/handler.js.map +1 -0
  12. package/dist/handlers/delete-goal/index.js +3 -0
  13. package/dist/handlers/delete-goal/index.js.map +1 -0
  14. package/dist/handlers/delete-goal/tool.js +13 -0
  15. package/dist/handlers/delete-goal/tool.js.map +1 -0
  16. package/dist/handlers/get-dashboard-analysis/handler.js +51 -0
  17. package/dist/handlers/get-dashboard-analysis/handler.js.map +1 -0
  18. package/dist/handlers/get-dashboard-analysis/index.js +3 -0
  19. package/dist/handlers/get-dashboard-analysis/index.js.map +1 -0
  20. package/dist/handlers/get-dashboard-analysis/tool.js +13 -0
  21. package/dist/handlers/get-dashboard-analysis/tool.js.map +1 -0
  22. package/dist/handlers/get-dashboard-analysis-context/handler.js +125 -0
  23. package/dist/handlers/get-dashboard-analysis-context/handler.js.map +1 -0
  24. package/dist/handlers/get-dashboard-analysis-context/index.js +3 -0
  25. package/dist/handlers/get-dashboard-analysis-context/index.js.map +1 -0
  26. package/dist/handlers/get-dashboard-analysis-context/tool.js +13 -0
  27. package/dist/handlers/get-dashboard-analysis-context/tool.js.map +1 -0
  28. package/dist/handlers/get-skill-sheet-project-summary-context/handler.js +25 -2
  29. package/dist/handlers/get-skill-sheet-project-summary-context/handler.js.map +1 -1
  30. package/dist/handlers/index.js +7 -0
  31. package/dist/handlers/index.js.map +1 -1
  32. package/dist/handlers/list-goals/handler.js +43 -0
  33. package/dist/handlers/list-goals/handler.js.map +1 -0
  34. package/dist/handlers/list-goals/index.js +3 -0
  35. package/dist/handlers/list-goals/index.js.map +1 -0
  36. package/dist/handlers/list-goals/tool.js +13 -0
  37. package/dist/handlers/list-goals/tool.js.map +1 -0
  38. package/dist/handlers/update-dashboard-analysis/handler.js +93 -0
  39. package/dist/handlers/update-dashboard-analysis/handler.js.map +1 -0
  40. package/dist/handlers/update-dashboard-analysis/index.js +3 -0
  41. package/dist/handlers/update-dashboard-analysis/index.js.map +1 -0
  42. package/dist/handlers/update-dashboard-analysis/tool.js +13 -0
  43. package/dist/handlers/update-dashboard-analysis/tool.js.map +1 -0
  44. package/dist/handlers/update-goal/handler.js +70 -0
  45. package/dist/handlers/update-goal/handler.js.map +1 -0
  46. package/dist/handlers/update-goal/index.js +3 -0
  47. package/dist/handlers/update-goal/index.js.map +1 -0
  48. package/dist/handlers/update-goal/tool.js +13 -0
  49. package/dist/handlers/update-goal/tool.js.map +1 -0
  50. package/dist/schemas/tool-input.js +77 -0
  51. package/dist/schemas/tool-input.js.map +1 -1
  52. package/dist/services/api/dashboard-analysis.js +7 -0
  53. package/dist/services/api/dashboard-analysis.js.map +1 -0
  54. package/dist/services/api/dashboard.js +4 -0
  55. package/dist/services/api/dashboard.js.map +1 -0
  56. package/dist/services/api/goal.js +13 -0
  57. package/dist/services/api/goal.js.map +1 -0
  58. package/dist/services/api/index.js +3 -0
  59. package/dist/services/api/index.js.map +1 -1
  60. package/dist/services/api/memo.js +2 -0
  61. package/dist/services/api/memo.js.map +1 -1
  62. package/dist/tool.js +8 -1
  63. package/dist/tool.js.map +1 -1
  64. package/dist/types/dashboard-analysis.js +2 -0
  65. package/dist/types/dashboard-analysis.js.map +1 -0
  66. package/dist/types/dashboard.js +2 -0
  67. package/dist/types/dashboard.js.map +1 -0
  68. package/dist/types/goal.js +2 -0
  69. package/dist/types/goal.js.map +1 -0
  70. package/dist/types/index.js +3 -0
  71. package/dist/types/index.js.map +1 -1
  72. package/docs/tools.md +31 -0
  73. package/docs/usage-examples.md +18 -0
  74. package/package.json +1 -1
package/docs/tools.md CHANGED
@@ -16,8 +16,10 @@ Clients and assistants should follow these rules:
16
16
  - `paput_save_pending_candidate` requires explicit user approval because it creates a PaPut memo from a local pending candidate.
17
17
  - `paput_delete_skill_sheet_project` should be used only when the user clearly intends to remove a project.
18
18
  - `paput_update_skill_sheet_project_ai_summary` should be used only after the MCP client AI model has generated a project summary and the user intends to save it.
19
+ - `paput_update_dashboard_analysis` should be used only after the MCP client AI model has generated dashboard analysis and the user intends to save it.
19
20
  - `paput_set_skill_sheet_skills` replaces the full skill list and should be used only when the complete desired final list is known.
20
21
  - `paput_discard_pending_candidate` removes a pending item from the save flow and should be confirmed when the candidate may still be useful.
22
+ - `paput_delete_goal` should be used only when the user clearly intends to remove a goal.
21
23
  - Update and upsert tools should preserve existing data unless the user requested the change.
22
24
 
23
25
  ## Memo Tools
@@ -56,6 +58,35 @@ mode.
56
58
  | `paput_get_skill_sheet_project_summary_context` | Read-only | Get project information and related memo bodies for MCP client-side summary generation. |
57
59
  | `paput_update_skill_sheet_project_ai_summary` | Destructive/write | Save an AI-generated project summary. |
58
60
 
61
+ ## Goal Tools
62
+
63
+ | Tool | Safety | Use case |
64
+ | ------------------- | ----------------- | ----------------------------------------------------------------------------------- |
65
+ | `paput_list_goals` | Read-only | List active and archived goals. Active goals are current analysis targets. |
66
+ | `paput_create_goal` | Write | Create a goal for career, learning, portfolio, project, or other progress tracking. |
67
+ | `paput_update_goal` | Destructive/write | Update a goal. The update request body includes `id`, and success returns no body. |
68
+ | `paput_delete_goal` | Destructive | Delete a goal by ID. The API path uses `/goal/:id`. |
69
+
70
+ Archived goals are historical context. Active goals are normally used as the basis for
71
+ dashboard analysis.
72
+
73
+ ## Dashboard Analysis Tools
74
+
75
+ | Tool | Safety | Use case |
76
+ | -------------------------------------- | ----------------- | ----------------------------------------------------------------------------------------------- |
77
+ | `paput_get_dashboard_analysis` | Read-only | Get the saved dashboard analysis result. |
78
+ | `paput_get_dashboard_analysis_context` | Read-only | Get dashboard summary, goals, skill sheet, recent memos, notes, and categories for AI analysis. |
79
+ | `paput_update_dashboard_analysis` | Destructive/write | Save dashboard analysis generated by the MCP client AI model. |
80
+
81
+ `paput_get_dashboard_analysis_context` returns raw source data in
82
+ `structuredContent` for MCP client-side analysis. The context asks the MCP client
83
+ AI model to analyze current position, strengths, recently growing areas, thin
84
+ areas, missing knowledge against goals, next knowledge to learn, and expressions
85
+ suitable for a skill sheet or career history. It also instructs the client AI to
86
+ write the final output in the user's language. The MCP server does not
87
+ recalculate dashboard continuity from activities; it relies on summary values
88
+ returned by the PaPut API.
89
+
59
90
  ## Knowledge Capture And Local Cache Tools
60
91
 
61
92
  These tools are local CLI mode only. They are not listed by the remote HTTP MCP
@@ -104,3 +104,21 @@ Expected tool flow:
104
104
  3. `paput_get_note` to verify attached memo IDs
105
105
 
106
106
  Use case: create curated collections from existing PaPut memos.
107
+
108
+ ## 7. Generate And Save Dashboard Analysis
109
+
110
+ Prompt:
111
+
112
+ ```text
113
+ Analyze my PaPut dashboard and goals, then save the dashboard analysis.
114
+ ```
115
+
116
+ Expected tool flow:
117
+
118
+ 1. `paput_get_dashboard_analysis_context`
119
+ 2. MCP client AI generates the analysis from `structuredContent`
120
+ 3. `paput_update_dashboard_analysis` after the user intends to save the result
121
+ 4. `paput_get_dashboard_analysis` to verify the saved result
122
+
123
+ Use case: keep analysis generation in the MCP client AI while PaPut MCP only
124
+ retrieves source data and saves the finished analysis.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "paput-mcp",
3
- "version": "2.7.0",
3
+ "version": "2.8.0",
4
4
  "description": "PaPut MCP Server",
5
5
  "main": "dist/index.js",
6
6
  "type": "module",