Doriku

Doriku is a shared control plane for AI coding agents — Claude Code, Cursor, Windsurf, and human teammates sync tasks, memory, decisions, and file locks…

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

  • Doriku Task: Tasks: lifecycle, coordination, recovery. create with objective+done_criteria and log with progress_summary+next_step are quality-scored; resume returns a full resume pack.
  • Doriku Agent: Agent presence and coordination. heartbeat responses include pending_commands[] (console-issued interrupt/inject_task) — act on them when present.
  • Doriku Memory: Persistent memory shared across sessions, projects, and AI tools. relate/neighbors manage the memory graph; glossary_*/preference_* tune search scoring.

What data it sees

Do you need an account

No: the server works without sign-in

Doriku is a shared control plane for AI coding agents — Claude Code, Cursor, Windsurf, and human teammates sync tasks, memory, decisions, and file locks through one MCP server.\n\n12 consolidated tools (~15KB tools/list) covering:\n\n- Tasks & coordination — atomic claim/release, dependencies, resume packs that restore full context across sessions and tools\n- Persistent memory — workspace-scoped knowledge with lexical + semantic search\n- Governance — file lock policies, cost caps, approval workflows, audit trail\n- Automations & workflows — schedules, status triggers, Slack/Discord notifications\n- Team visibility — live console dashboard, agent presence, handoff summaries\n\nMulti-agent safe by design: two agents can work the same repo without stepping on each other.\n\nGet started: sign up at https://doriku.io (free tier: 2 agents, 100 tasks/mo), then npx @doriku/cli setup. Auth: Bearer API key from the console.

How to connect

How to connect Doriku to Claude

The server address to paste into Claude settings:

https://doriku--doriku.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect Doriku to ChatGPT

The server address to paste into ChatGPT settings:

https://doriku--doriku.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect Doriku to Cursor

The server address to paste into Cursor settings:

https://doriku--doriku.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (12)

Raw names from tools/list. Only developers need these.

doriku_taskTasks: lifecycle, coordination, recovery. create with objective+done_criteria and log with progress_summary+next_step are quality-scored; resume returns a full resume pack.
doriku_agentAgent presence and coordination. heartbeat responses include pending_commands[] (console-issued interrupt/inject_task) — act on them when present.
doriku_memoryPersistent memory shared across sessions, projects, and AI tools. relate/neighbors manage the memory graph; glossary_*/preference_* tune search scoring.
doriku_contextKey-value working context (workspace/project/agent scoped). set with source+scope records provenance.
doriku_decisionDecision records. record with problem+chosen_option+alternatives+rationale is quality-scored.
doriku_projectProjects group related tasks. summarize generates a progress summary; summary returns the latest.
doriku_workspaceWorkspaces and state sync: snapshot at session start, then poll changes with the returned sequence number.
doriku_workflowMulti-step workflows across agents. step_* verbs manage step run lifecycle for executing agents.
doriku_automationAutomation rules (triggers: task_status_change|task_created|schedule|manual) and the Smart Dispatcher (Pro).
doriku_governanceMulti-agent guardrails: file locks, lock policies, token cost caps, audit trail.
doriku_searchGlobal search across tasks, projects, and agents. Top 5 per category by relevance.
doriku_sessionSession flow: structured handoffs, next actions, token usage reporting, plan capabilities.