# Reported issues for mcp-server

Pod holds 14 of 14 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to [mcp-server](/mcp/mcp-server-cachly-dev).

## Most discussed

### feat: VS Code extension deep integration — inline Brain annotations

The cachly VS Code extension currently provides a sidebar panel. We should add inline code annotations powered by the brain:

**Proposed features:**
- Hover over a function: show if there is a known lesson for this code path
- Yellow warning gutter icon when a brain lesson mentions this file
- Code lens: `[2 brain lessons for this module]` — click to open
- `Ctrl+Shift+B`: open brain recall for symbol under cursor

**Implementation:** Extension listens for `brain_predict` output and maps `file_p

[Read the thread](https://github.com/cachly-dev/cachly-mcp/issues/15) · 2026-05-06 · open · 2 comments

### feat: webhook notifications for brain events

Allow external systems to subscribe to brain events:

- `lesson_stored` — fired when `learn_from_attempts` is called
- `session_started` / `session_ended`
- `prediction_made` — when `brain_predict` generates predictions

**Config example:**
```json
{"webhook_url": "https://your-server.com/brain-events", "events": ["lesson_stored"]}
```

Useful for triggering Slack alerts, CI workflows, or custom dashboards when the team brain learns something new.

[Read the thread](https://github.com/cachly-dev/cachly-mcp/issues/10) · 2026-05-06 · open · 2 comments

### docs: self-hosted Docker Compose deployment guide

Many enterprise users want to run cachly on-premises. We should provide a complete self-hosted setup guide.

**Minimum viable guide should cover:**
- `docker-compose.yml` for the brain API + Postgres
- Environment variable reference (all required vars)
- Reverse proxy setup (nginx/Caddy examples)
- First-time JWT generation
- Health check endpoints
- Backup strategy for Postgres data

**Audience:** DevOps engineers at mid-size companies with data residency requirements.

This would also help wit

[Read the thread](https://github.com/cachly-dev/cachly-mcp/issues/14) · 2026-05-06 · open · 1 comment

### feat: brain export/import for backup and migration

✅ Implementiert in `src/handlers/share.ts`.

Verfügbare Tools:
- **`brain_share`** — erstellt einen shareable Snapshot mit UUID-Link
- **`brain_import`** — importiert via `share_id` mit `dry_run`-Option und Conflict-Handling
- **`brain_export_md`** — exportiert alle Lessons als Markdown (confidence-sortiert)
- **`brain_import_meta`** — importiert k-anonyme Meta-Lessons aus dem Global Commons

**Offener Gap:** Kein NDJSON/JSON-Export für maschinenlesbares Backup (nur Markdown). Wird als separates

[Read the thread](https://github.com/cachly-dev/cachly-mcp/issues/13) · 2026-05-06 · closed · 1 comment

### perf: streaming support for large session_start payloads

Currently `session_start` returns the full session context as a single JSON payload. For teams with large brains (1000+ lessons), this can exceed LLM context windows.

**Proposed solution:**
- Add `stream: true` option to `session_start`
- Return lessons as a stream of JSON objects
- Client accumulates them, LLM sees them progressively
- Reduces time-to-first-token significantly

**Alternative:** `session_start_summary` that returns only the top-N most relevant lessons for the current `focus` to

[Read the thread](https://github.com/cachly-dev/cachly-mcp/issues/12) · 2026-05-06 · closed · 1 comment

### feat: Slack/Discord bot integration for team brain alerts

Provide a ready-to-use Slack/Discord bot that surfaces brain activity to the team:

- Post a message when a critical lesson is stored (`severity: critical`)
- Daily digest of lessons learned by the team
- `/brain ask <question>` slash command
- `/brain recall <topic>` for instant recall in chat

**Slack App Manifest** and **Discord Bot** setup guide would be part of this.

This makes the team brain ambient and actionable without requiring every engineer to install the MCP server.

[Read the thread](https://github.com/cachly-dev/cachly-mcp/issues/11) · 2026-05-06 · open · 1 comment

### feat: GitHub Actions integration — auto-learn from CI failures

✅ Vollständig implementiert in `cachly-dev/cachly-action`.

`action.yml` unterstützt 5 Modi:
- **setup** — MCP-Config + copilot-instructions + Codebase-Indexierung
- **learn** — Auto-Learn aus Git-Commits bei PR-Merge
- **scan** — Vorhersage von PR-Failures + GitHub-Comment
- **hygiene** — Autonomes Aufräumen veralteter Lessons
- **confirm** — CI-Outcome zurück ans Brain (Self-Calibration via `brain_confirm_ci`)

Beispiel-Usage wie im Issue beschrieben ist live. Schließe dieses Issue als erledig

[Read the thread](https://github.com/cachly-dev/cachly-mcp/issues/9) · 2026-05-06 · closed · 1 comment

### fix: broken GitHub links in README (mcp-server → cachly-mcp)

Several links in the README point to the old repository name `cachly-dev/mcp-server` which has been moved to `cachly-dev/cachly-mcp`.

Affected links:
- `https://github.com/cachly-dev/mcp-server/issues`
- `https://github.com/cachly-dev/mcp-server`
- Star badge link in header

These return 404 and make the project look unmaintained.

[Read the thread](https://github.com/cachly-dev/cachly-mcp/issues/8) · 2026-05-06 · closed · 1 comment

## Most recent

### security: document CACHLY_JWT token rotation procedure

Users with long-lived JWTs have no documented procedure for rotating their API keys. This is a security risk if a token is leaked.

**Required documentation:**
1. How to generate a new JWT from `cachly.dev/settings`
2. How to revoke an old token
3. How to update MCP config files after rotation
4. Recommended rotation interval (we suggest 90 days)

This should be added to the README under a new `## Security` section.

[Read the thread](https://github.com/cachly-dev/cachly-mcp/issues/7) · 2026-05-06 · closed · 1 comment

### fix: server.json version not bumped on npm publish

When publishing a new version to npm, the `server.json` file in the repository root was not being updated in sync with `package.json`. This caused Glama and Smithery to display stale version metadata.

**Root cause:** The release workflow does not include a step to update `server.json` version field.

**Fix:** Add a `preversion` npm script that syncs `server.json` version from `package.json`.

[Read the thread](https://github.com/cachly-dev/cachly-mcp/issues/6) · 2026-05-06 · closed · 1 comment

### docs: add CONTRIBUTING.md with development setup guide

Contributors currently have no guide for local development, testing, and submitting PRs. We should add a `CONTRIBUTING.md` that covers:

- Prerequisites (Node 20+, npm)
- Running tests: `npm test`
- Building: `npm run build`
- Submitting PRs: branch naming, commit format
- Code style: we use ESLint + Prettier

This is especially important as we plan to open-source more internals.

[Read the thread](https://github.com/cachly-dev/cachly-mcp/issues/5) · 2026-05-06 · closed · 1 comment

### feat: npx @cachly-dev/mcp-server init — auto-install git hooks for CLS Layer 5

✅ Implementiert — der Einstiegspunkt ist `autopilot` (nicht `init`), was dem Landing-CTA entspricht (`npx @cachly-dev/mcp-server@latest autopilot`).

**Git-Hook-Integration:** `src/cls-hook.ts` — `installOrUpgradeHook()` erstellt/aktualisiert `.git/hooks/post-commit` idempotent, erkennt bestehende Hooks und hängt sicher an. Graceful skip wenn kein `CACHLY_JWT` gesetzt.

**Autopilot:** `src/handlers/advanced.ts` — generiert CLAUDE.md, `.github/copilot-instructions.md`, `.continue/cachly-autopilot

[Read the thread](https://github.com/cachly-dev/cachly-mcp/issues/3) · 2026-05-06 · closed · 1 comment

### fix: server.json description had outdated tool count (63 → 67)

After adding `crystal_view`, `compact_recover`, `brain_from_git`, `brain_predict_failures` in v0.9.7 the tool count jumped from 63 to 67. The `server.json` description still showed 63.

[Read the thread](https://github.com/cachly-dev/cachly-mcp/issues/2) · 2026-05-06 · closed · 1 comment

### docs: add usage examples for brain_from_git and brain_predict_failures

The four new tools added in v0.9.7 (`crystal_view`, `compact_recover`, `brain_from_git`, `brain_predict_failures`) need usage examples in the README.

Closing with the v0.9.7 CHANGELOG entry — already shipped.

[Read the thread](https://github.com/cachly-dev/cachly-mcp/issues/1) · 2026-05-06 · closed · 1 comment

The remaining reports are on [the project's issue tracker](https://github.com/cachly-dev/cachly-mcp/issues).