langsmith-fetch-skill MCP — Casos de uso, Instalar & Demo ao vivo

Por que usar

Principais recursos

Pulls traces directly from LangSmith Studio via CLI
Auto-triggers on debugging-flavored prompts
Tracks failures + root causes
Latency + token usage analysis
Tool-call and memory operation review
Session export

Demo ao vivo

Como fica na prática

langsmith-fetch-skill.replay ▶ pronto

0/0

Instalar

Escolha seu cliente

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

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

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

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

{
  "mcpServers": {
    "langsmith-fetch-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/OthmanAdi/langsmith-fetch-skill",
        "~/.claude/skills/langsmith-fetch-skill"
      ],
      "_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": {
    "langsmith-fetch-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/OthmanAdi/langsmith-fetch-skill",
        "~/.claude/skills/langsmith-fetch-skill"
      ],
      "_inferred": true
    }
  }
}

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

~/.codeium/windsurf/mcp_config.json

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

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

~/.continue/config.json

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

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

~/.config/zed/settings.json

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

Adicione em context_servers. Zed recarrega automaticamente ao salvar.

claude mcp add langsmith-fetch-skill -- git clone https://github.com/OthmanAdi/langsmith-fetch-skill ~/.claude/skills/langsmith-fetch-skill

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

Casos de uso

Usos do mundo real: langsmith-fetch-skill

Diagnose a slow agent without opening LangSmith UI

👤 LangChain/LangGraph devs ⏱ ~20 min intermediate

Quando usar: An agent that used to be snappy is now slow; you want root cause.

Pré-requisitos

LangSmith API key — smith.langchain.com -> Settings -> API Keys
Skill installed — git clone https://github.com/OthmanAdi/langsmith-fetch-skill ~/.claude/skills/langsmith-fetch-skill

Fluxo

Ask Claude to diagnose

Why is my agent <name> slow? Pull the last 20 traces from LangSmith and find the hotspot.✓ Copiado

→ Skill fetches traces; reports latency by step
Drill in

Focus on trace <id> — break down tool-call times.✓ Copiado

→ Per-tool latency with the outlier called out

Resultado: A specific step to optimize, not a hunch.

Armadilhas

Optimizing the average when tail latency is the problem — Ask for p95/p99 specifically

Combine com: filesystem

Root-cause an agent failure from a trace id

👤 Anyone running LangGraph in production ⏱ ~15 min intermediate

Quando usar: A user reported an error; you have the trace id.

Fluxo

Fetch + analyze

Debug trace <id>. What was the immediate error, what's the root cause in the graph?✓ Copiado

→ Error step + upstream decision that led to it

Resultado: A fix targeting the actual decision point, not the symptom.

Find which node burns the most tokens

👤 Teams optimizing LLM spend ⏱ ~30 min intermediate

Quando usar: Monthly review of agent spend.

Fluxo

Aggregate token usage

Across last 7 days' traces, rank graph nodes by total token usage.✓ Copiado

→ Ranked table with % share
Propose tightening

For the top 3, propose prompt-compression or model downgrade options.✓ Copiado

→ Targeted opt list

Resultado: Measurable spend reduction without chasing tiny savings.

Combinações

Combine com outros MCPs para 10× de alavancagem

langsmith-fetch-skill + filesystem

Save exports alongside the agent code for lineage

Export the debugging session to debugging/traces/<date>.json.✓ Copiado

langsmith-fetch-skill + github

Attach trace summary to a bug report

Summarize trace <id> and post as comment on GitHub issue #42.✓ Copiado

Ferramentas

O que este MCP expõe

Ferramenta	Entradas	Quando chamar	Custo
fetch_recent	project, limit	Broad diagnosis	LangSmith quota
fetch_trace	trace_id	Deep dive on one run	LangSmith quota
analyze_failures	traces	Post-fetch analysis	0
export_session	traces	Archive for later	0

Custo e limites

O que custa rodar

Cota de API: LangSmith: depends on plan; Studio has generous quotas
Tokens por chamada: Low — traces are structured
Monetário: Free skill; LangSmith free tier covers most devs
Dica: Use fetch_recent with a narrow window, not full history

Segurança

Permissões, segredos, alcance

Escopos mínimos: LangSmith: read on your project(s)

Armazenamento de credenciais: LANGCHAIN_API_KEY in env

Saída de dados: Only to LangSmith (where the traces already live)

Nunca conceda: Write to LangSmith — skill only reads

Traces can include user inputs and outputs — treat them as user data under your privacy policy.

Solução de problemas

Erros comuns e correções

langsmith-fetch: command not found

Install LangSmith CLI or ensure it's on PATH

Verificar: which langsmith-fetch

Empty results

Check project name and time window; traces are project-scoped

Alternativas

langsmith-fetch-skill vs. outros

Alternativa	Quando usar	Troca
LangSmith web UI	You prefer clicking	No Claude analysis

Mais

Recursos

📖 Leia o README oficial no GitHub

🐙 Ver issues abertas

🔍 Ver todos os 400+ servidores MCP e Skills