Replace developer-cli MCP server with per-command Claude Code skills#875
Draft
Replace developer-cli MCP server with per-command Claude Code skills#875
Conversation
…, aspire-restart, team-interrupt
…d team-interrupt skill
…ontextProtocol package references
tjementum
force-pushed
the
pp-1161-replace-developer-cli-mcp-server-with-skills
branch
from
e0f6f0f to
224f330
Compare
|
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 & Motivation
The custom developer-cli MCP server wrapped the same CLI commands the developer CLI already exposes (
build,test,format,lint,run,restart,stop,e2e,send-interrupt-signal). It was the source of recurring bugs - hardcoded ports, Aspire startup races returning misleading success messages, file locking on Windows, worktree-binding gotchas tied to the MCP startup directory - and a recent Claude Code change broke its progress notifications, removing its main remaining benefit. The CLI fallback (dotnet run --project developer-cli -- <command>) already worked correctly and is naturally worktree-aware.This change drops the MCP server entirely and replaces it with per-command Claude Code skills. Each skill documents the exact CLI invocation, flags, and timing notes so agents pick the right command via skill matching instead of through an MCP tool wrapper.
build,test,format,lint,e2e,aspire-restart,team-interrupt) under.claude/skills/claude-command send-interrupt-signal --team X --agent YCLI subcommand that writes the agent signal file at~/.claude/teams/{team}/signals/{agent}.signaland prints the interrupt ID on stdout for the caller to prefix to its follow-upSendMessagedeveloper-cli/Commands/McpCommand.cs(~890 lines), drop theModelContextProtocolpackage references fromdeveloper-cli/DeveloperCli.csproj, remove thedeveloper-clientry from.mcp.json, and drop"developer-cli"fromenabledMcpjsonServersin.claude/settings.jsonAGENTS.md, and thepre-tool-use-bash.shhook error messages to reference the skills and direct CLI invocation form.claude/hooks/send-interrupt.shbash equivalent of the new CLI subcommandPortAllocation.LoadFromauto-picks the first free base port from[9100, 9200, ..., 9900]for worktrees on first load (root checkout keeps9000), and thebasePortpositional argument is removed frompp runandpp restartsince.workspace/port.txtis now the single source of truthcheck-interrupt.shhook reason so an agent that has already processed the matching message ID continues instead of stoppingChecklist