4,500+ servers built on MCP Fusion
Vinkius
LangSmith logo
Vinkius
Claude Code logo

How to Use the LangSmith MCP in Claude Code

Pipe LangSmith MCP Server observability data directly into your terminal with Claude Code for headless trace debugging.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

LangSmith MCP on Cursor AI Code Editor MCP Client LangSmith MCP on Claude Desktop App MCP Integration LangSmith MCP on OpenAI Agents SDK MCP Compatible LangSmith MCP on Visual Studio Code MCP Extension Client LangSmith MCP on GitHub Copilot AI Agent MCP Integration LangSmith MCP on Google Gemini AI MCP Integration LangSmith MCP on Lovable AI Development MCP Client LangSmith MCP on Mistral AI Agents MCP Compatible LangSmith MCP on Amazon AWS Bedrock MCP Support
MCP Servers - Free for Subscribers
Claude Code

Connect LangSmith MCP to Claude Code

Create your Vinkius account to connect LangSmith to Claude Code and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Monitor Projects from the CLI

The `langsmith_list_projects` tool outputs your high-level tracing metrics straight to standard out. Claude Code fetches your project list, grabbing aggregate run counts, latency stats, and feedback scores. This fits perfectly into a morning SRE routine. You run a quick terminal command to check system health, and the agent pulls the latency metrics across all environments without you ever opening a browser tab.

Query Execution Runs Headless

The `langsmith_list_runs` tool extracts recent LLM executions for a specific project. Claude Code pulls the run names, execution statuses, token usage, and timing data. You can script this into a CI/CD pipeline. Have your GitHub Action trigger Claude Code to check the staging project for any failed runs after a deployment, automatically failing the build if the error rate spikes.

Debug Deep MCP Server Traces

The `langsmith_get_run` tool isolates a single trace ID and pulls the granular execution data. Claude Code retrieves the exact inputs, outputs, and intermediate tool calls of that specific run. When an alert fires at 2 AM, you just pipe the trace ID into your terminal. The agent reads the payload, identifies the timeout in the chain execution, and prints the root cause directly to your shell.

Setup guide

Set up LangSmith MCP in Claude Code

Prerequisites

  • Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
  • Active Vinkius subscription with a valid endpoint token
  1. 1

    Run the add command

    Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.

  2. 2

    Verify the connection

    Start a Claude Code session and type /mcp to list connected servers. You should see langsmith-mcp with a green status indicator.

  3. 3

    Start using tools

    Ask Claude Code something like "Check my latest LangSmith transactions." It will automatically discover and invoke the available LangSmith tools.

Terminal
claude mcp add --transport http langsmith-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about LangSmith MCP in Claude Code

Run `claude mcp add --transport http -- ` in your terminal. Make sure all flags come before the server name so the config saves correctly to `~/.claude.json`.
Yes, if you script it. You can set up a cron job that triggers the agent to run the list projects tool and check the median latency stats against your SLAs.
That is exactly what it is built for. You can run it headless in a Docker container to validate that your integration tests didn't generate any failed LLM runs.
You instruct the agent on how you want the data. Tell it to output the trace inputs and token counts as a JSON object, and it formats standard out accordingly.
Your execution metadata, including raw token usage and model inputs, is routed through an ephemeral V8 Isolate Sandbox. Vinkius strips all state after the terminal session closes, guaranteeing strict data isolation.

Start using the LangSmith MCP today

We host it, we monitor it, we maintain it. You just paste one token.

Built & Managed by Vinkius 30s setup 3 tools

We've already built the connector for LangSmith. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 3 tools are live and waiting. You're up and running in seconds.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.