WinstonRedGuard MCP Server
Bridge your WinstonRedGuard monorepo into MCP agents for governance, pipelines, memory, and OSINT tooling with optional read-only defaults.
Overview
WinstonRedGuard MCP Server is a Build-phase MCP server that exposes WinstonRedGuard monorepo governance, pipelines, memory, and OSINT tools to MCP agents with read-only defaults.
What is this MCP server?
- WinstonRedGuard monorepo bridge: governance, pipelines, memory, and OSINT-oriented tools
- PyPI package wrg-mcp-server (1.0.8) with pipx runtime hint and stdio default transport
- WRG_REPO_ROOT required when installed outside the repo; auto-detect when run from inside
- WRG_MCP_ALLOW_MUTATIONS defaults to 0 for read-only; set to 1 for memory_set and pipeline_run
- Optional HTTP transports: streamable-http or sse via --transport for remote deployments
- Server version 1.0.8
- Default mutation policy: WRG_MCP_ALLOW_MUTATIONS=0 (read-only)
- 3 transport options documented: stdio, streamable-http, sse
Community signal: 1 GitHub stars.
What problem does it solve?
Your agent cannot safely see WRG governance, pipeline state, or repo memory when those systems live only inside a custom monorepo with no MCP surface.
Who is it for?
Builders already using WinstonRedGuard who want MCP-driven repo governance and pipelines without bespoke scripts per tool.
Skip if: Anyone without a WRG monorepo checkout or who needs a generic cloud MCP with no local repo root.
What do I get? / Deliverables
After configuration with WRG_REPO_ROOT, your assistant can query—and optionally mutate when enabled—the WRG toolchain from the same session as your code edits.
- MCP-accessible WRG governance and pipeline visibility from your agent
- Optional memory and pipeline mutations when WRG_MCP_ALLOW_MUTATIONS=1
- HTTP-deployable MCP when using streamable-http or sse transport
Recommended MCP Servers
Journey fit
Agent-tooling in build is where you wire custom repos and automation into Claude/Cursor; WRG is explicitly a monorepo bridge for MCP agents rather than end-user analytics. Agent-tooling fits because the server exposes repo-scoped tools (memory, pipelines, governance) that extend what your coding agent can do inside a WRG checkout.
How it compares
Monorepo-specific MCP bridge with governance and OSINT tools, not a hosted universal database or diagram MCP.
Common Questions / FAQ
Who is WinstonRedGuard MCP Server for?
Developers and agent operators working in a WinstonRedGuard monorepo who want Claude Code or similar clients to call WRG tools over MCP.
When should I use WinstonRedGuard MCP Server?
Use it when you are building or operating agent workflows that must read WRG memory, pipelines, or governance data from inside the repo.
How do I add WinstonRedGuard MCP Server to my agent?
Install wrg-mcp-server via pipx, set WRG_REPO_ROOT to your monorepo path, add stdio MCP config, and keep WRG_MCP_ALLOW_MUTATIONS at 0 until you need writes.