@mtaap/mcp 0.2.12 → 0.4.1

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
@@ -498,6 +498,12 @@ report_error -> abandon_task -> list_tasks -> assign_task (retry or pick differe
498
498
 
499
499
  ## Usage
500
500
 
501
+ There are two ways to use the Collab MCP server:
502
+
503
+ ### Option 1: Local Installation (Recommended for Claude Desktop)
504
+
505
+ Install and run locally using stdio transport:
506
+
501
507
  1. Configure your environment variables
502
508
  2. Add to your MCP client configuration (Claude Desktop, OpenCode, etc.):
503
509
 
@@ -506,7 +512,7 @@ report_error -> abandon_task -> list_tasks -> assign_task (retry or pick differe
506
512
  "mcpServers": {
507
513
  "collab": {
508
514
  "command": "npx",
509
- "args": ["@mtaap/mcp"],
515
+ "args": ["-p", "@mtaap/mcp", "collab-mcp"],
510
516
  "env": {
511
517
  "COLLAB_BASE_URL": "https://collab.mtaap.de",
512
518
  "COLLAB_API_KEY": "your-api-key"
@@ -518,6 +524,27 @@ report_error -> abandon_task -> list_tasks -> assign_task (retry or pick differe
518
524
 
519
525
  3. Use the tools from your AI agent
520
526
 
527
+ ### Option 2: Remote HTTP Server
528
+
529
+ Connect to the Collab MCP server using the Streamable HTTP transport. This is useful for:
530
+ - Claude.ai and Claude Mobile (which don't support local MCP servers)
531
+ - Environments where you can't install npm packages
532
+
533
+ Configure your MCP client to connect to the remote server:
534
+
535
+ ```json
536
+ {
537
+ "mcpServers": {
538
+ "collab": {
539
+ "url": "https://collab.mtaap.de/mcp",
540
+ "headers": {
541
+ "X-API-Key": "your-api-key"
542
+ }
543
+ }
544
+ }
545
+ }
546
+ ```
547
+
521
548
  ## Troubleshooting
522
549
 
523
550
  ### "COLLAB_API_KEY is required"