MCP Hooks

The Vibeless desktop app bundles a local MCP server (vibeless-mcp-server). Once the app is running and a project is open, any MCP-aware AI editor can connect to it. There is no npm package or separate process to start — the app manages the server lifecycle.

How the server works

The MCP server runs as a sidecar binary inside the desktop app. It exposes the full set of Vibeless tools (listed in the MCP Tool Reference) to any connected editor. The server uses stdio transport, which means each editor spawns it as a child process rather than connecting over a network socket.

The server selects a response format based on which editor it detects. You can override this by passing --adapter <id> where <id> is one of: cursor, claude-code, codex, gemini, generic-mcp.

Supported editors

Claude Code

Add to claude_desktop_config.json (usually at ~/.claude/claude_desktop_config.json):

{
  "mcpServers": {
    "vibeless": {
      "command": "vibeless-mcp-server",
      "args": []
    }
  }
}

Restart Claude Code after saving the file.

Cursor

1. Open Settings (Cursor menu > Settings, or Ctrl+Shift+J).
2. Select the MCP tab.
3. Click Add new global MCP server.
4. Enter the path to vibeless-mcp-server (check the Vibeless app Settings panel for the exact path).

The resulting ~/.cursor/mcp.json entry looks like:

{
  "mcpServers": {
    "vibeless": {
      "command": "/path/to/vibeless-mcp-server",
      "args": []
    }
  }
}

Other MCP-aware editors

Any editor that supports the Model Context Protocol (stdio transport) works with the same shape:

{
  "command": "/path/to/vibeless-mcp-server",
  "args": []
}

Check your editor's documentation for where to place the server config.

Finding the binary path

The install path for vibeless-mcp-server varies by platform:

• Windows — %LOCALAPPDATA%\Vibeless\binaries\vibeless-mcp-server.exe
• macOS — /Applications/Vibeless.app/Contents/MacOS/binaries/vibeless-mcp-server

The Vibeless app's Settings panel shows the exact path for your installation.

Verifying the connection

After wiring your editor, ask your agent:

Call vibeless_get_project_context and tell me what project I have open.

If the response describes your active Vibeless project, the server is connected and the tools are available.

Available tools

The full input and output schema for every tool is in the MCP Tool Reference. A quick overview:

| Tool | Purpose | |------|---------| | vibeless_get_project_context | Project info, active phase, constraints, hooks | | vibeless_get_phase_spec | Phase spec and tasks | | vibeless_get_task_spec | Single task with merged constraints | | vibeless_run_drift_check | Deterministic drift report (no LLM) | | vibeless_check_constraint | Constraint and prior-decision lookup | | vibeless_log_decision | Persist an agent decision | | vibeless_declare_intent | Scope-aware context loading | | vibeless_propose_phase_boundary | LLM-backed phase boundary proposal | | vibeless_structured_handoff_digest | LLM-backed project handoff summary | | vibeless_topology_summary | Code graph node/edge counts | | vibeless_topology_query | Filter graph nodes and edges |