Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

feat(integration): read-only MCP server — findings and resolve from IDE

Aperta
  • Qualcosa non va?
#317 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
github, java
Ambito
api, backend

Direzione di ricerca

Start by reading the repository README and the existing /resolve implementation to understand how findings, GitHub authorization, and persisted sessions are handled. Then identify the app's integration and API entry points. Done means documenting MCP tools and resources, listing findings for an owner, repository, and PR, and resolving threads with /resolve-equivalent authorization, without granting branch write access.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement java
Problem Statement

Greptile and CodeRabbit expose IDE/MCP integrations so maintainers can list review findings and drive resolution from Cursor or other agents. ThrillhouseBot is dashboard-only today — no programmatic surface for IDE workflows. This limits “daily driver” stickiness for teams that live in the editor.

Proposed Solution

Ship a read-only MCP server (phase 1 — no agentic fix PR yet) that exposes:

  • List open findings / threads for a PR (from persisted sessions + live GitHub state)
  • Resolve a finding thread (/resolve-equivalent) when the caller is authorized
  • Optional: link to dashboard session deep-link (#237 SSE / session persistence)

Defer to a later issue: opening fix PRs (#57 agentic fix), full agentic exploration (#63).

Related issues
  • #57 — agentic fix PR (post-1.0; out of scope here)
  • #63 — multi-agent workflow (post-1.0)
  • #34 — linters/SAST (complementary trust signals in v0.7.0)
  • #58 — issue-tracker context (another v0.7.0 integration)
  • #315 — 👀 command ack (orthogonal; MCP is separate transport)
Acceptance criteria
  • MCP server documents tools/resources in repo (docs/ or README)
  • Auth model defined (installation token / dashboard OAuth bridge / API token — see #326 if token-based)
  • Read-only listing of findings for (owner, repo, pr)
  • Resolve-thread action with same authorization rules as /resolve
  • No write access to PR branches from MCP in this issue
Alternatives considered
  • Full MCP parity with Greptile “Fix All” — too large; #57 covers agentic fix separately.
  • Dashboard-only forever — acceptable for v0.x but blocks IDE-native workflows.
Priority

Nice to have for v0.7.0 — after core trust signals (#34, #58, #60).

Code of Conduct
  • I have searched for existing issues and this is not a duplicate.
Lingua principale
Java
Stelle
35
Fork
7
Merge medio
9h 37m
PR unite (30g)
148

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di devops-thiago/ThrillhouseBot

Tutte le issue di devops-thiago/ThrillhouseBot

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.