@starasia/task-management-mcp 1.1.4 → 1.1.6
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 +45 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -41,6 +41,42 @@ Or run without global install:
|
|
|
41
41
|
npx -y @starasia/task-management-mcp
|
|
42
42
|
```
|
|
43
43
|
|
|
44
|
+
## Quick start for users
|
|
45
|
+
|
|
46
|
+
You do not need to know every MCP tool name to use this package. In most AI agents, ask in natural language and let the agent choose the right tool.
|
|
47
|
+
|
|
48
|
+
Start by asking the agent to log in:
|
|
49
|
+
|
|
50
|
+
```text
|
|
51
|
+
Login to Task Management MCP
|
|
52
|
+
```
|
|
53
|
+
|
|
54
|
+
The agent should call `start_web_sso_login`, show you a secure SSO login URL, then ask you to open the URL and log in through the browser. Do **not** paste your SSO password into chat. After login, the agent will call `check_web_sso_login`. If your account has access to multiple organizations, the agent should show organization names and ask which one to use.
|
|
55
|
+
|
|
56
|
+
After login, try prompts like:
|
|
57
|
+
|
|
58
|
+
```text
|
|
59
|
+
Show my Task Management spaces
|
|
60
|
+
```
|
|
61
|
+
|
|
62
|
+
```text
|
|
63
|
+
What projects exist in the Ofa Lite space?
|
|
64
|
+
```
|
|
65
|
+
|
|
66
|
+
```text
|
|
67
|
+
Create a task in the MVP Generate Cycle project for implementing fleet settings
|
|
68
|
+
```
|
|
69
|
+
|
|
70
|
+
```text
|
|
71
|
+
Assign this task to Bayu
|
|
72
|
+
```
|
|
73
|
+
|
|
74
|
+
```text
|
|
75
|
+
Summarize my overdue tasks
|
|
76
|
+
```
|
|
77
|
+
|
|
78
|
+
Agents should preview write actions first. For example, when creating or updating tasks, the agent should show the planned title, description, status, priority, dates, and assignees before calling write tools with `dryRun: false`.
|
|
79
|
+
|
|
44
80
|
## Claude Code
|
|
45
81
|
|
|
46
82
|
Install global lalu daftarkan ke Claude Code:
|
|
@@ -162,7 +198,7 @@ CLI/local fallback flow:
|
|
|
162
198
|
|
|
163
199
|
Manual fallback remains available through `set_auth_context` when explicitly needed.
|
|
164
200
|
|
|
165
|
-
The MCP stores auth context in an encrypted local store and process memory, returns masked auth status, and never returns the bearer token from any tool.
|
|
201
|
+
The MCP stores auth context in an encrypted local store and process memory, returns masked auth status, and never returns the bearer token from any tool. The persisted context is reused until its configured expiry.
|
|
166
202
|
|
|
167
203
|
Call `clear_auth_context` when the session is done; it clears process state, pending SSO sessions, web login sessions, and the persisted auth store.
|
|
168
204
|
|
|
@@ -180,6 +216,14 @@ Optional SSO API base URL override, mainly for local/dev testing:
|
|
|
180
216
|
TASK_MANAGEMENT_SSO_API_BASE_URL=https://api.starasia.tech/sso
|
|
181
217
|
```
|
|
182
218
|
|
|
219
|
+
Optional auth persistence TTL override. The value is milliseconds; for example, 30 days:
|
|
220
|
+
|
|
221
|
+
```bash
|
|
222
|
+
TASK_MANAGEMENT_AUTH_TTL_MS=2592000000
|
|
223
|
+
```
|
|
224
|
+
|
|
225
|
+
Use a stable `TASK_MANAGEMENT_AUTH_STORE_KEY` in deployment so the encrypted auth store remains readable after MCP restarts.
|
|
226
|
+
|
|
183
227
|
Passwords are accepted only by `sso_login`; the resulting token stays in MCP process memory and is never returned.
|
|
184
228
|
|
|
185
229
|
## Safety notes
|