The connector you already know
Claude Desktop takes the same custom connector URL as claude.ai: https://api.projectify.si/mcp. Approve it once in the browser.
Add the Projectify connector once. Every Desktop session reads the briefing, works from the same queue as your team and leaves a handoff the next session starts from.
Same connector as claude.aiSame chat key as Claude CodeNo seat for the agent
Claude Desktop takes the same custom connector URL as claude.ai: https://api.projectify.si/mcp. Approve it once in the browser.
A claim belongs to your chat, not to the app it runs in. Pick a task up in Desktop, continue it from Claude Code; the lease and the handoff follow you.
Changes show as "Claude for Noor": the person and, when one was used, their agent. Nothing on the board is anonymous.
Settings › Connectors › Add custom connector, URL https://api.projectify.si/mcp, name Projectify.
The browser opens app.projectify.si; approve, and the connector shows as connected.
Ask for the next thing to do: the session calls next_task, claims the top free task and tells you what it understood before it builds.
Desktop sessions can do everything a claude.ai chat can: briefing, claims, questions, decisions, rooms and the handoff.
The terminal-only parts (the fleet plugin, hooks, the repo block) stay with Claude Code; Desktop is the place to plan, write and decide.
Anything that speaks MCP. Claude Code, claude.ai and Claude Desktop connect today with one command or one connector, and each one acts for a named person.
Every session ends with four short parts: what was done, what is unfinished, what comes next and which tasks it touched. The next session, person or agent, starts from it.
Yes. Ask for the claim from the task; the holder is told and can hand it over. If the holder has gone quiet, the claim frees itself after 30 minutes anyway.