drift MCP — Casos de uso, Instalar & Demo ao vivo

Por que usar

Principais recursos

Pattern detection: auto-infers conventions from your actual code
Decision memory: write-once notes that persist across sessions
Multi-language: TypeScript, Rust, Java, Python, C#, PHP
MCP + offline CLI — same engine, two interfaces
Local-first: all data stored on your disk, nothing uploaded

Demo ao vivo

Como fica na prática

drift.replay ▶ pronto

0/0

Instalar

Escolha seu cliente

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

{
  "mcpServers": {
    "drift": {
      "command": "uvx",
      "args": [
        "drift"
      ],
      "_inferred": true
    }
  }
}

Abra Claude Desktop → Settings → Developer → Edit Config. Reinicie após salvar.

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

{
  "mcpServers": {
    "drift": {
      "command": "uvx",
      "args": [
        "drift"
      ],
      "_inferred": true
    }
  }
}

Cursor usa o mesmo esquema mcpServers que o Claude Desktop. Config de projeto vence a global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "drift": {
      "command": "uvx",
      "args": [
        "drift"
      ],
      "_inferred": true
    }
  }
}

Clique no ícone MCP Servers na barra lateral do Cline, depois "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "drift": {
      "command": "uvx",
      "args": [
        "drift"
      ],
      "_inferred": true
    }
  }
}

Mesmo formato do Claude Desktop. Reinicie o Windsurf para aplicar.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "drift",
      "command": "uvx",
      "args": [
        "drift"
      ]
    }
  ]
}

O Continue usa um array de objetos de servidor em vez de um map.

~/.config/zed/settings.json

{
  "context_servers": {
    "drift": {
      "command": {
        "path": "uvx",
        "args": [
          "drift"
        ]
      }
    }
  }
}

Adicione em context_servers. Zed recarrega automaticamente ao salvar.

claude mcp add drift -- uvx drift

Uma linha só. Verifique com claude mcp list. Remova com claude mcp remove.

Casos de uso

Usos do mundo real: drift

Onboard an AI assistant to your codebase's conventions

👤 Tech leads tired of reminding Claude 'no, we don't use classes here' ⏱ ~20 min beginner

Quando usar: First session on a new repo, or after a big refactor that changed conventions.

Pré-requisitos

drift installed — uvx drift or install globally

Fluxo

Run the initial scan

Run drift scan on this repo. Tell me what patterns you detected around error handling, module structure, and naming.✓ Copiado

→ Concrete convention summary with examples
Record decisions you want preserved

Record these team decisions: we use Result<T,E> not exceptions, one controller per feature folder, snake_case for file names. Tag them 'conventions'.✓ Copiado

→ Confirmation; entries queryable later
Verify future sessions pick it up

In a new session: what conventions does this repo follow?✓ Copiado

→ Claude recites the decisions you recorded

Resultado: Every future AI session starts with your team's conventions loaded — fewer corrections, more productive chats.

Armadilhas

Patterns are inferred from existing code, including bad code — Review the initial scan and delete any 'conventions' that are actually tech debt you're trying to escape
Decision memory drifts from reality if you forget to update it — Treat memory entries like docs — review quarterly

Combine com: filesystem · github

Enforce team conventions during PR review

👤 Code reviewers ⏱ ~10 min intermediate

Quando usar: Before approving a PR, check it didn't silently break team patterns.

Fluxo

Load this PR's diff

Load the diff for PR #213 and compare it against the conventions drift has recorded.✓ Copiado

→ List of convention-matches and misses
Draft review comments for deviations

For each deviation, draft a polite review comment citing the convention.✓ Copiado

→ Comment text per finding

Resultado: Consistent PR reviews without the reviewer having to remember every unwritten rule.

Armadilhas

New patterns may be intentional — don't be dogmatic — Let the author override with a 'new pattern' decision that gets recorded for future PRs

Combine com: github

Maintain a lightweight architecture decision log

👤 Any team that keeps forgetting why choices were made ⏱ ~5 min beginner

Quando usar: Instead of a formal ADR folder no one updates.

Fluxo

Record a decision when made

Record decision: we picked Postgres over DynamoDB because of ad-hoc query needs. Date today. Tags: db, architecture.✓ Copiado

→ Entry saved with ID
Query later when the question returns

Why did we pick Postgres?✓ Copiado

→ The stored decision surfaces

Resultado: Institutional memory that survives turnover.

Combinações

Combine com outros MCPs para 10× de alavancagem

drift + filesystem

drift knows the conventions, filesystem does the edits

Using the conventions drift has recorded, refactor src/api/users.ts to match. Use filesystem to apply edits.✓ Copiado

drift + github

Review incoming PRs against recorded conventions

Fetch PR #88, check it against drift conventions, draft review comments for any drift.✓ Copiado

Ferramentas

O que este MCP expõe

Ferramenta	Entradas	Quando chamar	Custo
scan_codebase	path: str	First session, or after large refactors	free; CPU-bound
list_conventions	tag?: str	Load context at session start	free
record_decision	title: str, body: str, tags?: str[]	When team agrees on something non-obvious	free
query_memory	query: str	When Claude should recall past context	free (local embeddings)
detect_pattern	area: str	Ad-hoc 'how do we normally do X here?'	free

Custo e limites

O que custa rodar

Cota de API: None — fully local
Tokens por chamada: Convention summaries: ~1k tokens. Full scan dumps can be 10k+
Monetário: Free and open source
Dica: Load summary conventions at session start, not the full scan. Full scan only on refactor.

Segurança

Permissões, segredos, alcance

Armazenamento de credenciais: Local SQLite or filesystem only

Saída de dados: None by default — runs fully offline

Decision memory may contain sensitive business context. Add the drift data dir to .gitignore.
If you enable any cloud sync features, review what's leaving the machine.

Solução de problemas

Erros comuns e correções

Scan hangs on a large monorepo

Exclude generated and vendor directories via .driftignore (same syntax as .gitignore).

Verificar: drift scan --dry-run

Memory query returns nothing relevant

Rebuild local embeddings index; new decisions don't surface until indexed.

Verificar: drift reindex

Claude doesn't use recorded conventions

Make sure the MCP is listed first in your client config so its context loads at the start of every session.

Verificar: claude mcp list

Alternativas

drift vs. outros

Alternativa	Quando usar	Troca
MARM-Systems	You want general cross-session memory not specific to code	Less code-aware; more general notes
llm-context.py	You want rule-driven code bundling rather than memory	No persistence layer
Plain ADRs in the repo	You prefer docs-as-code	AI has to read them each session — higher token cost

Mais

Recursos

📖 Leia o README oficial no GitHub

🐙 Ver issues abertas

🔍 Ver todos os 400+ servidores MCP e Skills