Selvedge vs Docguard — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Selvedge vs Docguard
In-depth architectural comparison of the Selvedge and Docguard MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Selvedge
Developer Tools · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
Docguard
Developer Tools · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
Verdict Summary: Choose Selvedge if you need specialized Developer Tools tools running via a local process. Choose Docguard if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Selvedge when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Change tracking for AI-era codebases. AI agents call it to log structured change events (entity + diff + reasoning) before the session ends, then query history with diff, blame, history, changeset, and search. Captures the intent that would otherwise evaporate.
Deterministic documentation-drift detection for AI agents. Validates a project's canonical docs against its actual code — no LLM guessing; every finding has a stable code and a suggested fix. Five read-only tools over stdio: guard, score, explain, verify-claims, diagnose. npx -y docguard-cli mcp
Category & Scope
Tools & Capabilities Breakdown
Selvedge Tools (8)
log_change
Record a change event with entity, diff, and reasoning. `rename_from` + `change_type="rename"` records the dual-event rename pattern; `change_type="supersede"` re-opens a reverted decision (append-only); optional `constraint` / `stale_when` keep the decision's principle and its invalidation conditi…
diff
History for an entity or entity prefix, each row annotated with `superseded_by
blame
Most recent change + context for an exact entity, plus the derived decision `status` (active / reverted / reopened)
history
Filtered history across all entities
changeset
All events grouped under a named feature/task slug
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Selvedge is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Docguard belongs to Developer Tools using local stdio subprocess. Select Selvedge when you need capabilities focused on developer tools and Docguard when you require tools for developer tools.
Prior change attempts on an entity + inferred outcome (tried → reverted → re-opened) — call it before editing. Optional `fuzzy` query adds semantically similar records (needs the `semantic` extra; falls back to substring)
stale_decisions
Decisions due for a revisit: past their `revisit_after` and still in active use (`flag="revisit_due"`), or whose `stale_when` condition matched a later change (`flag="review_suggested"`)