Skip to content

mcp-server 3.2.0: update_project tool; handoff 422 names the membership story - #1037

Merged
mkreyman merged 3 commits into
masterfrom
fix/mcp-update-project
Nov 11, 2026
Merged

mkreyman merged 3 commits into
masterfrom
fix/mcp-update-project

Conversation

@mkreyman

Copy link
Copy Markdown
Owner

Closes #1036.

What changed

  • mcp-server/index.js: new update_project tool for PATCH /api/v1/projects/:id. It sends name, repo_url, description, tech_stack, mission and metadata. It never sends slug or status, and it refuses locally a call that names no field or has a malformed id. It uses orchestratorPinnedApiCall, as create_epic and update_epic do (orchestrator key verbatim, else user key). The description warns that a repo_url must be on only one active project.
  • mcp-server/lib/handoff.js: a 422 on a work-project post now names the fix, a membership story in that project, never a second channel. This matches the handoff skill (mkreyman/claude-config#1075).
  • README rows (root and mcp-server/), CHANGELOG, and a version bump to 3.2.0.

Testing

  • node --test test/*.test.js in mcp-server: all pass. This includes the new test/update_project_tool.test.js and the existing handoff_tool.test.js and delete_project_tool.test.js.

Review findings

  1. medium, fixed: the route sweep could not see orchestratorPinnedApiCall("PATCH", ...). The request now lives in lib/project-update.js as a literal apiCall("PATCH", ...). PATCH /api/v1/projects/:param is removed from the gap table, and its PUT twin is now duplicate.
  2. medium, fixed: the request shape was inline in index.js, against the repo's lib/ rule. It moved to lib/project-update.js with an injected apiCall, like the epic tools.
  3. low, fixed: the test only matched source text. It now runs the request with a recording apiCall (named fields only, never slug or status, an empty mission sent, an empty update and a malformed id refused with nothing sent), and it reads index.js through stripComments.

Risk

The new tool is additive. The server already enforces orchestrator role and the human anchor on PATCH. The one sharp edge is a repo_url that duplicates another active project, which makes resolve_project 409. The tool description says so; the server does not stop it.

How to revert

Revert the squash commit. Nothing reads update_project yet.

…ip story (#1036)

No MCP tool reached PATCH /api/v1/projects/:id, so no session could set a work
project's repo_url (Second Brain has none, so SessionStart resolves no channel
for second_brain). update_project sends name/repo_url/description/tech_stack/
mission/metadata with the orchestrator-pinned key, never slug or status, and
refuses an empty update locally. The handoff tool's 422 remediation on a work
project now names the membership-story fix instead of stopping at the cause.
# Conflicts:
#	mcp-server/CHANGELOG.md
#	mcp-server/package-lock.json
#	mcp-server/package.json
@mkreyman

Copy link
Copy Markdown
Owner Author

Review attested at e38c604d384e: The lean-review round ran from claude-config session 4610d003 on x1 (task a96be607e15f095db), so the loopctl store did not count it. It reviewed origin/master...fix/mcp-update-project at 590623d, using the bundle /home/mkreyman/workspace/loopctl/.git/review-context/range-origin-master...fix-mcp-update-project-at-590623d820825a07791e785f.bundle.md. It found 3 issues, all fixed in 7275222: the route sweep could not see the call, the request shape was inline instead of in lib/, and the test only matched source text. The commit after that is a merge of origin/master (CHANGELOG and version conflicts resolved to 3.12.0), and the mcp-server suite passes 914/914.

@mkreyman
mkreyman merged commit 613920a into master Nov 11, 2026
17 checks passed
@mkreyman
mkreyman deleted the fix/mcp-update-project branch November 11, 2026 04:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

mcp-server: update_project tool, so Second Brain can carry its repo_url; name the membership remedy on a work-project 422

1 participant