LangChain documents a LangSmith Model Context Protocol server that lets MCP clients read conversation threads, prompts, runs and traces, datasets, experiments, and billing usage from a LangSmith workspace. For LangSmith Cloud, docs recommend the OAuth-authenticated LangSmith Remote MCP (regional endpoints on api.smith.langchain.com and documented EU/APAC/AWS variants) with the same tool surface and no separate deployment. The standalone HTTP server at https://langsmith-mcp-server.onrender.com/mcp remains documented for API-key access via the LANGSMITH-API-KEY header, while self-hosted LangSmith users can run the open-source langsmith-mcp-server package with uvx, Docker HTTP on port 8000, or point LANGSMITH_ENDPOINT at private instances. Tools include get_thread_history, list_prompts, fetch_runs (with FQL filters and character-budget pagination), dataset/example readers, list_experiments, and get_billing_usage per the official tool table.
Use cases
- Let coding agents pull the latest failing root runs from a production project before proposing fixes
- Compare prompt templates stored in LangSmith without copy-pasting secrets into chat logs
- Page through long thread histories with documented character-based pagination limits
- Inspect experiment metrics (latency, cost, feedback) tied to a dataset before approving rollout
- Audit trace billing usage for a date range when finance asks for utilization evidence
Key features
- Cursor
- VS Code
- Claude Desktop
- Claude Code
- Codex
Frequently Asked Questions
- Should new LangSmith Cloud users use this hosted Render URL?
- Official docs mark the standalone server page as deprecated for Cloud in favor of LangSmith Remote MCP OAuth endpoints; keep Render or uvx paths for self-hosted or legacy setups.
- Which environment variables matter locally?
- LANGSMITH_API_KEY is required; LANGSMITH_WORKSPACE_ID disambiguates multi-workspace keys; LANGSMITH_ENDPOINT targets self-hosted or regional APIs.
- How does pagination work on large traces?
- get_thread_history and fetch_runs (when trace_id is set) use character-budget pages with page_number and total_pages—docs default max_chars_per_page around 25000.
Related
Related
3 Indexed items
Apify MCP Server
Apify documents an official Model Context Protocol server hosted at https://mcp.apify.com that speaks Streamable HTTP in line with the current MCP specification; Apify warns that SSE transport was deprecated for removal April 1, 2026. Hosted clients authenticate through browser OAuth or by supplying Bearer tokens sourced from Console → Settings → Integrations (`APIFY_TOKEN`), can pin tool bundles via URL query (`?tools=actors,docs,apify/rag-web-browser` style examples reproduce Apify wording), optionally append `telemetry-enabled=false`, and benefit from inferred structured-output schemas surfaced for Actor tooling on hosted endpoints unlike the default stdio server. When MCP clients refuse remote transports, docs recommend `npx -y @apify/actors-mcp-server` with `APIFY_TOKEN` for stdio, Node.js ≥18, and adherence to documented per-user throughput (Apify cites up to thirty requests per second across Actor runs plus storage/documentation calls). Specialized payment modes (open x402 on Base plus Skyfire) appear as optional adjunct pages inside the broader integration handbook.
n8n MCP Server Trigger
The MCP Server Trigger is a first-party n8n core node that turns an n8n workflow into a Model Context Protocol server endpoint. Instead of chaining conventional trigger nodes, it connects only to tool nodes so remote MCP clients can list tools and invoke them over long-lived Server-Sent Events or streamable HTTP transports (stdio is explicitly unsupported). Each node exposes separate test and production MCP URLs, optional bearer or header authentication, and documentation explains how to proxy Claude Desktop through `npx mcp-remote` plus queue-mode caveats for multi-replica webhook deployments.
Snowflake-managed MCP Server
Snowflake documents a Snowflake-hosted Model Context Protocol (MCP) endpoint that fronts governed Snowflake data and Cortex workloads without provisioning a separate MCP bridge VM. Administrators declare tools with SQL (`CREATE MCP SERVER`)—for example Cortex Search queries, Cortex Analyst chat-style messages, Cortex Agent executions, parameterized SQL runners, or custom tools backed by Snowflake-native functions—and clients authenticate using Snowflake OAuth against the MCP revision pinned in Snowflake release notes.