Summary
The Logseq HTTP API supports logseq.Editor.removeBlock to delete blocks, but the MCP server doesn't expose this functionality.
Use case
When using the MCP server to manage blocks (e.g., adding test blocks or cleaning up duplicates), there's no way to remove blocks programmatically. Currently users have to manually delete blocks in Logseq.
Workaround
Direct API calls work fine:
curl -X POST http://127.0.0.1:12315/api \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{"method": "logseq.Editor.removeBlock", "args": ["<block-uuid>"]}'
Proposed solution
Add a new tool like logseq_delete_block or logseq_remove_block that wraps the logseq.Editor.removeBlock API method.
Thanks for this useful MCP server!
Summary
The Logseq HTTP API supports
logseq.Editor.removeBlockto delete blocks, but the MCP server doesn't expose this functionality.Use case
When using the MCP server to manage blocks (e.g., adding test blocks or cleaning up duplicates), there's no way to remove blocks programmatically. Currently users have to manually delete blocks in Logseq.
Workaround
Direct API calls work fine:
Proposed solution
Add a new tool like
logseq_delete_blockorlogseq_remove_blockthat wraps thelogseq.Editor.removeBlockAPI method.Thanks for this useful MCP server!