mcp-task-server 0.1.0 → 0.1.2

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 (2) hide show
  1. package/README.md +111 -5
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -74,7 +74,7 @@ npm start
74
74
 
75
75
  ## Cursor IDE Integration
76
76
 
77
- Add to your `.cursor/mcp.json`:
77
+ Add to your project's `.cursor/mcp.json`:
78
78
 
79
79
  ```json
80
80
  {
@@ -82,13 +82,50 @@ Add to your `.cursor/mcp.json`:
82
82
  "task-server": {
83
83
  "command": "npx",
84
84
  "args": ["-y", "mcp-task-server"],
85
- "cwd": "/path/to/your/project"
85
+ "cwd": "/absolute/path/to/your/project"
86
86
  }
87
87
  }
88
88
  }
89
89
  ```
90
90
 
91
- The `cwd` parameter sets the workspace root where task files will be stored.
91
+ ### Important: cwd Limitations
92
+
93
+ The `cwd` parameter has limitations in Cursor:
94
+
95
+ 1. **Must be an absolute path** - Relative paths and `~` expansion do not work reliably
96
+ 2. **Set per-project** - Each project needs its own `.cursor/mcp.json` with the correct `cwd`
97
+ 3. **No dynamic resolution** - Cursor does not automatically resolve `cwd` to the current workspace
98
+ 4. **Global config issues** - If using `~/.cursor/mcp.json` (global), the `cwd` applies to all projects
99
+
100
+ **Recommended setup**: Add `.cursor/mcp.json` to each project with an absolute path:
101
+
102
+ ```json
103
+ {
104
+ "mcpServers": {
105
+ "task-server": {
106
+ "command": "npx",
107
+ "args": ["-y", "mcp-task-server"],
108
+ "cwd": "/Users/yourname/Projects/my-project"
109
+ }
110
+ }
111
+ }
112
+ ```
113
+
114
+ **Alternative**: Use environment variable for the working directory:
115
+
116
+ ```json
117
+ {
118
+ "mcpServers": {
119
+ "task-server": {
120
+ "command": "npx",
121
+ "args": ["-y", "mcp-task-server"],
122
+ "env": {
123
+ "TASK_WORKSPACE": "/Users/yourname/Projects/my-project"
124
+ }
125
+ }
126
+ }
127
+ }
128
+ ```
92
129
 
93
130
  ## Configuration
94
131
 
@@ -155,8 +192,8 @@ High-level overview auto-generated from tasks.json:
155
192
  ## Task Completion Summary
156
193
 
157
194
  ### Completed Tasks (3/5)
158
- - Task 1: Project Setup
159
- - Task 2: Database Schema
195
+ - Task 1: Project Setup
196
+ - Task 2: Database Schema
160
197
  ```
161
198
 
162
199
  This architecture scales well for complex projects with many tasks and subtasks.
@@ -299,6 +336,72 @@ If you have existing `.taskmaster/tasks.json`:
299
336
  3. Individual task files are generated
300
337
  4. Progress summary is updated
301
338
 
339
+ ## Publishing to npm
340
+
341
+ ### Prerequisites
342
+
343
+ 1. An npm account at [npmjs.com](https://www.npmjs.com/)
344
+ 2. Node.js 18+
345
+
346
+ ### npm Security Changes (2025+)
347
+
348
+ npm has updated its security model:
349
+
350
+ - **TOTP authenticator apps are deprecated** for new 2FA setups
351
+ - **Security keys (WebAuthn/FIDO)** are now required for new 2FA configurations
352
+ - **Automation tokens** are required for CI/CD and scripted publishing
353
+
354
+ ### Creating a Publish Token
355
+
356
+ 1. Go to [npmjs.com/settings/~/tokens](https://www.npmjs.com/settings/~/tokens)
357
+ 2. Click **Generate New Token** → **Granular Access Token**
358
+ 3. Configure:
359
+ - **Token name**: `mcp-task-server-publish` (or your preference)
360
+ - **Bypass two-factor authentication (2FA)**: Check this box (required for CLI publishing)
361
+ - **Allowed IP ranges**: Optional - add your IP as `x.x.x.x/32` for extra security
362
+ - **Packages and scopes**: Select **Read and write**, then **All packages**
363
+ - **Expiration**: 90 days (maximum for granular tokens)
364
+ 4. Click **Generate Token**
365
+ 5. Copy the token immediately (you won't see it again)
366
+
367
+ ### Publishing
368
+
369
+ ```bash
370
+ # Set the token as an environment variable
371
+ export NPM_TOKEN=npm_xxxxxxxxxxxx
372
+
373
+ # Build and publish
374
+ cd /path/to/mcp-task-server
375
+ npm publish --//registry.npmjs.org/:_authToken=$NPM_TOKEN
376
+ ```
377
+
378
+ The `prepublishOnly` script automatically runs `npm run build` before publishing.
379
+
380
+ ### Releasing Updates
381
+
382
+ ```bash
383
+ # Bump version (updates package.json and creates git tag)
384
+ npm version patch # 0.1.1 -> 0.1.2
385
+ npm version minor # 0.1.2 -> 0.2.0
386
+ npm version major # 0.2.0 -> 1.0.0
387
+
388
+ # Publish the new version
389
+ npm publish --//registry.npmjs.org/:_authToken=$NPM_TOKEN
390
+ ```
391
+
392
+ ### Verifying Publication
393
+
394
+ ```bash
395
+ npm info mcp-task-server
396
+ ```
397
+
398
+ ### Token Security Tips
399
+
400
+ - **Regenerate tokens** before they expire (90 day limit)
401
+ - **Use IP restrictions** if publishing from a static IP
402
+ - **Never commit tokens** to version control
403
+ - **Store tokens securely** (e.g., password manager, environment variables)
404
+
302
405
  ## Development
303
406
 
304
407
  ```bash
@@ -310,6 +413,9 @@ npm run build
310
413
 
311
414
  # Watch mode
312
415
  npm run dev
416
+
417
+ # Test locally before publishing
418
+ npm pack # Creates .tgz file for inspection
313
419
  ```
314
420
 
315
421
  ## License
package/package.json CHANGED
@@ -1,11 +1,11 @@
1
1
  {
2
2
  "name": "mcp-task-server",
3
- "version": "0.1.0",
3
+ "version": "0.1.2",
4
4
  "description": "MCP server for task management with multi-agent coordination",
5
5
  "type": "module",
6
6
  "main": "./dist/index.js",
7
7
  "bin": {
8
- "mcp-task-server": "./dist/index.js"
8
+ "mcp-task-server": "dist/index.js"
9
9
  },
10
10
  "files": [
11
11
  "dist"