Skip to main content
The LangSmith Remote MCP is a Model Context Protocol (MCP) server hosted by LangSmith. It exposes the same tools as the standalone LangSmith MCP Server (conversation history, prompts, runs and traces, datasets, experiments, billing) but with OAuth-based authentication, so MCP-compatible clients connect directly without an API key, a separate deployment, or any header configuration. The Remote MCP is available on all LangSmith Cloud regions and on self-hosted LangSmith deployments running v0.15 or later. Self-hosted deployments on earlier versions should continue to use the standalone LangSmith MCP Server.

​
Endpoints

LangSmith Cloud:
Region
GCP US
GCP EU
GCP APAC
AWS US
The server discovers the rest of its OAuth metadata via RFC 8414 at /.well-known/oauth-authorization-server on the same host, so a compliant MCP client only needs the URL above. Self-hosted LangSmith: https://<your-langsmith-host>/api/mcp, where <your-langsmith-host> is the hostname of your LangSmith instance.

​
Authentication

Authentication uses OAuth 2.1 with Dynamic Client Registration (RFC 7591). Compatible MCP clients register themselves automatically on first use—there is no client ID to provision and no API key to manage. After registration:
  1. The client opens an authorization URL in your browser.
  2. You log in to LangSmith (or use an existing session) and consent.
  3. The client receives an access token and refresh token.
  4. The access token is automatically refreshed by the client when it expires.
The session is scoped to your LangSmith user and workspace permissions—calls through the MCP server can only view what your account is permitted to view.

​
Quickstart

​
Claude Code

Add the server to your project’s .mcp.json (or run claude mcp add --transport http -s user langsmith https://api.smith.langchain.com/mcp to install it user-wide): 
{
  "mcpServers": {
    "langsmith": {
      "type": "http",
      "url": "https://api.smith.langchain.com/mcp"
    }
  }
}
Then run /mcp and select langsmith to complete the OAuth flow. Tools become available as mcp__langsmith__<tool_name>.

​
Deep Agents Code (dcode)

Add the server to your user-level ~/.deepagents/.mcp.json file to make it available in every Deep Agents Code project, or add it to a project-level .mcp.json file for only that project. See the Deep Agents Code MCP tools docs for discovery locations and precedence rules. 
{
  "mcpServers": {
    "langsmith": {
      "url": "https://api.smith.langchain.com/mcp",
      "transport": "http",
      "auth": "oauth"
    }
  }
}
Then complete the OAuth login flow in one of two ways:
  • In the Deep Agents Code TUI, run /mcp, select langsmith, and follow the login prompt.
  • From your shell, run: 
    dcode mcp login langsmith
Launch dcode, or restart an active session, to load the LangSmith MCP tools. In an interactive session, run /mcp to inspect server status and loaded tools.

​
Cursor

Add to your Cursor mcp.json: 
{
  "mcpServers": {
    "LangSmith": {
      "url": "https://api.smith.langchain.com/mcp"
    }
  }
}
Cursor will prompt you to complete the OAuth flow on first use.

​
Other clients

Any MCP client supporting the Streamable HTTP transport and OAuth 2.1 with dynamic client registration can connect with just the URL above.

​
Known client incompatibilities

OpenAI Codex CLI does not work with the LangSmith Remote MCP. Codex omits the RFC 8707 resource parameter required by the MCP authorization spec during the OAuth flow, so login appears to succeed but the issued token is not bound to the LangSmith MCP and initialize fails with an auth-required error. Two upstream issues affect token exchange and authorize requests in Codex (refer to openai/codex#20729 and openai/codex#13891). In the meantime, use the LangSmith CLI from Codex—it supports the same projects, traces, runs, datasets, experiments, and threads as the MCP server, with native OAuth login.

​
Available tools

The Remote MCP exposes the same tool surface as the standalone server:
  • Conversation and threads: get_thread_history
  • Prompt management: list_prompts, get_prompt_by_name, push_prompt
  • Traces and runs: fetch_runs, list_projects
  • Datasets and examples: list_datasets, list_examples, read_dataset, read_example, create_dataset, update_examples
  • Experiments and evaluations: list_experiments, run_experiment
  • Billing: get_billing_usage
See the standalone server reference for parameter and pagination details—both servers share the same tool implementations.

​
Re-authenticating

If a client loses its session (for example, after revoking access in your LangSmith account, or if the refresh token is invalidated), trigger re-auth from the client:
  • Claude Code: run /mcp, select langsmith, choose re-authenticate.
  • Cursor: disable and re-enable the server in MCP settings.
  • Other clients: consult the client’s MCP settings UI.

​
Self-hosted LangSmith

Self-hosted LangSmith deployments on v0.15 or later expose the Remote MCP at https://<your-langsmith-host>/api/mcp. Configuration, authentication, and tool surface are identical to LangSmith Cloud. For deployments on earlier versions, run the standalone LangSmith MCP Server in your own environment and point its LANGSMITH_ENDPOINT at your self-hosted instance.
Connect these docs to Claude, VSCode, and more via MCP for real-time answers.
Edit this page on GitHub or file an issue.