The Parsemend MCP server.
It runs on your machine as parsemend mcp, from @parsemend/cli 0.3.0. Your agent uses it to list your issues, read one in full and post the fix back.
Install and sign in
Node 20 or later. parsemend login opens your browser; in CI, pass --token.
npm install -g @parsemend/cli
parsemend loginRegister it with your agent
Add --cwd /path/to/repo to pin a repository.
claude mcp add parsemend -- parsemend mcpcodex mcp add parsemend -- parsemend mcp{
"mcpServers": {
"parsemend": {
"command": "parsemend",
"args": ["mcp"]
}
}
}{
"mcpServers": {
"parsemend": {
"command": "parsemend",
"args": ["mcp"]
}
}
}The four tools
The first three are all an agent needs. The fourth is optional.
| Tool | What it does | Model call | Network |
|---|---|---|---|
| list_issueslist_issues(project?, status?, limit?) | Lists issues across your projects, unresolved by default, with the short id your agent uses for everything else (api-47). | No model call | Reads from Parsemend |
| get_issue_contextget_issue_context(issue, include?) | Returns the issue's context bundle: the issue and project, sample events with stack traces, connected errors, the trace tree, related logs and any earlier analysis. Your agent reads your repository itself and fixes it with its own tools. | No model call | Reads from Parsemend |
| post_backpost_back(issue, summary?) | Posts the current git diff and a summary to the issue, so the fix is recorded next to the error it addresses. The tool description tells your agent to ask you first. | No model call | Sends the diff to Parsemend, only when you approve |
| analyze_issueanalyze_issue(issue, model?, skip_plan?) | Runs Parsemend's own root-cause explorer and planner locally. Optional, and it needs a repository code mapping, which today means a GitHub-connected repository. | Your own provider key, spent on your machine | Calls your model provider |
Every flag is in the customer docs.
Questions
What is the Parsemend MCP server?
A local Model Context Protocol server in the @parsemend/cli package. Run as parsemend mcp, it lets a coding agent list your issues, read one in full and post a fix back.
Does any tool send data from my machine?
Only post_back, which sends the diff and a summary to the issue. analyze_issue, if you use it, calls your own model provider. The others only read.
Why does analyze_issue need GitHub when nothing else does?
It maps stack frames to files through code mappings, which today need a GitHub-connected repository. The other three tools need no mappings.