MCP v2.2.0: wiki curation tools (unpublish, archive, delete)#107
Merged
MCP v2.2.0: wiki curation tools (unpublish, archive, delete)#107
Conversation
Agents could create and publish wiki articles via MCP but had no way to retract bad drafts — low-signal articles (session summaries, commit recaps) were piling up with no cleanup path short of curl. Adds three new MCP tools that gate on LOOPCTL_USER_KEY per the "destructive ops above orchestrator" rule in CLAUDE.md: - knowledge_unpublish → POST /articles/:id/unpublish - knowledge_archive → POST /articles/:id/archive - knowledge_delete → DELETE /articles/:id (archives under the hood) No REST API changes — the endpoints already existed and already required role: user. This PR only exposes them through the MCP server. Bumps mcp-server to 2.2.0, updates CHANGELOG and README (tool count 42 → 45, LOOPCTL_USER_KEY description expanded to list all tools that require it). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
knowledge_unpublish,knowledge_archive,knowledge_delete— so agents can retract low-signal wiki drafts without curl. All three route to REST endpoints that already exist and already requirerole: :user; this PR only exposes them via MCP.LOOPCTL_USER_KEYper the "destructive ops above orchestrator" rule inCLAUDE.md(same pattern asknowledge_bulk_publishanddelete_project).mcp-serverto 2.2.0; updatesCHANGELOG.mdandREADME.md(tool count 42 → 45,LOOPCTL_USER_KEYdescription now lists every tool that requires it).Motivation
Debrief-style skills were creating wiki drafts liberally but there was no retract path via MCP. Bad drafts accumulated until someone did
curl. These three tools close the curation loop so orchestrators can clean up after themselves (the debrief skill is being updated separately inclaude-configto draft-only behaviour and lean on these new tools).Trust model check
:userinarticle_controller.ex:24andarticle_workflow_controller.ex:1-5.Test plan
mix precommit— compile, format, credo --strict, dialyzer, 2286 tests passnode --check mcp-server/index.jsknowledge_unpublish/knowledge_archive/knowledge_deleteagainst a real tenant draftmcp-v2.2.0on the merge commit andnpm publishfrommcp-server/