Atlas / MCP servers / richlira / Compass

CompassSAFE

mcp/richlira/compass-1
Verdict
SAFE
Grade
B
Trust score
89 /100
Exposed tools
6 4r · 2w · 0d
Transport
stdio
License
—
Stars
34
01

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

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:

Read from source at commit ab05857c74dcOBSERVED · 2026-10-08
Advertisement
02

Connect

Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.

claude-code
claude mcp add compass-mcp --env COMPASS_DATA_DIR=${COMPASS_DATA_DIR} -- npx -y [email protected]
claude-desktop
{
  "mcpServers": {
    "compass-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ],
      "env": {
        "COMPASS_DATA_DIR": "${COMPASS_DATA_DIR}"
      }
    }
  }
}
03

Exposed tools (6)

4 read · 2 write · 0 destructive.

ToolRiskDescription
add_taskwriteAdd a new task to your task list.
complete_taskreadMark a task as complete.
get_contextreadRead a project context file. Use when user references a project —
get_tasksreadGet tasks filtered by status, tags, or deadline.
init_workspacereadInitialize the Compass workspace. Creates ~/compass-data/ with tasks.md and contexts/. Safe to run multiple times — won
save_contextwriteSave or update a project context file. Use when user says
04

Trust audit

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codePASS
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
none-observed
Network
none-observed
Shell
none-observed
Dependencies
not all pinned
Secrets in source
none-found

Findings (2)

LOWInventory / provenance · inv.no_license · CWE-1104
Why it matters. no LICENSE file and no repo licence
Fix. add a licence
LOWSupply chain · supply.unpinned · CWE-829, CWE-1357
package.json
zod
Why it matters. 1 dependency range(s) float
Fix. pin exact versions or ship a lockfile

Gates applied: no_behavioural_pass, no_license.

Audited 2026-10-08 · audit v0.4.1 · source sha ab05857c74dcfull audit observations/trust-audit/mcp-server/richlira__compass-1.json · Report an issue / request a re-scan
05

Audit history

Every audit this server has had. A grade with a past is a grade somebody is still checking.

DateSourceVerdictGradeScoreChange
2026-10-08ab05857c74dcSAFEB89first audit
06

Questions

What tools does Compass expose?

6 in total: 4 read-only, 2 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.

Is Compass safe to connect to an agent?

The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.

What credentials does Compass need?

It reads COMPASS_DATA_DIR from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.

How does Compass run?

It speaks stdio, so it runs as a local process your client starts. It is published on npm as compass-mcp at 1.0.0.

How current is this page?

The grade is for one exact copy of the source (ab05857c74dc), read on 2026-10-08. The repository is watched and re-audited when it changes.

Advertisement