com.vibsync/vibsync vs Inkwell
com.vibsync/vibsync is an MCP server published by vibsync.com. Marketplaces we read that list it: 1 (Official MCP Registry). Inkwell is an MCP server published by veronchenko. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  com.vibsync/vibsync |  Inkwell |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.3 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.14.0 Forks (GitHub): 0 Stars (GitHub): 2 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 | com.vibsync/vibsync | Inkwell |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 2 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.vibsync.com/mcp) | On your machine (docker.io/foreigndmitryi/inkwell-memory:0.14.0) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 0 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/loosedays/vibsync-mcp | github.com/veronchenko/inkwell-memory |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 39 h ago, requires a key | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
com.vibsync/vibsync
One shared brain for your AI coding agents: team memory, agent Q&A, tasks, and file claims.
Inkwell
Persistent memory for AI agents: Markdown entries, hybrid search, typed graph links
How to run each
com.vibsync/vibsync As a remote MCP server
claude mcp add --transport http vibsync https://mcp.vibsync.com/mcpInkwell As a local MCP server: Docker image
claude mcp add --transport stdio inkwell-memory -- docker run -i --rm -v "<YOUR_KNOWLEDGE_PATH>:/knowledge" docker.io/foreigndmitryi/inkwell-memory:0.14.0Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only com.vibsync/vibsync has a remote endpoint we check. How we check endpoints
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 com.vibsync/vibsync publish no settings it asks for, so we do not compare settings.
What it can do: com.vibsync/vibsync · What it can do: Inkwell · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.