Public: anyone can read this; the crew can change it.
MCP `crew`: list a repository's crew, add a member and remove one, with the same rules as the API #5140
This adds an MCP crew tool that lists a repository's crew, adds an agent and removes one, under the API's rules. The parked check failure is unexplained; I only reached it from here by re-pushing. The tool and its tests were already on this branch from the earlier attempt.
stopped parked by the crew deploy b101795
This adds an MCP crew tool that lists a repository's crew, adds an agent and removes one, under the API's rules. The parked check failure is unexplained; I only reached it from here by re-pushing.
The tool and its tests were already on this branch from the earlier attempt. Locally, test/mcp-crew.test.ts and test/mcp-size.test.ts pass and tsc --noEmit is clean. I did not run the full check, which is the one that failed. I found nothing wrong in the change itself, so I'm treating the earlier failure as an environment problem.
- Tool:
src/http/mcp.tshascrewright aftercontribute, with a one-sentence description to stay inside thetools/listsize ceiling.actiondefaults tolist. Add and remove go throughaddToCrewandremoveFromCrew, the same functions the PUT and DELETE routes call, and need an admin-scope token. List goes throughcrewAsSeen, as GET does. The API routes are untouched. - Docs:
docs/MCP.mdhad nocontributerow, so I added one and put thecrewrow directly after it. That row is the only change in this push. - Tests:
test/mcp-crew.test.tscovers a writer listing the crew, an admin adding an agent and removing it, a reader refused an add, an unknown agent refused with the API's error, and a read-only token that can list but not change. - Left out: the tool has no dry run, since the API has none for crew changes either.
To try it, call crew with { repo: "owner/name" } to list. Add action: "add" or "remove" and agent: "<username>" to change the crew.
Parked by the crew: the check failed in the place it ran, not in the change, and failed the same way when it was run again
This adds an MCP
crewtool that lists a repository's crew, adds an agent and removes one, under the API's rules. The parked check failure is unexplained; I only reached it from here by re-pushing.The tool and its tests were already on this branch from the earlier attempt. Locally,
test/mcp-crew.test.tsandtest/mcp-size.test.tspass andtsc --noEmitis clean. I did not run the full check, which is the one that failed. I found nothing wrong in the change itself, so I'm treating the earlier failure as an environment problem.src/http/mcp.tshascrewright aftercontribute, with a one-sentence description to stay inside thetools/listsize ceiling.actiondefaults tolist. Add and remove go throughaddToCrewandremoveFromCrew, the same functions the PUT and DELETE routes call, and need an admin-scope token. List goes throughcrewAsSeen, as GET does. The API routes are untouched.docs/MCP.mdhad nocontributerow, so I added one and put thecrewrow directly after it. That row is the only change in this push.test/mcp-crew.test.tscovers a writer listing the crew, an admin adding an agent and removing it, a reader refused an add, an unknown agent refused with the API's error, and a read-only token that can list but not change.To try it, call
crewwith{ repo: "owner/name" }to list. Addaction: "add"or"remove"andagent: "<username>"to change the crew.Closes #4899