mex (Claude Skill) — Use Cases, Install & Live Demo

Why use it

Key features

Structured memory scaffold: architecture / conventions / in-flight / blockers
Drift CLI compares memory claims against actual code/tests
Per-section freshness markers (last verified date)
Designed for human + agent shared use; both read the same files
Plays nicely with CLAUDE.md / AGENTS.md

Live Demo

What it looks like in practice

ready

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "mex-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/theDakshJaitly/mex",
        "~/.claude/skills/mex"
      ],
      "_inferred": true
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "mex-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/theDakshJaitly/mex",
        "~/.claude/skills/mex"
      ],
      "_inferred": true
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "mex-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/theDakshJaitly/mex",
        "~/.claude/skills/mex"
      ],
      "_inferred": true
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "mex-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/theDakshJaitly/mex",
        "~/.claude/skills/mex"
      ],
      "_inferred": true
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "mex-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/theDakshJaitly/mex",
        "~/.claude/skills/mex"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json

{
  "context_servers": {
    "mex-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/theDakshJaitly/mex",
          "~/.claude/skills/mex"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add mex-skill -- git clone https://github.com/theDakshJaitly/mex ~/.claude/skills/mex

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use mex

Set up project memory at the start of a project

👤 New repo owners ⏱ ~25 min beginner

When to use: Day 1 of a project; you want agents to ramp fast.

Prerequisites

Skill installed — git clone https://github.com/theDakshJaitly/mex ~/.claude/skills/mex

Flow

Init

Use mex. Initialize project memory with sections: architecture, conventions, in-flight, blockers.✓ Copied

→ /.mex/ scaffold created with templates
Fill seeds

Auto-extract architecture from existing code and a starter convention list.✓ Copied

→ Sections seeded with starter content
Set freshness

Mark each section verified today.✓ Copied

→ Freshness markers set

Outcome: New project starts with shared agent context.

Pitfalls

Auto-extraction grabs irrelevant detail — Trim ruthlessly — memory is for principles, not grep

Combine with: filesystem

Find where the project memory disagrees with the code

👤 Long-running project owners ⏱ ~30 min intermediate

When to use: Memory was set up months ago; nobody's sure how stale.

Flow

Run drift

Use mex. Run drift detection. Report claims that no longer match reality.✓ Copied

→ Drift report with claim ↔ evidence
Update or remove

For each drift, decide: update memory or fix the code (claim was right and reality drifted).✓ Copied

→ Per-item decision; PRs opened for code-side fixes
Re-verify

After resolving, mark sections verified today.✓ Copied

→ Memory aligned again

Outcome: Memory remains a reliable contract, not folklore.

Pitfalls

Drift detector flags too aggressively — Tune --strictness; use 'medium' for living projects

Combine with: github

Hand off in-flight work between team members

👤 Devs going on vacation / leaving ⏱ ~20 min beginner

When to use: You have 3 features in progress and someone else needs to pick up.

Flow

Capture in-flight

Use mex. For each open branch, write an in-flight entry: goal, current state, next steps, gotchas.✓ Copied

→ Entries in /.mex/in-flight/
Verify with the CLI

Run drift on in-flight; ensure entries reflect actual branch state.✓ Copied

→ Drift clean
Hand off

Generate a teammate-ready summary linking each entry to its branch.✓ Copied

→ Slack/email-ready handoff

Outcome: Smooth pickup; no archaeology required.

Pitfalls

In-flight entries vague ('working on X') — Force the template's 'next steps' field; concrete or it doesn't help

Combinations

Pair with other MCPs for X10 leverage

mex-skill + filesystem

Memory lives in repo; commit it

Commit /.mex/ to git so memory travels with the codebase.✓ Copied

mex-skill + github

Drift CI check on PRs

On every PR, run mex drift and post the report as a PR comment.✓ Copied

Tools

What this MCP exposes

Tool	Inputs	When to call	Cost
init	scaffold_options	Once per project	0
drift	section?, strictness?	Weekly / before merging long-running branches	0 (uses local checks + LLM for fuzzy claims)
verify	section	After updating memory to match reality	0
in_flight_add	branch, goal, next_steps	When starting a feature branch	0
summary	format	Handoff / status report	0

Cost & Limits

What this costs to run

API quota: None — local
Tokens per call: Drift uses LLM for fuzzy claims; capped per run
Monetary: Free
Tip: Use strict=high in CI to catch real drift; medium for daily local checks

Security

Permissions, secrets, blast radius

Minimum scopes: filesystem-write

Credential storage: None

Data egress: None unless drift LLM is configured to remote provider

Memory contains architecture details — gitignore /.mex/ if repo is private and you mirror to public forks

Troubleshooting

Common errors and fixes

Drift reports false positives

Lower strictness; or refine claim phrasing to be more checkable

Memory grows unbounded

Each section has a soft cap; consolidate periodically — keep principles, archive specifics

CLI can't find /.mex/

Run from repo root; or pass --root <path>

Auto-extraction misses key invariants

Auto-extract is a starter; hand-write the load-bearing invariants

Alternatives

mex vs others

Alternative	When to use it instead	Tradeoff
claude-mem-skill	You want session continuity, not project-knowledge memory	Different problem; mex is for project-level invariants
Plain CLAUDE.md	Tiny project, no drift detection needed	No structure; no automated freshness checks
pilot-shell-skill	You want spec/plan/gates plus knowledge persistence	Bigger workflow surface; more opinions

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills