NotePlan / NotePlan/noteplan-mcp
noteplan_edit_content.edit_line doesn't seem to honor the dryRun flag
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 16
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Using MCP inspector, on a scratch note called scratch, I ran:
{
"method": "tools/call",
"params": {
"name": "noteplan_edit_content",
"arguments": {
"action": "edit_line",
"title": "scratch",
"content": "* Spike test task ^spk1a2 EDITED",
"line": 3,
"dryRun": true
},
"_meta": {
"progressToken": 3
}
}
}
...then looked at the note in NotePlan and found that it was actually updated with the new text. I'd, of course, expect the content to not change when using dryRun: true.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the TypeScript handler for the noteplan_edit_content tool and its edit_line action, then trace how the dryRun argument is handled. Reproduce the request with MCP inspector against the scratch note. Done means dryRun: true reports the operation without changing the note content.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100