@jtalk22/slack-mcp 2.0.0 → 3.1.0

package/docs/LAUNCH-MATRIX.md

@@ -1,12 +1,14 @@
-# Capability Matrix (v2.0.0)
+# Capability Matrix (v3.0.0)
 
 Comparison matrix for release notes and channel posts. Keep competitor references unnamed.
 
-| Capability | This Release (`v2.0.0`) | Typical Session-Based Alternatives |
+| Capability | This Release (`v3.0.0`) | Typical Session-Based Alternatives |
 |---|---|---|
 | Read-only status checks | Enforced and verified in install flow | Often undocumented or mixed with refresh side effects |
 | Deterministic doctor exits | Enforced (`0/1/2/3`) with install-path coverage | Often ad-hoc or text-only |
 | Structured diagnostics | Shared fields in MCP/web error payloads | Mixed payload shapes |
+| Hosted HTTP auth default | Bearer required on `/mcp` by default | Often permissive by default |
+| Hosted HTTP CORS | Explicit allowlist (`SLACK_MCP_HTTP_ALLOWED_ORIGINS`) | Often wildcard/implicit |
 | Unknown token age handling | Explicit `unknown_age` semantics | Missing timestamp may appear as stale/failing |
 | Tool contract stability | No MCP tool rename/removal | Varies by release |
 | Local-first operator path | First-class (`stdio`, `web`) | Varies by runtime emphasis |

package/docs/LAUNCH-OPS.md

@@ -1,18 +1,18 @@
-# Launch Ops Runbook (v2.0.0)
+# Launch Ops Runbook (v3.0.0)
 
-This runbook defines launch-day monitoring, response rules, and reinforcement loops.
+This runbook defines launch-day monitoring and distribution for technical/operator channels (no X/Reddit dependency).
 
-## Same-Day Fanout Order
+## Same-Day Fanout Order (9 Channels)
 
-1. GitHub release publish (`v2.0.0`)
-2. npm publish confirm (`@jtalk22/slack-mcp@2.0.0`)
-3. MCP registry metadata update
-4. Smithery listing metadata parity update
-5. `awesome-mcp-servers` version update PR
-6. Glama listing refresh/update
-7. HN post + first comment
-8. X thread
-9. Reddit technical post
+1. GitHub release page refresh (`v3.0.0` copy + install-proof block)
+2. npm parity confirm (`@jtalk22/slack-mcp@3.0.0`)
+3. MCP registry parity confirm (`3.0.0`)
+4. Smithery listing metadata/parity update (or timestamped propagation note)
+5. `awesome-mcp-servers` listing PR refresh
+6. Glama metadata sync and canonical link verification
+7. HN thread update comment (high-signal install proof + support path)
+8. GitHub Discussions announcement/support threads update
+9. GitHub Pages/docs surface publish + link verification
 
 ## Monitoring Cadence
 
@@ -21,9 +21,10 @@ This runbook defines launch-day monitoring, response rules, and reinforcement lo
 
 Track:
 - install reports and blocker count
-- npm version/install confirmation
-- registry parity status
-- inbound issue volume and severity
+- npm/MCP parity state
+- listing propagation status (Smithery/Glama)
+- inbound issue and discussion severity
+- hosted migration questions (`SLACK_MCP_HTTP_AUTH_TOKEN`, CORS allowlist)
 
 ## Triage Rules
 
@@ -33,38 +34,38 @@ P1 install blocker:
 - add fix to patch queue
 
 Non-blocking request:
-- acknowledge and route to issue template
+- acknowledge and route to issue/discussion template
 - provide timeline as best effort
 
 ## Escalation Triggers
 
 1. If install failures exceed 3 unique reports in 24h:
-- pause outbound posting
+- pause outbound promotion
 - prioritize hotfix
 
 2. If support load exceeds 2 hours/day for 2 days:
-- move to stability-only mode
+- switch to stability-only mode
 - defer non-critical requests
 
 ## 24h / 48h / 72h Follow-Up
 
 24h:
-- publish release-health delta and short technical update
+- publish release-health delta and short technical summary
 
 48h:
-- answer top 5 recurring questions in docs
+- patch docs for top recurring setup questions
 
 72h:
-- publish `v2.0.1` only if launch defects are confirmed
+- ship `v3.0.1` only if launch defects are confirmed
 
 ## Evidence Log
 
 Use:
-- `docs/release-health/launch-log-template.md`
+- local `output/release-health/launch-log-template.md` (private by default)
 
 Capture:
 - channel
 - UTC timestamp
-- URL
+- URL or command evidence
 - action taken
-- observed result
+- observed result (`success|partial|blocked`)

package/docs/RELEASE-HEALTH.md

@@ -1,81 +1,77 @@
 # Release Health Tracking
 
-Use this to track installation reliability and operational load during the current release cycle.
+Operator telemetry is private-by-default in this repo.
 
-## One-command snapshot
+By default, release-health scripts write to local gitignored files under:
+
+- `output/release-health/`
+
+Use public docs output only when explicitly needed.
+
+## Snapshot (local default)
 
 ```bash
 node scripts/collect-release-health.js
 ```
 
 Outputs:
+
+- `output/release-health/latest.md`
+- `output/release-health/YYYY-MM-DD.md`
+
+Optional public output:
+
+```bash
+node scripts/collect-release-health.js --public
+```
+
+Outputs:
+
 - `docs/release-health/latest.md`
 - `docs/release-health/YYYY-MM-DD.md`
-- `docs/release-health/automation-delta.md` (when delta script is run)
 
-## Version parity report
+## Version Parity (local default)
 
 ```bash
 npm run verify:version-parity
 ```
 
 Output:
-- `docs/release-health/version-parity.md`
 
-If external registries are still propagating immediately after publish:
+- `output/release-health/version-parity.md`
+
+Optional public output:
 
 ```bash
-npm run verify:version-parity -- --allow-propagation
+node scripts/check-version-parity.js --public
 ```
 
-24-hour loop artifacts:
-- `docs/release-health/24h-start.md`
-- `docs/release-health/24h-end.md`
-- `docs/release-health/24h-delta.md`
-
-## What it captures automatically
-
-- npm downloads (last week, last month)
-- npm latest version
-- GitHub stars, forks, open issues
-- GitHub 14-day traffic views/clones (owner token required via `gh auth`)
-- Count of `deployment-intake` issues
+## Delta Report (local default)
 
-## 14-day targets
-
-- weekly downloads: `>= 180`
-- qualified deployment-intake submissions: `>= 2`
-- support load: `<= 2 hours/week`
+```bash
+node scripts/build-release-health-delta.js
+```
 
-## Manual fields to track alongside snapshots
+Defaults:
 
-- Weekly support minutes spent.
-- Deployment-intake quality (clear use case, owner, timeline).
-- Traffic source notes (search, referrals, docs traffic).
-- External \"first run succeeded\" confirmations (issues/discussions).
+- `--after output/release-health/latest.md`
+- `--out output/release-health/automation-delta.md`
 
-## Recommended cadence
+## Prepublish Dry Run (local default)
 
-- Days 1-7: daily snapshot
-- Days 8-14: every 2-3 days
+```bash
+npm run verify:release-dry-run
+```
 
-## Automated cadence (low-touch)
+Output:
 
-- Workflow: `.github/workflows/release-health.yml`
-- Triggers:
-  - scheduled at `07:15` and `19:15` UTC
-  - manual `workflow_dispatch`
-- Outputs per run:
-  - workflow summary with current snapshot and baseline delta
-  - artifacts: `docs/release-health/latest.md`, `docs/release-health/automation-delta.md`
+- `output/release-health/prepublish-dry-run.md`
 
-## Local delta command
+## CI Workflow
 
-If you want to compare two explicit snapshots locally:
+Workflow: `.github/workflows/release-health.yml`
 
-```bash
-node scripts/build-release-health-delta.js \
-  --before docs/release-health/24h-start.md \
-  --after docs/release-health/24h-end.md \
-  --out docs/release-health/24h-delta.md
-```
+- collects local snapshots in `output/release-health/`
+- publishes workflow summary
+- uploads artifacts for maintainers
+- does not commit telemetry files back to the repo

package/docs/TROUBLESHOOTING.md

@@ -161,6 +161,33 @@ cat /tmp/slack-web-api.log
 cat /tmp/slack-web-api.error.log
 ```
 
+### Hosted HTTP `/mcp` Returns 503 or 401
+
+If you run `node src/server-http.js`, `/mcp` is protected by default.
+
+`503 http_auth_token_missing` means you did not set:
+
+```bash
+SLACK_MCP_HTTP_AUTH_TOKEN=change-this
+```
+
+`401 unauthorized` means your request is missing or using the wrong bearer token.
+
+Example request:
+
+```bash
+curl http://localhost:3000/mcp \
+  -H "Authorization: Bearer $SLACK_MCP_HTTP_AUTH_TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"1.0.0"}}}'
+```
+
+For local-only testing (not remote exposure), you can opt out:
+
+```bash
+SLACK_MCP_HTTP_INSECURE=1 node src/server-http.js
+```
+
 ---
 
 ## Claude Desktop Issues

package/docs/WEB-API.md

@@ -1,6 +1,15 @@
 # Web API Reference
 
-The Slack Web Server exposes all MCP tools as REST endpoints, accessible from any browser or HTTP client. This is useful for accessing Slack from claude.ai (which doesn't support MCP).
+The Slack Web Server exposes all MCP tools as REST endpoints, accessible from any browser or HTTP client.
+
+Claude web now supports remote MCP connectors on paid plans, so this Web API mode is best used for:
+- local localhost dashboard workflows
+- REST/API integrations
+- fallback operation when you do not want to host a remote MCP endpoint
+
+References:
+- https://support.anthropic.com/en/articles/11995447-connectors-in-claude
+- https://support.anthropic.com/en/articles/11175166-about-custom-integrations-using-remote-mcp
 
 ## Starting the Server
 
@@ -269,9 +278,9 @@ The UI auto-connects with the default API key:
 4. Send messages directly from the browser
 
 **Using with claude.ai:**
-1. Open the web UI alongside claude.ai
-2. Browse/search for relevant conversations
-3. Copy-paste message content into claude.ai as needed
+1. Preferred: add a remote MCP connector in Claude settings if you run a remote endpoint.
+2. Fallback: open the web UI alongside claude.ai for local browsing/search.
+3. Copy-paste relevant message content as needed.
 
 ---
 

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "@jtalk22/slack-mcp",
   "mcpName": "io.github.jtalk22/slack-mcp-server",
-  "version": "2.0.0",
-  "description": "Session-based Slack access for Claude - DMs, channels, search, and threads. Local-first with your existing Slack session.",
+  "version": "3.1.0",
+  "description": "Session-based Slack MCP for Claude and MCP clients: local-first workflows, secure-default HTTP.",
   "type": "module",
   "main": "src/server.js",
   "bin": {
@@ -24,45 +24,40 @@
     "tokens:auto": "node scripts/token-cli.js auto",
     "tokens:clear": "node scripts/token-cli.js clear",
     "screenshot": "node scripts/capture-screenshots.js",
+    "build:social-preview": "node scripts/build-social-preview.js",
+    "build:demo-mobile": "node scripts/build-mobile-demo.js",
+    "build:demo-mobile:gif": "node scripts/build-mobile-demo.js --gif",
     "record-demo": "node scripts/record-demo.js",
+    "social-preview:update": "node scripts/update-github-social-preview.js --headed",
+    "cf:browser": "node scripts/cloudflare-browser-tool.js",
     "metrics:release-health": "node scripts/collect-release-health.js",
     "metrics:release-health:delta": "node scripts/build-release-health-delta.js",
-    "verify:version-parity": "node scripts/check-version-parity.js"
+    "impact:push:v3": "node scripts/impact-push-v3.js --dry-run",
+    "impact:push:v3:apply": "node scripts/impact-push-v3.js --apply",
+    "verify:version-parity": "node scripts/check-version-parity.js",
+    "verify:release-dry-run": "node scripts/release-preflight.js"
   },
   "keywords": [
+    "claude",
     "mcp",
-    "mcp-server",
     "model-context-protocol",
     "slack",
     "slack-api",
-    "slack-mcp",
-    "slack-integration",
-    "claude",
     "claude-desktop",
-    "claude-code",
-    "cursor",
-    "llm",
-    "ai",
-    "ai-assistant",
-    "automation",
-    "workflow-automation",
-    "developer-tools",
     "cli",
-    "productivity",
-    "messaging",
-    "message-search",
-    "direct-messages",
-    "channels",
-    "workspace",
+    "developer-tools",
+    "mcp-server",
     "session-based",
+    "claude-code",
+    "local-first",
     "session-mirroring",
-    "slack-dm",
-    "slack-threads",
-    "workspace-search",
-    "mcp-tools",
-    "mcp-stdio",
-    "mcp-http",
-    "open-source"
+    "slack-mcp",
+    "secure-by-default",
+    "llm",
+    "slack-integration",
+    "ai-agents",
+    "automation",
+    "productivity"
   ],
   "author": "jtalk22",
   "license": "MIT",
@@ -70,7 +65,7 @@
     "type": "git",
     "url": "git+https://github.com/jtalk22/slack-mcp-server.git"
   },
-  "homepage": "https://jtalk22.github.io/slack-mcp-server/public/demo.html",
+  "homepage": "https://jtalk22.github.io/slack-mcp-server/",
   "bugs": {
     "url": "https://github.com/jtalk22/slack-mcp-server/issues"
   },
@@ -86,9 +81,14 @@
     "lib/",
     "public/",
     "scripts/",
-    "docs/",
+    "docs/*.md",
+    "docs/assets/",
+    "docs/images/*.png",
+    "docs/images/*.svg",
     "README.md",
-    "LICENSE"
+    "LICENSE",
+    "server.json",
+    "smithery.yaml"
   ],
   "devDependencies": {
     "playwright": "^1.57.0"