Skip to content

Add vardoger - #113

Merged
its-mash merged 2 commits into
mcpmux:mainfrom
dstrupl:add-vardoger
Apr 24, 2026
Merged

Add vardoger#113
its-mash merged 2 commits into
mcpmux:mainfrom
dstrupl:add-vardoger

Conversation

@dstrupl

@dstrupl dstrupl commented Apr 22, 2026

Copy link
Copy Markdown
Contributor

Adds io.github-dstrupl-vardoger — a stdio MCP server that personalizes AI coding assistants by analyzing local conversation history from Cursor, Claude Code, Codex, Copilot CLI, Windsurf, Cline, and OpenClaw. Runs entirely on the user's machine; no API keys, no network egress. Source: https://github.com/dstrupl/vardoger (PyPI: vardoger, Apache-2.0).

Metadata

  • Transport: stdio, invoking vardoger mcp (installed via pipx install vardoger, Python ≥3.11).
  • Auth: none — reads local filesystem paths only (~/.cursor/, ~/.claude/, ~/.codex/, etc.).
  • Platforms: all.
  • Categories: developer-tools, productivity, ai-ml.
  • Optional input: VARDOGER_MCP_PLATFORM (lets users pin the host platform if the server's auto-detect picks the wrong one — not required in the common case).

Local validation

  • node scripts/validate.js servers/io.github-dstrupl-vardoger.jsonPASS
  • node scripts/validate.js --check-conflictsNo conflicts found across 106 server file(s).
  • node scripts/validate.js --all → no FAIL or CONFLICT output

DCO signed off in the commit.

Signed-off-by: David Strupl <dstrupl@gmail.com>
dstrupl added a commit to dstrupl/vardoger that referenced this pull request Apr 22, 2026
Opened [mcpmux/mcp-servers#113](mcpmux/mcp-servers#113)
from `dstrupl:add-vardoger` with DCO sign-off. Upstream validator
(`node scripts/validate.js`) reports PASS + no ID/alias conflicts
against the 106-server baseline. Upstream has no CI suite; the PR
sits in `REVIEW_REQUIRED` waiting on a human maintainer.

Bookkeeping:

- Table row flipped from `Not started — prep complete` to `Submitted`
  with `Submitted on = 2026-04-22`, Surface column now points to the
  live PR, and Notes record the verification run + current review state.
- "Last refreshed" note appended with the PR link so the next session
  can see the McpMux event without scanning the table.
- "Next session pickup" reorganized: McpMux moved out of §2
  (Ready-to-publish) and into §1 (Poll reviewer queues) with a concrete
  `gh pr view` poll command and the on-merge action (copy `mergedAt`
  into Live on, Status → Live).

No code or plugin-manifest changes — this is status-table bookkeeping
only.

Made-with: Cursor
Comment thread servers/io.github-dstrupl-vardoger.json Outdated
Switch the VARDOGER_MCP_PLATFORM env-var input from a free-text field
to a select with explicit options for each supported host platform
(cursor, claude-code, codex, openclaw, copilot, windsurf, cline) plus
an "Auto-detect (default)" empty-value option that maps to vardoger's
existing auto-detect fallback. Drops the now-redundant placeholder and
the "Valid values: ..." sentence from the description.

Addresses @its-mash's review on PR mcpmux#113.

Signed-off-by: David Strupl <dstrupl@gmail.com>
@dstrupl

dstrupl commented Apr 23, 2026

Copy link
Copy Markdown
Contributor Author

Thanks for the review, @its-mash! Great suggestion — just pushed 80e6cb2 to the PR branch that switches VARDOGER_MCP_PLATFORM from text to select.

The options mirror vardoger's seven supported platform identifiers plus an explicit "Auto-detect (default)" entry (empty-string value) that maps to the server's existing auto-detect fallback in _env_default_platform():

"options": [
  { "value": "",            "label": "Auto-detect (default)", "description": "Let vardoger pick based on the calling host." },
  { "value": "cursor",      "label": "Cursor" },
  { "value": "claude-code", "label": "Claude Code" },
  { "value": "codex",       "label": "Codex" },
  { "value": "openclaw",    "label": "OpenClaw" },
  { "value": "copilot",     "label": "GitHub Copilot CLI" },
  { "value": "windsurf",    "label": "Windsurf" },
  { "value": "cline",       "label": "Cline" }
]

I also dropped the now-redundant placeholder and trimmed the "Valid values: …" sentence from description since the options make it obvious.

Happy to drop the empty "Auto-detect" option and make the select strictly one-of-7 if you would prefer a cleaner UX — let me know. Validation still passes (npm run validate:all → 106 PASS / 0 FAIL, npm run check-conflicts → no conflicts).

dstrupl added a commit to dstrupl/vardoger that referenced this pull request Apr 23, 2026
Mirror the change pushed to mcpmux/mcp-servers#113: switch the
VARDOGER_MCP_PLATFORM input from free-text to a select with explicit
options for each supported host platform (cursor, claude-code, codex,
openclaw, copilot, windsurf, cline) plus an "Auto-detect (default)"
empty-value option that maps to the server's existing auto-detect
fallback.

No change required in src/vardoger/mcp_server.py: the server contract
and accepted values are identical; only the host input widget changes.

Update MARKETPLACE_STATUS.md: bump "Last refreshed" to 2026-04-23 and
document the review response in the McpMux row's Notes.
@its-mash
its-mash merged commit 495adbc into mcpmux:main Apr 24, 2026
1 check passed
dstrupl added a commit to dstrupl/vardoger that referenced this pull request Apr 24, 2026
McpMux PR #113 was merged by @its-mash on 2026-04-24 at 17:03 UTC as
merge commit 495adbc. vardoger is now in the McpMux bundle; the
gateway refreshes from main roughly hourly, so Cursor, Claude Desktop,
VS Code, and Windsurf users on the McpMux desktop gateway pick up the
entry automatically.

Bookkeeping only — no code or plugin-manifest changes:

- MARKETPLACE_STATUS.md McpMux row: Submitted -> Live,
  Live on = 2026-04-24, Notes record the merge commit and the bundle
  refresh cadence.
- Last refreshed bumped to 2026-04-24 with a summary of the flip;
  previous refresh notes pushed down one level.
- Next session pickup: trimmed the stale PR #113 polling bullet and
  left a short pointer confirming the merge.
- PRD.md Phase 4 checkbox for McpMux ticked and status line rewritten
  to Live, per MARKETPLACE_STATUS.md "How to update" step 3.
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.

2 participants