TrackerHelp

Claude Code + MCP

Drive Tracker from any Claude Code session — log requirements, gaps, evidence, and tasks without leaving the IDE.

Hosted MCP (recommended)

Tracker speaks MCP directly over HTTPS. No local clone, no node_modules, no .env — Claude Code talks straight to the SaaS endpoint.

1. Mint a personal token

Sign in and go to Settings → API tokens. Click Create token, give it a friendly name (e.g. laptop mcp), and copy the trk_… string. It's shown once — paste it somewhere safe.

2. Register the MCP once

Run the command below in a terminal:

claude mcp add tracker --transport http \
  https://app.tracker.trythis.digital/mcp \
  --header "Authorization: Bearer trk_..."

Verify with claude mcp list. You should see tracker ✓ Connected.

3. (Optional) Pin a specific project

With one project, no pin needed — the API picks it. With several, add an X-Project-Id header so the session stays on one of them. The header accepts either the friendly org-slug/project-slug reference (visible on the project Settings page) or the cuid:

claude mcp add tracker --transport http \
  https://app.tracker.trythis.digital/mcp \
  --header "Authorization: Bearer trk_..." \
  --header "X-Project-Id: acme-ai/customer-support-assistant"

The list_projects tool returns each project's ref field if you'd rather discover it from a Claude Code session.

4. Use it from any project

Open a Claude Code session in any repo and try:

  • “list my tracker projects”
  • “list open gaps for project X”
  • “log a gap for SEC-5.3 with severity high saying we don't rate-limit prompt-injection tests yet”
  • “mark AI-1.2 as met and attach this PR URL as evidence”
  • “create a task to wire up prompt-injection defences, priority critical”
  • “import the EU AI Act framework pack into my project”

What the MCP can do

The MCP exposes these tools and resources out of the box:

  • Context resources (auto-listed; Claude Code reads them at session start): tracker://project/active-requirements, tracker://project/open-gaps, tracker://project/path-map. Mirror tools get_active_requirements, get_open_gaps, get_path_map for clients without resource auto-read.
  • Pre-edit consult: check_change — given the paths you're about to touch, returns affected requirements, warnings (status / open critical gap), and per-requirement suggested evidence.
  • Diff-shaped lookup: suggest_requirements_for_files — given the file paths in a diff, returns requirements ranked by overlap with their existing evidence. Use post-edit / on-PR.
  • Reads: list_projects, list_frameworks, list_requirements, list_gaps, list_tasks, get_requirement.
  • Mutations: create_requirement / update_requirement, create_gap / update_gap, create_task / update_task, add_evidence.
  • Bulk mutations: bulk_update_requirements, bulk_update_gaps, bulk_create_tasks — one round-trip for N items, with best-effort or transactional semantics.
  • Framework adoption: list_framework_packs, import_framework_pack.

Drop in the consult skill

For sessions where the model is editing code rather than chatting, copy docs/claude/skills/tracker-consult.md from the Tracker repo into your consuming project's .claude/skills/. It teaches the consult-before-edit ritual: read the three resources at session start, call check_change before any non-trivial edit, act on the warnings, log evidence after the change ships.

Self-host / advanced: stdio MCP

For self-host operators (or anyone running Tracker on a network Claude Code can't reach over HTTPS), the MCP also ships as a local stdio process. You'll need a clone of the Tracker repo + Node 22+.

Edit .env in your local clone:

TRACKER_API_URL="https://your-tracker-host.example.com"
TRACKER_API_TOKEN="trk_..."
# Optional — pin a specific project rather than "most recent". Either
# the org-slug/project-slug ref or the project's cuid works:
TRACKER_PROJECT_ID="acme-ai/customer-support-assistant"

Then register the local proxy:

claude mcp add tracker -s user -- \
  bash -c 'cd /path/to/tracker && npm run mcp:server'

Same tool catalogue and resources as the hosted variant — they share the same code (src/lib/mcp/build-server.ts) and only differ in transport.

Troubleshooting

  • 401 Unauthorized — the token is wrong, revoked, or you forgot the Authorization: header. Re-mint, re-register.
  • No project visible — the API picks the user's most recently updated project by default. Add an X-Project-Id header to be explicit.
  • Tools don't show up — claude mcp list should show tracker ✓ Connected. If not, re-run the claude mcp add command.
  • TLS warning in browser when checking the URL — the SaaS currently uses Let's Encrypt staging certs. Browser-trust kicks in once the issuer flips to prod (Phase 1 launch). Doesn't affect Claude Code.