Claude Desktop Setup

Connecting a Direktor node to Claude Desktop is a three-step process: generate a per-node token, add an entry to ~/.claude.json, reload Claude Desktop.

Prerequisites

Claude Desktop installed and signed in.
Node.js (for the mcp-remote bridge — Claude Desktop auto-invokes it via npx).
A Direktor workspace with at least one node placed.

Step 1 — Generate a token from the node card

Open direktor.tech and go to the workspace containing the node you want to connect.
Hover (or tap) the node’s card on the canvas.
Click ⋯ → Connect to Claude Desktop.
Confirm the prompt. A modal appears with a one-time token and a copy-ready JSON snippet.

The token begins with of_dkmcp_ and is shown once. If you lose it, click Disconnect and re-mint.

Step 2 — Add the MCP server to `~/.claude.json`

Copy the JSON snippet from the modal and paste it into the mcpServers block of your ~/.claude.json (macOS and Linux; %APPDATA%\claude-desktop\claude_desktop_config.json on Windows).

The snippet looks like this (with your actual values):


{
  "mcpServers": {
    "direktor-cmo": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://direktor-mcp.openfactory.tech/mcp-stream/mcp",
        "--header",
        "Authorization: Bearer of_dkmcp_your_key_here"
      ]
    }
  }
}

If you already have other mcpServers entries (like openfactory for the OpenFactory MCP), just add direktor-cmo alongside — don’t replace them.

Self-hosted backends

If you’re running your own Direktor backend, point at your host instead:


"args": [
  "mcp-remote",
  "http://localhost:8011/mcp-stream/mcp",
  "--header",
  "Authorization: Bearer of_dkmcp_your_key_here"
]

Naming convention

Use direktor-<role> as the mcpServers key so you can distinguish nodes:

direktor-cmo, direktor-cto, direktor-sales-vp.

Claude Desktop displays these keys in its tool picker — clear names help you pick the right node when you have multiple connected.

Step 3 — Reload Claude Desktop

Fully quit and restart Claude Desktop. On next launch:

Open a new chat.
In the tools panel (bottom-right), look for direktor-cmo (or whatever key you chose). It should list four tools: do, list_skills, get_activity, list_peers.
Try list_peers as a first check — it returns the other roles in your workspace and confirms auth works.

Connecting multiple nodes

Repeat steps 1–2 for each node you want accessible. Each gets its own of_dkmcp_ token and its own entry in mcpServers. Your CMO, CTO, and Sales VP can all appear as independent tool namespaces.

Troubleshooting

`tools/list` returns nothing

You restarted Claude Desktop but the connection is stuck. Check:

Your token is pasted correctly and hasn’t been revoked.
The URL matches the modal (prod vs localhost).
npx mcp-remote --help works from your terminal (Node.js is installed).

401 Unauthorized

The token was revoked or never valid. Go back to the node card → Disconnect → re-mint.

Tool calls hang

The agent container might be cold-starting. Give it 15–30 seconds for the first tool call after a quiet period. If it’s still hung after a minute, the agent might be waiting on a human decision — check the node’s activity timeline in direktor.tech.

Scope error: “node not found”

You’re hitting a node that no longer exists (deleted from the chart). Re-mint the token from a current node.

Revoking access

To revoke a token:

Direktor.tech → Workspace → Node card → ⋯ → Disconnect Claude Desktop.
Remove the matching entry from ~/.claude.json so Claude Desktop stops trying the dead endpoint.

Revocation is immediate. Any subsequent tool call from a revoked token returns 401.

Tools Reference — schema + examples for all four tools.
Example Flows — realistic user stories.