feat(init): register the redis MCP server per agent and unhide the command - #1104
Draft
VaskoAtanasovRedis wants to merge 2 commits into
Draft
feat(init): register the redis MCP server per agent and unhide the command#1104VaskoAtanasovRedis wants to merge 2 commits into
VaskoAtanasovRedis wants to merge 2 commits into
Conversation
VaskoAtanasovRedis
force-pushed
the
feat/init/7-mcp
branch
from
August 13, 2026 08:16
1377e51 to
8588919
Compare
VaskoAtanasovRedis
force-pushed
the
feat/init/7-mcp
branch
from
August 13, 2026 08:20
8588919 to
f731b25
Compare
VaskoAtanasovRedis
force-pushed
the
feat/init/7-mcp
branch
2 times, most recently
from
August 13, 2026 13:14
fc02db5 to
d97380b
Compare
VaskoAtanasovRedis
force-pushed
the
feat/init/7-mcp
branch
from
August 14, 2026 09:16
d97380b to
f1adac1
Compare
…mmand Each targeted agent's project config (.mcp.json, .cursor/mcp.json, .vscode/mcp.json with type stdio) gains a credential-free redis server: a sh launcher sources .env at start, so the URL never lands in a committed file. The runner prefers uvx and falls back to a Docker bridge (host.docker.internal rewrite); with neither, the config is still written for uvx and a note says so. Codex is user-scoped and reported skipped. Existing configs are merged, foreign servers survive, a replaced redis entry is reported with its old command masked, and invalid JSON is left untouched. The default onboarding path is now complete end to end, so the command leaves hiding and gets its docs page.
The launcher gains --add-host=host.docker.internal:host-gateway (Linux Engine does not define that name; Docker Desktop has it built in), and the URL rewrites anchor on :// so a password or a foo.localhost host can never be rewritten. Also in this slice's scope: - tests asserting agent-specific MCP files pin --agent claude instead of relying on machine detection (test(init): pin --agent in MCP assertions); the live full-run assertion follows the solo-Claude layout to .claude/skills - the docs describe the one deliberate overwrite: a differing redis MCP entry is replaced with its old command masked, env/skill files stay kept (docs(cli): describe MCP replace vs env kept)
VaskoAtanasovRedis
force-pushed
the
feat/init/7-mcp
branch
from
August 19, 2026 13:24
f1adac1 to
61249fd
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.
Stacked on #1103. MCP registration per agent - and the slice that unhides
redisctl init..mcp.json/.cursor/mcp.json/.vscode/mcp.json(servers+type: stdio); codex is user-scoped and skipped, the skills cover it.sh -c 'set -a; . ./.env ...'launcher sources.envwhen the agent starts the server; tests assert no URL value ever lands in a committed config.docker run mcp/redisbridge with://-anchoredhost.docker.internalrewrites; with neither, the config is written for uvx and a note points at installing uv.redisentry is replaced with its old command masked in the note; invalid JSON is kept untouched (the PoC crashed here).Deviation: rewritten config files come out key-sorted (serde_json without
preserve_order; enabling it would change ordering workspace-wide). Only files we actually modify are affected.Verify:
redisctl init --agent claude,vscode --no-install-cli;grep -c 'redis://' .mcp.jsonprints 0; re-run reads unchanged.