Ermöglicht es einem Coding Agent, Review-Kommentare aus Preview-Deployments zu lesen, darauf zu reagieren und diese zu lösen.
Auch bekannt als maple-kit/maple, @maple-kit/mcp
- Stars
- 22
- Tools
- —
- Downloads, 30 Tage
- —
- Neueste Version
- 0.17.1
- Letzter Commit
- 3. Nov. 2026
- Lizenz
- Apache-2.0
Was ist Maple MCP?
Maple ist ein MCP server. Ermöglicht es einem Coding Agent, Review-Kommentare aus Preview-Deployments zu lesen, darauf zu reagieren und diese zu lösen.
Zusammenfassung generiert aus dem README des Projekts
Über Maple MCP server
Maple bietet Coding Agents eine Möglichkeit, direkt mit Review-Kommentaren zu interagieren, die in Preview-Deployments gefunden werden. Es erlaubt einem AI-Client, spezifisches Feedback zu lesen, den Kontext über Viewports oder Screenshots zu verstehen, notwendige Code-Änderungen anzuwenden und diese Kommentare als gelöst zu markieren. So entsteht ein geschlossener Kreislauf, in dem ein Agent visuelle oder funktionale Kritik während des Entwicklungsprozesses autonom bearbeiten kann.
Entwickler können diesen Server lokal nutzen, indem sie Kommentare aus einem .maple/ Verzeichnis lesen, oder ihn mit GitHub verbinden, indem sie einen GITHUB_TOKEN, MAPLE_GITHUB_OWNER und MAPLE_GITHUB_REPO bereitstellen. Der Server enthält einen spezialisierten Stop Hook, der für Clients wie Claude Code entwickelt wurde, um zu verhindern, dass ein Agent seine Aufgabe beendet, solange noch offene Kommentare existieren. Er unterstützt zudem das Management von Merge Gates, indem er über die MAPLE_URL mit bereitgestellten Routen kommuniziert, um Check-Ergebnisse neu zu veröffentlichen, sobald die Kommentare gelöst sind.
Was du damit machen kannst
- 1Automatisierte KommentarlösungEin Agent kann einen spezifischen Kommentar identifizieren, den Fix anwenden und den Commit aufzeichnen, der das Problem behoben hat.
- 2Überwachung von neuem FeedbackEin Entwickler kann einen Agenten anweisen, darauf zu warten, dass ein Reviewer neue Kommentare in einem bestimmten Branch postet.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
So installierst du Maple MCP
Formate geprüft am 10. Nov. 2026Maple MCP in Claude Code installieren
$ claude mcp add --env GITHUB_TOKEN=<YOUR_GITHUB_TOKEN> maple -- npx -y @maple-kit/mcpMaple MCP in Cursor installieren
~/.cursor/mcp.json
{
"mcpServers": {
"maple": {
"command": "npx",
"args": [
"-y",
"@maple-kit/mcp"
],
"env": {
"GITHUB_TOKEN": "<YOUR_GITHUB_TOKEN>"
}
}
}
}Maple MCP in VS Code installieren
.vscode/mcp.json
{
"servers": {
"maple": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@maple-kit/mcp"
],
"env": {
"GITHUB_TOKEN": "<YOUR_GITHUB_TOKEN>"
}
}
}
}Maple MCP in Claude Desktop installieren
claude_desktop_config.json
{
"mcpServers": {
"maple": {
"command": "npx",
"args": [
"-y",
"@maple-kit/mcp"
],
"env": {
"GITHUB_TOKEN": "<YOUR_GITHUB_TOKEN>"
}
}
}
}Maple MCP in Codex installieren
~/.codex/config.toml
[mcp_servers.maple] command = "npx" args = ["-y", "@maple-kit/mcp"] [mcp_servers.maple.env] GITHUB_TOKEN = "<YOUR_GITHUB_TOKEN>"
Maple MCP in Gemini CLI installieren
~/.gemini/settings.json
{
"mcpServers": {
"maple": {
"command": "npx",
"args": [
"-y",
"@maple-kit/mcp"
],
"env": {
"GITHUB_TOKEN": "<YOUR_GITHUB_TOKEN>"
}
}
}
}Konfiguration
GITHUB_TOKENSecretA token that can read and write the repository's pull request comments. Required for the github store.
MAPLE_GITHUB_OWNERThe repository's owner. Required for the github store.
MAPLE_GITHUB_REPOThe repository. Required for the github store.
MAPLE_STOREgithub, the default when a forge is configured, or file, the comments under .maple/ on this machine.
| Name | Beschreibung | Typ |
|---|---|---|
| GITHUB_TOKEN | A token that can read and write the repository's pull request comments. Required for the github store. | Secret |
| MAPLE_GITHUB_OWNER | The repository's owner. Required for the github store. | |
| MAPLE_GITHUB_REPO | The repository. Required for the github store. | |
| MAPLE_STORE | github, the default when a forge is configured, or file, the comments under .maple/ on this machine. |
Automatisierte Checks
Geluften am 12. Nov. 2026Vollständiger Bericht →Unsere automatisierten Checks bestanden. Das ist kein Security-Audit: Lies den Code und gib dem Server nur den minimal notwendigen Zugriff. Wie die Checks funktionieren
- Source Repository verknüpft und erreichbarBestanden
- Open Source Lizenz (OSI)Bestanden
- Commit oder Release im letzten JahrBestanden
- Package-Name ähnelt keinem populären PackageBestanden
- Remote Endpoint nutzt HTTPSNicht geprüft
- Destruktive Tools sind markiertNicht geprüft
- Keine versteckten Anweisungen an das ModellBestanden
- Kein kritischer Hinweis im Paket oder seinen AbhängigkeitenBestanden
README
Auf GitHub ansehen@maple-kit/mcp
The Model Context Protocol server that hands a coding agent the review comments Maple collected on a preview deployment.
Pre-release. Every package here is 0.x and makes no compatibility promise.
The agent waits for a comment, reads it with its context — file:line from
the tagger, the viewport, the screenshot, the mock it was written under — makes
the change, and resolves it against the commit that fixed it. The reviewer's
half is the overlay; the two meet in the store.
Install
npm install @maple-kit/mcp
Two binaries ship: maple-mcp, the server, and maple-stop-hook, which stops
an agent from calling itself finished while comments are still open.
Connect an agent
A client starts the server with no arguments, so it is configured through the
environment. In Claude Code's .mcp.json:
{
"mcpServers": {
"maple": {
"command": "npx",
"args": ["-y", "-p", "@maple-kit/mcp", "maple-mcp"],
"env": { "MAPLE_GITHUB_OWNER": "acme", "MAPLE_GITHUB_REPO": "web" }
}
}
}
and run the client under op run --env-file so GITHUB_TOKEN never lands in a
file. A missing value fails at startup rather than on the first tool call.
| Name | Secret | What it is |
|---|---|---|
GITHUB_TOKEN |
Yes | A token that can read and write pull-request comments. Required for the github store. |
MAPLE_GITHUB_OWNER |
No | The repository's owner. Required for the github store. |
MAPLE_GITHUB_REPO |
No | The repository. Required for the github store. |
MAPLE_GITHUB_API |
No | The API root, for Enterprise Server. |
MAPLE_STORE |
No | github, the default when a forge is configured, or file, the default when none is: the comments under .maple/. |
MAPLE_BRANCH |
No | The branch the Stop hook checks, else the one checked out. The server ignores it. |
MAPLE_URL |
No | The deployed route's mount URL. A resolve asks it to republish the gate. |
MAPLE_GATE_TOKEN |
Yes | For CI only: the gate App's installation token. Not with MAPLE_URL. |
MAPLE_GATE_APP_ID |
No | The gate App's id, so it updates its own check run rather than another's. |
MAPLE_REQUIRE_APPROVAL |
No | true to hold the gate until somebody approves, matching the route and CI. |
With no forge
Set none of GITHUB_TOKEN, MAPLE_GITHUB_OWNER and MAPLE_GITHUB_REPO and the
server reads and writes the comments fileStore() keeps under .maple/ in its
working directory's repository, so the loop works on a laptop with no pull
request. MAPLE_STORE=file says so explicitly. It is a laptop's store, not a
preview pod's: docs/connectors.md has the argument. The Stop hook reads the
same folder for the branch checked out in the session's working directory, and
stays silent where there is no .maple/ folder, no comments for the branch or
no repository.
Tools
| Tool | Reads | What it does |
|---|---|---|
list_comments(branch, statuses?) |
✓ | Return the review comments on a branch, newest first. |
wait_for_comments(branch, cursor?, timeoutMs?) |
✓ | Block until a new comment arrives or the wait elapses. Returns status "timeout" rather than failing when nothing arrives. |
resolve_comment(id, sha, note?) |
Mark a comment resolved, recording the commit that addressed it. | |
get_comment_context(id, branch) |
✓ | Return everything needed to act on one comment: anchor, viewport, surrounding markup and any replay link. A comment written under a Maple Mock carries mock.recipe and mock.replay, a link to the page in that state. |
start_solo(previewUrl) |
Start a bridge on localhost and return the link that pairs a deployed preview with it. The reviewer opens the link in their browser and the comments they write there land in .maple/ for list_comments and wait_for_comments to read. They never count toward the merge gate. |
wait_for_comments is clamped to 55 seconds because every coding client cuts a
tool call off at 60, and it emits notifications/progress every 15 seconds. A
timeout is a result: an agent that treats one as an error stops looping the
first time nobody is looking. Its cursor is a timestamp; omit it on the first
call to drain whatever is already waiting.
The Stop hook
MCP gives a server no way to interrupt a client, so the loop is closed from the
other end. Claude Code's Stop hook runs when the agent believes it is
finished, and Maple's answers with the comments still open:
{
"hooks": {
"Stop": [
{ "hooks": [{ "type": "command", "command": "npx -y -p @maple-kit/mcp maple-stop-hook" }] }
]
}
}
The Maple Claude Code plugin registers it for you. It blocks while a comment
is open or needs_reverify, at most eight stops in a row per session; on the
ninth it lets the session end and says what is still open, which beats an agent
resolving comments to escape. The count is kept per session_id in the system
temp directory, and a stop no block caused starts it again.
The hook does not see .mcp.json's env. That block is handed to the MCP
server alone; a hook runs in the client's own environment. So
MAPLE_GITHUB_OWNER, MAPLE_GITHUB_REPO and GITHUB_TOKEN have to be set
where the client itself starts — under the same op run --env-file — or the
hook fails naming the one missing. With neither of the first two set, it reads
the comments under .maple/ for the current branch instead, and lets every
stop through where there are none. MAPLE_BRANCH defaults to the branch checked out in the
session's working directory.
Resolving clears the gate
With MAPLE_URL set to a deployed route's mount URL, such as
https://web-482.preview.acme.dev/api/maple, resolve_comment asks that route
to republish maple/visual-review, so an agent that resolves the last comment
with nothing left to push does not leave the check holding on finished work.
The request carries the branch and GITHUB_TOKEN, which must be able to push
to the repository. The route decides the verdict and publishes with the gate
App's own credentials, which never leave it. A failed refresh is logged to
stderr and the resolve is still recorded.
MAPLE_GATE_TOKEN is the other way, for CI: a gate App installation token the
server publishes with directly. It expires an hour after it is minted, so it
suits a job, not a session. Setting both fails at startup.
Documentation
- The agent loop
- The merge gate
- The
maple-reviewskill turns a pull request's```maplecomments into a worklist without the server.
Licence
Apache-2.0. See LICENSE and NOTICE.
Maple MCP Fragen
Wie füge ich Maple MCP zu Claude Code hinzu?
Führe claude mcp add --env GITHUB_TOKEN=<YOUR_GITHUB_TOKEN> maple -- npx -y @maple-kit/mcp in deinem Terminal aus. Füge --scope user hinzu, damit der Server in jedem Projekt verfügbar ist.
Wie füge ich Maple MCP zu Cursor hinzu?
Öffne ~/.cursor/mcp.json und füge den Server unter mcpServers hinzu, mit der Cursor-Config aus dem Installationsabschnitt oben.
Woher weiß der Agent, was er fixen muss?
Der Agent nutzt Tools, um den Kontext der Kommentare zu erfassen, einschließlich Dateiname, Zeilennummer, Viewport, Screenshots und dem umgebenden Markup.
Kann ich Maple auch ohne GitHub-Repository nutzen?
Ja, falls keine GitHub-Credentials bereitgestellt werden, liest und schreibt der Server Kommentare in ein lokales .maple/ Verzeichnis im Arbeitsverzeichnis.
Was passiert, wenn der Agent versucht, die Aufgabe zu beenden, während noch Kommentare offen sind?
Der maple-stop-hook kann verhindern, dass der Agent die Aufgabe abschließt, indem er die Session blockiert, solange noch offene Kommentare existieren oder eine erneute Verifizierung erforderlich ist.