Changes
- library: the Library's MCP servers go to Hermes and eight other agents (EUPH on Discord: Hermes gets skills but no MCP) — agents with a skills folder had no MCP target, so the MCP editor had nowhere to write for them. Now Hermes ($HERMES_HOME/config.yaml mcp_servers, comments and other keys kept), omp (agent/mcp.json), Kimi Code (mcp.json), Devin (mcp_config.json), Grok Build (config.toml [mcp_servers.*], no SSE), Droid (~/.factory/mcp.json), Qoder and Qoder CN (settings.json), Cline (cline_mcp_settings.json or $CLINE_MCP_SETTINGS_PATH) and Command Code (mcp.json, no SSE) take them, each in the schema its own source reads; a user's own keys on magpie's entries survive an edit and their own servers show to bring in. WorkBuddy, OpenHanako and fx still get none: the first two run a server only once approved or switched on inside them, and fx drops its whole file over one entry it refuses. Each format was read back by the agent's own CLI in a sandbox HOME (hermes, kimi, devin, droid, qodercli, cline, cmd, grok). TestHermesMCP, TestHermesMCPFound and TestAgentMCPFiles fail without the change. go vet, go build -tags nogui (darwin, GOOS=linux), GOOS=windows go build, go test -tags nogui ./... pass; library-items, shared-skills, click-scroll, old-webkit pass.
- Per-model preferences: the machinery three changes share (#288)
Install
Download from usemagpie.ai, or curl -fsSL https://usemagpie.ai/install.sh | sh. An installed magpie updates itself.
- macOS (Apple Silicon):
magpie-darwin-arm64.dmg - macOS (Intel):
magpie-darwin-amd64.dmg - Windows:
magpie-windows-amd64.exe(ARM:magpie-windows-arm64.exe) - Linux:
magpie-linux-amd64/magpie-linux-arm64(needs GTK 3 and WebKitGTK 4.1) - Terminal only:
magpie-cli-<os>-<arch>