Claude Project Coordinator

Your local project desk for Claude. Track Xcode and Swift work across many repos, then ask Claude what is hot, stale, or next.

CPC is an MCP server that gives Claude a structured, on-disk view of your projects: status, notes, tech stack, activity, and health. It runs on macOS beside Claude Desktop, Cursor, or Claude Code. Data never leaves your machine.

v1.4.1 · official Swift MCP SDK · MIT · local JSON knowledge base

Who is this for?

Pick the path that matches you. Same binary, different first questions.

1. Multi-project Swift hobbyist

You have several apps and packages. Context switches burn time, and you forget which repo was mid-refactor.

Start with:

• "Add my WeatherApp at ~/Developer/WeatherApp"
• "Show me all my tracked projects"
• "Which projects need my attention?"
• "Update WeatherApp status to 'Core Data models half done'"

What you get: a living roster with status, notes, auto-detected tech (SwiftUI, SPM, Xcode project/workspace), and a health score so quiet projects surface again.

2. Claude Desktop daily driver

Claude is your coding desk. You want continuity between chats without pasting the same project list.

Start with:

• "List my projects and their current status"
• "What's going on with TodoApp?"
• "Find all SwiftUI patterns we've stored"
• "Show my project activity this week"

What you get: Claude can call nine MCP tools against your KnowledgeBase instead of guessing from conversation memory.

3. Cursor or Claude Code agent user

Agents write code well but lose the portfolio view. You want the agent to know which project it is in and whether that project is healthy.

Start with:

• Wire CPC into Cursor / Claude Code MCP settings (see Installation)
• "Get project status for Claude-Project-Coordinator"
• "Get technology trends across my tracked projects"
• "Show a 14-day activity heat map"

What you get: project health and timelines as tool results the agent can act on, next to the files it already sees.

4. Privacy-first / local-only setup

You will not send a project inventory to a cloud PM tool. Everything should live beside the binary.

Start with:

• Build from source, point MCP at .build/release/project-coordinator
• Optional: CPC_KNOWLEDGE_BASE=~/Library/Application Support/CPC for data outside the git tree
• Keep KnowledgeBase/projects/*.json out of public repos (already gitignored)

What you get: JSON on disk, path allowlisting, no account, no telemetry.

5. Already using a memory MCP

You store decisions and people in Memory Service (or similar). You do not want a second conversation dump.

How they fit together:

Use both. Do not replace one with the other.

Full feature list

Project desk