Skip to content

feat(warp): register the EGC MCP servers in ~/.warp/.mcp.json (#1678) - #1963

Merged
Fmarzochi merged 1 commit into
mainfrom
feat/warp-mcp-registration-1678
Oct 17, 2026
Merged

Fmarzochi merged 1 commit into
mainfrom
feat/warp-mcp-registration-1678

Conversation

@Fmarzochi

@Fmarzochi Fmarzochi commented Oct 17, 2026 •

Copy link
Copy Markdown
Owner

Part of #1678: Warp gets the EGC MCP servers the memory rule points at.

What changes

egc init registers egc-guardian and egc-memory under the standard mcpServers object of ~/.warp/.mcp.json, Warp's global file, whose servers Warp starts itself; merged so the person's own servers stay. Gated on ~/.warp, the Linux config directory ~/.config/warp-terminal or warp-terminal on PATH.

Warp also reads the files of other tools (Claude Code's ~/.claude.json, a project's .mcp.json, Codex's config.toml), but only spawns those once the person enables it, so the global file is where the servers run without a click. The project-scope .warp/.mcp.json is the project's own and is not touched.

Source: Warp MCP, read on 2026-10-17.

Verification

  • tests/lib/mcp-register.test.js 134/134 on the branch rebased over main c80350e (Junie and Copilot CLI included), two new cases: the target with its gate (the two directories and the binary) and the file it writes; a pre-existing server kept with its working_directory and an idempotent second run. Both fail on main.
  • tests/spec/integration-tiers.test.js 9/9 with the Warp row updated.
  • npm run preflight: no new findings. Local Sonar gate: 0 new findings.

Summary by cubic

egc init now registers egc-guardian and egc-memory in ~/.warp/.mcp.json, Warp's global file, whose servers Warp starts itself, so they run without the person enabling them.

  • Existing servers in the file are kept, and a second run is idempotent.
  • Registration is gated on ~/.warp, ~/.config/warp-terminal, or warp-terminal on PATH, so a machine without Warp gets nothing written.
  • The project-scope .warp/.mcp.json is the project's own and is not touched.

Written for commit 67c8624. Summary will update on new commits.

View guided diff Turn on auto-fix

Warp reads MCP servers from the mcpServers object of ~/.warp/.mcp.json, its
global file, and starts those servers itself; the files of other tools it
also reads (Claude Code's ~/.claude.json, a project's .mcp.json, Codex's
config.toml) only spawn once the person enables them, and the project-scope
.warp/.mcp.json is the project's own (docs.warp.dev/agents/capabilities/mcp,
read on 2026-10-17). egc init now registers egc-guardian and egc-memory in
the global file, merged so the person's own servers stay, gated on ~/.warp,
the Linux config directory ~/.config/warp-terminal or warp-terminal on PATH.

Tests: the target, its gate on the two directories and on the binary, the
file it writes, and a pre-existing server kept with its working_directory
and an idempotent second run.

Signed-off-by: Felipe Marzochi <fmarzochi@gmail.com>
@sonarqubecloud

Copy link
Copy Markdown

@codecov

codecov Bot commented Oct 17, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@Fmarzochi
Fmarzochi merged commit fa14655 into main Oct 17, 2026
36 checks passed
@Fmarzochi
Fmarzochi deleted the feat/warp-mcp-registration-1678 branch October 17, 2026 11:41
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.

1 participant