Wuniq
About
Local-first structured project memory for AI coding agents. Requires the free Wuniq desktop app.
Details
- Author
- wuniq
- Categories
- AI
Jump to
Setup
Install Wuniq in your MCP client (Claude Desktop, Cursor, Windsurf, and others).
Repository: https://github.com/wuniq/wuniq-mcp
Follow the installation instructions in the repository README, then restart your MCP client.
Wuniq is free. This MCP package requires the Wuniq desktop app, currently available for Windows and Linux. Download it only through the official, trusted links atwuniq.com. Do not use third-party mirrors.
Wuniq is a knowledge engine for AI-assisted work. It stores decisions, constraints, intent, and human reasoning in.wuniqfiles beside your project files, so any MCP-compatible AI can read and maintain the knowledge exactly where the work lives.
Wuniq is local-first: no account, no cloud storage, and no telemetry.
This repository contains the small, open-source MCP launcher published as@wuniq/mcp, the manifest submitted to theofficial MCP Registry, and thin wrappers for Claude, Codex, Antigravity, and Gemini CLI that all start the same launcher.
The launcher has zero dependencies. It connects your MCP client to the MCP server included with the installed Wuniq desktop app:
MCP-compatible AI or IDE | v npx @wuniq/mcp | v Installed Wuniq desktop app | v Local projects and .wuniq knowledge
The Wuniq Knowledge Engine itself is not contained in this repository and is not distributed through npm. The MIT license in this repository applies only to the launcher.
- Install the free Wuniq desktop app using an official download link fromwuniq.com.
- Add Wuniq from your IDE's MCP registry gallery, where supported, or configure it manually:
{ "mcpServers": { "wuniq": { "command": "npx", "args": ["-y", "@wuniq/mcp"] } } }
Already have the app installed? You can also point your MCP configuration directly to thewuniq-mcpcommand placed on your PATH by the official Wuniq installation. Both methods connect to the same local engine.
Per-IDE instructions and current platform availability are maintained atwuniq.com.
OpenCode uses a project-levelopencode.jsonfile. Add Wuniq under itsmcpkey, keeping any providers, permissions, or other MCP servers already present:
{ "$schema": "https://opencode.ai/config.json", "mcp": { "wuniq": { "type": "local", "command": ["npx", "-y", "@wuniq/mcp"], "enabled": true, "timeout": 30000 } } }
Then add the Wuniq workflow to the project'sAGENTS.mdwithout removing any existing instructions:
# Wuniq KE (Knowledge Engine) At the start of every session, run open list using the Wuniq MCP tool. If it returns projects, open each one. If the list is empty, proceed normally — the user may open projects later from the Wuniq UI. Never assume the working directory is a Wuniq project; the working directory may be a container folder holding multiple projects. Only open paths that open list explicitly returns. Before working on any code file, read its Wuniq sidecar for context. After changing code, run sync.
This route was validated on Windows with OpenCode Desktop 1.18.4, Wuniq 1.15.1, and@wuniq/mcp1.0.1. MCP connection and theopen,read, andsynccalls worked correctly. Models vary in how reliably they act onAGENTS.mdwithout prompting, soopen listcan always be requested explicitly.
See the fullWuniq + OpenCode integration guidefor verification, Linux instructions, Precise mode, and troubleshooting.
The repository root is also a Claude plugin. It does not contain a second MCP server:.mcp.jsonstarts the published@wuniq/mcplauncher, which connects Claude to the MCP server inside the installed Wuniq app.
The plugin includes one compact skill that teaches Claude the safe Wuniq workflow: discover visible projects first, read their context before working, preserve confirmed decisions, and synchronize after changes. It does not pre-approve tools or elevate permissions.
Before marketplace submission, the plugin can be checked and loaded locally with Claude Code:
claude plugin validate --strict . claude --plugin-dir .
The same repository is also a Codex plugin. Its.codex-plugin/plugin.jsonreuses the same skill and.mcp.json; it starts@wuniq/mcplocally and does not create a hosted service or upload project data.
Add the public Wuniq marketplace from Codex:
codex plugin marketplace add Wuniq/wuniq-mcp --ref main
Then open thePluginsdirectory in the ChatGPT desktop app, select theWuniqmarketplace, and installWuniq. Start a new Codex session after installation so the skill and MCP server are loaded.
ChatGPT on the web cannot run this localstdioMCP server. Wuniq's full integration is therefore for local Codex clients: the ChatGPT desktop app, Codex CLI, and the Codex IDE extension.
The repository root is a native Antigravity plugin. Itsmcp_config.jsonstarts the published@wuniq/mcplauncher, whileskills/wuniq/SKILL.mdsupplies the safe Wuniq workflow. It does not contain a second MCP server or upload project data.
Install it in Antigravity CLI from the public repository:
agy plugin install https://github.com/Wuniq/wuniq-mcp
In Antigravity 2.0, Wuniq can also be configured as a custom MCP server with the samenpx -y @wuniq/mcpcommand while its MCP Store listing is under review.
The repository root is also a Gemini CLI extension. Itsgemini-extension.jsonstarts the same published@wuniq/mcplauncher, whileskills/wuniq/SKILL.mdsupplies the safe Wuniq workflow as an Agent Skill. It does not contain a second MCP server or upload project data.
Install it directly from the public repository:
gemini extensions install https://github.com/Wuniq/wuniq-mcp
Restart Gemini CLI after installation so the extension and its MCP tools are loaded.
Google has transitioned personal, Pro, and Ultra users from Gemini CLI to Antigravity CLI. The Gemini CLI extension remains available for supported Enterprise, Google Cloud, and API-based environments.
- "Open the Wuniq projects visible to you and summarize the important context for this task."
- "Before changing the authentication module, read its Wuniq context and preserve the constraints already decided."
- "Record the decision we just made, implement the change, and run Wuniq sync when you finish."
- The Wuniq app is missing:install it only from the official links atwuniq.com, then start a new Claude, Codex, Antigravity, or Gemini CLI session.
- open listreturns no projects:open the intended project in the Wuniq desktop interface and ask your AI client to try again.
- The launcher cannot start:confirm that Node.js andnpxare available, or use the direct per-client setup documented atwuniq.com.
The launcher passes the MCP client's standard input and output directly to the MCP server included with the installed app. If Wuniq is not installed, it exposes only a minimal MCP response explaining how to obtain the official app.
It does not configure IDEs, contain Wuniq product logic, upload project data, or provide a second Knowledge Engine.
Only install Wuniq through links published onwuniq.com. Do not use third-party mirrors or repackaged installers.
To report a security issue, use this repository's private vulnerability reporting instead of opening a public issue. SeeSECURITY.md.
- Wuniq website and official downloads
- Official MCP Registry entry
- @wuniq/mcpon npm
The MCP launcher and the Claude, Codex, Antigravity, and Gemini CLI wrappers in this repository are licensed under theMIT License. The Wuniq desktop app and Knowledge Engine are separate software and are not covered by this repository's license.
Local-first agent memory: a plain-Markdown Obsidian vault is the source of truth, with a rebuildable DuckDB index for hybrid BM25 + vector + graph recall.
Persistent memory and semantic search for AI coding assistants across sessions
Give your agent a memory: shared, cited, tenant-isolated knowledge-graph memory for any MCP host. Grounded answers from a local-first June endpoint — abstains rather than guesses.
Decentralized persistent memory for AI agents — encrypted vault storage built on Walrus and Sui.
Persistent memory for AI assistants and coding agents across ChatGPT, Claude, Cursor, and other MCP-compatible tools.
Your portable AI memory vault — memories, skills & configs, shared across every AI tool.
Local Work Model for AI agents that learns from real outcomes.
Adaptive MCP memory system for AI applications. Learns which retrieval strategies work for your data, scores results using cognitive science models, builds a knowledge graph automatically, and validates every parameter change against real query history before adopting it. Patent pending.
Auditable, self-improving knowledge & memory for AI agents over MCP — citation-enforced answers and a replayable why-trace, self-hosted on Postgres.
Turns your task manager into agent memory: hybrid (RRF) retrieval over TickTick or an Obsidian vault via an adapter contract. MCP server + CLI, no vector DB to maintain.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
