aio-codeflow vs io.github.klewicki7/vibelens-mcp
aio-codeflow is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑19.
aio-codeflow is a plugin bundle for AI coding tools published by aiocean. No marketplace we read lists it any more. io.github.klewicki7/vibelens-mcp is an MCP server published by klewicki7. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.klewicki7/vibelens-mcp | |
|---|---|---|
| Community marketplace aiocean/claude-plugins | Removed on 2026-10-19 Version: 2.0.3 Forks (GitHub): 1 Stars (GitHub): 4 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.0 Downloads/month (npm): 279 Downloads/week (npm): 32 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | aio-codeflowno longer listed · | io.github.klewicki7/vibelens-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 4 | 0 |
| Forks (GitHub) (differs) | 1 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (vibelens-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Parts of the bundle (differs) | 10 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/aiocean/claude-plugins | github.com/klewicki7/vibelens |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of aio-codeflow
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Find out what is actually true about your codebase before you change it. Index the repository once, then ask what calls this, what breaks if I change it, and which parts are…
-
Local-first codebase intelligence and Impact summaries for TypeScript and JavaScript using fallow
-
Deep code indexing for AI agents. FTS5 + embeddings + call graphs + git intelligence. Fully local.
-
Essential development tools for code review, debugging, and refactoring. Includes strategic agents for high-level decisions and tactical skills for specific operations.
-
Codebase intelligence for Claude Code. Indexes your repo into five layers (Graph, Git, Docs, Decisions, Code Health) and gives Claude deep understanding of architecture…
-
socraticode io.github.giancarloerra/socraticode
MCP server for enterprise local codebase indexing, semantic search, and code dependency graphs.
What each says it does
aio-codeflow
Understand, plan, debug, and review code as one coordinated workflow — codebase discovery, dependency mapping, implementation planning, root-cause debugging, and pre-merge review.
io.github.klewicki7/vibelens-mcp
VibeLens MCP tool for AI to visualize code changes with inline annotations in VS Code/Cursor
How to run each
aio-codeflow
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.klewicki7/vibelens-mcp As a local MCP server: npm package
claude mcp add --env "YOUR_API_KEY=<YOUR_YOUR_API_KEY>" --transport stdio vibelens-mcp -- npx -y vibelens-mcpRequires: YOUR_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of aio-codeflow publish no settings it asks for, so we do not compare settings.
What it can do: aio-codeflow · What it can do: io.github.klewicki7/vibelens-mcp · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.