Wigolo vs Visual Memory MCP
Two MCP servers from our AI & ML ranking, compared on live data - updated nightly, never sponsored.
Bottom line · 2026-09-30
Visual Memory MCP records significantly more monthly package installs (27,267 vs 3,512); both are actively maintained, with commits inside the last month.
How they differ in kind
Wigolo focuses on: Local-first web intelligence for AI agents - no keys, no cloud, no metered bill. Visual Memory MCP focuses on: @putervision/vision-memory-mcp is a zero-infrastructure, local-first Model Context Protocol (MCP) server and CLI tool that provides AI coding assistants (such as Cursor, Claude Code, Gemini, or… Environment-variable extraction: Wigolo yielded 7 variables; Visual Memory MCP yielded no variables extracted.
What each one does
Wigolo
Local-first web intelligence for AI agents - no keys, no cloud, no metered bill.
From the project's README.
Visual Memory MCP
@putervision/vision-memory-mcp is a zero-infrastructure, local-first Model Context Protocol (MCP) server and CLI tool that provides AI coding assistants (such as Cursor, Claude Code, Gemini, or Copilot) with visual state caching using perceptual hashing, local CLIP embeddings, and transition graphs to eliminate repetitive vision LLM calls.
From the project's README.
14 signals, side by side
| Signal | Wigolo | Visual Memory MCP |
|---|---|---|
| Monthly installs | 3,512 | 27,267 |
| GitHub stars | 5,432 | 87 |
| Last commit | 2026-09-29 | 2026-09-29 |
| Releases · last 90 days | 9 | 6 |
| In the registry since | Jul 2026 | Jul 2026 |
| Registry versions | 3 | 14 |
| Documented tools | not extracted - see README | not extracted - see README |
| Env vars extracted | 7 | none extracted - see README |
| Runs | local (stdio) | local (stdio) |
| Endpoint auth | local only | local only |
| Maintenance | actively maintained | actively maintained |
| License | NOASSERTION | NOASSERTION |
| Language | TypeScript | TypeScript |
| Category rank | #2 of 117 | #3 of 117 |
Environment variables found in the READMEs
These are extracted names, not a requiredness check. Project docs may mark them optional or require other setup.
Wigolo
- WIGOLO_LLM_PROVIDER
- GEMINI_API_KEY
- WIGOLO_SEARCH
- WIGOLO_GITHUB_TOKEN
- WIGOLO_TLS_TIER
- WIGOLO_EAGER_WARMUP
- WIGOLO_API_TOKEN
Visual Memory MCP
No environment variables were extracted from the README setup. Check the project documentation for other authentication or configuration steps.
Which one, for what
Derived from the signals above, not hands-on testing.
Pick Wigolo if…
- → release velocity matters - 9 releases in 90 days vs 6
- → category standing - #2 of 117 maintained AI & ML servers
Pick Visual Memory MCP if…
- → you want the more widely installed option - 27,267 monthly installs vs 3,512
- → measured package adoption matters - 27,267 monthly installs
Who's behind them
Wigolo - knockoutez: 1 MCP server tracked, 1 maintained, 5,432 combined stars.
Visual Memory MCP - putervision: 6 MCP servers tracked, 6 maintained, 304 combined stars. Full record.
Not sold on either?
The next-ranked AI & ML servers we track:
Quick answers
Is Wigolo better than Visual Memory MCP?
Package installs favor Visual Memory MCP: 27,267 monthly installs to 3,512. Wigolo still ranks #2 of 117 maintained AI & ML servers. Data as of 2026-09-30; we haven't hands-on tested either.
Can I use Wigolo and Visual Memory MCP together?
Yes - MCP clients accept multiple servers in one config, so you can enable both AI & ML servers side by side. If their tools overlap, keep the one whose toolset fits to keep your agent's tool list lean.
What environment variables do their READMEs document?
Wigolo: 7 environment variables extracted from the README setup; Visual Memory MCP: no environment variables extracted from the README setup. Extraction does not rule out other authentication or configuration steps; check each project's current documentation.
Keep exploring: best AI & ML servers · TypeScript servers · all comparisons · every server
Methodology: package-usage signal = npm/PyPI installs (last month, platform APIs) · maintenance = commit recency + release cadence (GitHub) · tool lists and environment-variable names extracted from each project's README · endpoint auth from our own nightly probes. We haven't hand-tested these servers; everything here is data as of 2026-09-30.