Wuniq KE (Knowledge Engine) MCP server

Wuniq MCP

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 at wuniq.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 .wuniq files 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.

What this repository contains

This repository contains the small, open-source MCP launcher published as @wuniq/mcp, the manifest submitted to the official 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 and connect

1. Install the free Wuniq desktop app using an official download link from wuniq.com.
2. 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 the wuniq-mcp command 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 at wuniq.com.

OpenCode

OpenCode uses a project-level opencode.json file. Add Wuniq under its mcp key, 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's AGENTS.md without 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/mcp 1.0.1. MCP connection and the open, read, and sync calls worked correctly. Models vary in how reliably they act on AGENTS.md without prompting, so open list can always be requested explicitly.

See the full Wuniq + OpenCode integration guide for verification, Linux instructions, Precise mode, and troubleshooting.

Claude plugin

The repository root is also a Claude plugin. It does not contain a second MCP server: .mcp.json starts the published @wuniq/mcp launcher, which connects Claude to the MCP server inside the installed Wuniq app.

Shortened. The full README is on GitHub.