Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

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

Open
  • Is something wrong?
#317 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github, java
Domain
api, backend

Research direction

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.

Written by the indexing model from the issue text.

Description

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.
Dominant language
Java
Stars
35
Forks
7
Avg merge
9h 23m
Merged PRs (30d)
154

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from devops-thiago/ThrillhouseBot

All issues in devops-thiago/ThrillhouseBot

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.