Skip to main content
MCP server CX Codex

Maple — Claude Code MCP server: review comments inside your agent

Hands a coding agent the review comments pinned to a live preview: it reads the context, edits the code and closes the note with a commit.

Install into Claude Code · Platform CLI All methods and platforms ↓
claude mcp add --env GITHUB_TOKEN=<GITHUB_TOKEN> --env MAPLE_GITHUB_OWNER=<MAPLE_GITHUB_OWNER> --env MAPLE_GITHUB_REPO=<MAPLE_GITHUB_REPO> --env MAPLE_STORE=<MAPLE_STORE> --transport stdio mcp -- npx -y @maple-kit/mcp
Open on GitHub

What Maple does

Maple gathers reviewer notes left on a running frontend, and this server passes them to the agent. The agent waits for a new comment, gets its anchor file:line, viewport, screenshot and the mock it was written under, makes the edit, then resolves the comment against the fixing commit. Reviewers stay in the overlay; both sides meet in the store.

Install the package with npm install @maple-kit/mcp. You get two binaries: maple-mcp for the server and maple-stop-hook, which blocks an agent from declaring itself done while comments remain open. Clients start the server with no arguments, so configuration lives in environment variables. The github store needs GITHUB_TOKEN with read and write access to pull-request comments plus MAPLE_GITHUB_OWNER and MAPLE_GITHUB_REPO. A missing value fails at startup instead of on the first tool call.

With no forge, comments are read from and written to .maple/ in the working directory, which keeps the loop usable on a laptop without a pull request. That store is meant for a local machine, not a preview pod. Every package is 0.x with no compatibility promise, so pin it if the workflow matters to your team. wait_for_comments caps at 55 seconds because clients cut a call at 60, and a timeout counts as a result — agents that treat it as an error stop looping the moment nobody is watching.

What it helps with

  • read a review comment together with its file and line anchor
  • wait for the next comment instead of polling the page by hand
  • resolve a comment and record the commit that fixed it
  • run the review loop on a laptop without a pull request
  • keep an agent from finishing while comments are still open

Example prompts for the agent

  • List the open review comments on branch feature/cart
  • Wait for a new comment, then fix what it points at
  • Resolve that comment and record the commit sha

How to install Maple

Platform CLI

claude mcp add --env GITHUB_TOKEN=<GITHUB_TOKEN> --env MAPLE_GITHUB_OWNER=<MAPLE_GITHUB_OWNER> --env MAPLE_GITHUB_REPO=<MAPLE_GITHUB_REPO> --env MAPLE_STORE=<MAPLE_STORE> --transport stdio mcp -- npx -y @maple-kit/mcp

Replace <…> with your own values

Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more

Questions about Maple

How do I install Maple in Claude Code?

Run claude mcp add maple -e GITHUB_TOKEN=<GITHUB_TOKEN> -- npx -y @maple-kit/mcp. For the full setup with owner, repo and store: `claude mcp add --env GITHUB_TOKEN=<GITHUB_TOKEN> --env MAPLE_GITHUB_OWNER=<MAPLE_GITHUB_OWNER> --env MAPLE_GITHUB_REPO=<MAPLE_GITHUB_REPO> --env MAPLE_STORE=<MAPLE_STORE> --transport stdio mcp -- npx -y @maple-kit/mcp`.

What does Maple do?

It feeds your agent the review comments collected on a preview deployment and gives it tools to list them, wait for new ones and close them with a commit reference.

Does Maple work without GitHub?

Yes. Leave GITHUB_TOKEN, MAPLE_GITHUB_OWNER and MAPLE_GITHUB_REPO unset and the server uses the comments under .maple/ in its working directory. MAPLE_STORE=file states that explicitly.

Similar MCP servers

All MCP servers for Code review and refactoring →

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor