BitSquare/Codeman
2
0
Fork 0
mirror of https://github.com/Ark0N/Codeman.git synced 2026-10-13 10:49:41 +02:00
Code Issues Packages Projects Releases Wiki Activity

feat(mcp-sync): sync GitHub Copilot CLI's MCP servers too

Browse Source 
Copilot CLI keeps its user MCP list in ~/.copilot/mcp-config.json (COPILOT_HOME moves it) but is
not a Codeman run mode, so it has no registry entry. Add the copilot-json dialect (mcpServers,
tools ["*"], type local/http/sse, checked against `copilot mcp add` 1.0.94) and declare Copilot as
a sync-only target in src/mcp-sync-targets.ts, listed after the registry CLIs. A server switched
off with `copilot mcp disable` is recorded in settings.json (disabledMcpServers), not on the
entry: sync reads that list so it is not copied, and reports the target unreadable if the file
is not valid JSON instead of guessing.
This commit is contained in:
Devvyn
2026-10-09 18:42:00 +08:00
parent 3a0cee6b90
commit 57d5c7b1c2
12 changed files with 372 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.changeset/mcp-sync-copilot.md
+5
View File
@@ -0,0 +1,5 @@
---
'aicodeman': minor
---
MCP server sync now includes GitHub Copilot CLI. If `copilot` is installed (or `~/.copilot/mcp-config.json` exists), its MCP servers are copied into your other CLIs and theirs into it, with the same rules as the others: only missing servers are added, nothing is edited or removed, a server you switched off with `copilot mcp disable` is not copied, and a file that receives env values or headers stays readable by you only. `COPILOT_HOME` is followed. Copilot is not a Codeman run mode, so it is declared as a sync-only target rather than a CLI-registry entry.