What is the key difference between Vibsync and Doriku?

Vibsync belongs to the Knowledge & Memory category with local stdio execution, while Doriku belongs to the Knowledge & Memory category with local stdio execution.

How do I install Vibsync or Doriku in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Vibsync and Doriku free or paid?

Vibsync operates under a Free / Open Source model (No auth required). Doriku operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Vibsync lists 0 tools with 0 views and 0 GitHub stars. Doriku lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Vibsync and Doriku together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

How do I install Vibsync or Doriku in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are Vibsync and Doriku free to use, or do they require API keys?

Vibsync is listed under a Free / Open Source model with No auth required . Doriku operates under a Free / Open Source model with No auth required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both Vibsync and Doriku at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both vibsync-3 and doriku-2 as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Vibsync has a Quality Score of 27 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars. Doriku holds a Quality Score of 27 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Vibsync vs Doriku

In-depth architectural comparison of the Vibsync and Doriku MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Vibsync

Knowledge & Memory · Local stdio

Quality: 27/100 (Emerging) | Auth: No auth required

Doriku

Knowledge & Memory · Local stdio

Quality: 27/100 (Emerging) | Auth: No auth required

Verdict Summary: Choose Vibsync if you need specialized Knowledge & Memory tools running via a local process. Choose Doriku if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Vibsync when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Vibsync Details

Choose Doriku when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Doriku Details

Feature & Specification Comparison

Specification	V Vibsync Knowledge & Memory	D Doriku Knowledge & Memory
Summary	One shared brain for your AI coding agents: team memory, agent Q&A, tasks, and file claims.	Shared control plane for AI coding agents — tasks, memory, decisions, file locks. 12 tools.
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

Tools & Capabilities Breakdown

Vibsync Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Doriku Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Vibsync Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "vibsync-3": {
      "command": "npx",
      "args": [
        "-y",
        "vibsync-3"
      ]
    }
  }
}

Doriku Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "doriku-2": {
      "command": "npx",
      "args": [
        "-y",
        "doriku-2"
      ]
    }
  }
}

Frequently Asked Questions

Vibsync is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Doriku belongs to Knowledge & Memory using local stdio subprocess. Select Vibsync when you need capabilities focused on knowledge & memory and Doriku when you require tools for knowledge & memory.

More alternatives to Vibsync More alternatives to Doriku Knowledge & Memory category hub Canonical compare URL

Related MCP Server Comparisons

Popular comparisons with Vibsync

Popular comparisons with Doriku

Doriku vs Moxie Docs MCP