richlira/compass-mcp

Эта страница переведена автоматически. Технические детали смотрите в оригинале. Открыть оригинал

34 stars 7 forks Качество 62 Тренд 12

Compass is an MCP server that gives Claude shared operational state across all three surfaces. Add a task in Chat, check it off in Code, filter by project in Cowork — same data, zero re-explaining.

Обзор

Compass is an MCP server that gives Claude shared operational state across all three surfaces. Add a task in Chat, check it off in Code, filter by project in Cowork — same data, zero re-explaining. Claude Chat, Cowork, and Code don't share state. Each session starts from zero. There's no way to ask in Chat "what did I finish in Code?" or tell Cowork "here's the context for this project" without re-explaining everything. Compass fixes that. One MCP server, visible to all three surfaces, backed by plain markdown files. It's the operational layer that connects how you think (Chat), how you execute (Cowork), and how you build (Code). Add to ~/Library/Application Support/Claude/claude_desktop_config.json: Restart Claude Desktop. All three tabs (Chat, Cowork, Code) will see Compass. Works in English, Spanish, Spanglish — whatever. Claude matches your intent to the right tool automatically. Creates ~/compass-data/ with tasks.md and contexts/ directory. Safe to run multiple times.

README

Показан фрагмент оригинального README. Открыть оригинал.

🧭 Compass MCP

The missing bridge between Claude Chat, Cowork, and Code.

Compass is an MCP server that gives Claude shared operational state across all three surfaces. Add a task in Chat, check it off in Code, filter by project in Cowork — same data, zero re-explaining.

┌───────────┐    ┌───────────┐    ┌───────────┐
│   Chat    │    │  Cowork   │    │   Code    │
└─────┬─────┘    └─────┬─────┘    └─────┬─────┘
      │                │                │
      └────────┬───────┴────────┬───────┘
               │                │
       ┌───────▼────────────────▼───────┐
       │         Compass MCP            │
       │                                │
       │   ┌──────────────────────┐     │
       │   │  ~/compass-data/     │     │
       │   │  tasks.md            │     │
       │   │  contexts/           │     │
       │   └──────────────────────┘     │
       └────────────────────────────────┘

Why?

Claude Chat, Cowork, and Code don’t share state. Each session starts from zero. There’s no way to ask in Chat “what did I finish in Code?” or tell Cowork “here’s the context for this project” without re-explaining everything.

Compass fixes that. One MCP server, visible to all three surfaces, backed by plain markdown files.

This is not another todo app. It’s the operational layer that connects how you think (Chat), how you execute (Cowork), and how you build (Code).

Install

git clone https://github.com/richlira/compass-mcp.git
cd compass-mcp
npm install
npm run build

Connect to Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "compass": {
      "command": "node",
      "args": ["/absolute/path/to/compass-mcp/build/index.js"]
    }
  }
}

Restart Claude Desktop. All three tabs (Chat, Cowork, Code) will see Compass.

Usage

No commands to memorize. Just talk:

You say	Compass does
“Set up my workspace”	`init_workspace` → creates `~/compass-data/`
“Add task: write copy for landing page, deadline April 5”	`add_task` → adds to `tasks.md`
“I finished the workshop slides”	`complete_task` → marks it done
“What’s still pending?”	`get_tasks` → returns filtered tasks
“Save context for Impact Lab: April 18, hackathon format”	`save_context` → creates `contexts/impact-lab.md`
“What do we know about the workshop?”	`get_context` → reads `contexts/workshop.md`

Works in English, Spanish, Spanglish — whatever. Claude matches your intent to the right tool automatically.

Tools

`init_workspace`

Creates ~/compass-data/ with tasks.md and contexts/ directory. Safe to run multiple times.

`add_task`

Adds a task to tasks.md.

title (required) — what needs to be done
tags — project or category tags (e.g. ["cancun", "marketing"])
deadline — due date
section — "active" (default) or "backlog"

Открыть полный README на GitHub

Установка

npx @modelcontextprotocol/inspector node build/index.js

Новичок в MCP? Начните с руководства на mcpskill.org →

Конфигурация

{
  "mcpServers": {
    "compass": {
      "command": "node",
      "args": ["/absolute/path/to/compass-mcp/build/index.js"]
    }
  }
}