LangSmith Tool Gateway Enters Public Beta for Agents
What shipped
LangChain opened the Public Beta of LangSmith Tool Gateway on November 19, 2026, running on the LangSmith Agent Platform (LangChain). The service gives agents a single MCP URL through which they can reach tools hosted across multiple MCP servers, rather than wiring each agent to each server individually (LangChain docs).
Why it matters
For teams building and deploying agents, tool access has been a patchwork of credentials, API keys and ad hoc permissioning scattered across whatever MCP servers an agent needs to call. Tool Gateway centralizes that: it manages credentials, identity, access policies, approvals and traces for every tool call an agent makes (LangChain docs). That matters for buyers of agent infrastructure because it turns tool access into something that can be audited and restricted after the fact, rather than something each agent integration handles on its own — a gap that has shown up repeatedly in agent-related incidents involving over-broad credentials.
How it works
Developers can register remote MCP servers, switch on built-in servers, connect accounts or API keys, and bundle selected tools into "tool kits" that agents draw from (LangChain docs). Access policies can deny specific tool calls at the level of an individual user, a service key, a combination of the two, an organization, or a workspace, and policies can also force a human approval step before a tool call executes (LangChain docs). Every call is traced, giving teams a record of what an agent requested and what it was permitted to do.
The Gateway supports MCP clients including LangChain, Deep Agents, Managed Deep Agents, Claude Code, and Cursor (LangChain docs), and remote MCP servers connecting to it must use Streamable HTTP over HTTPS (LangChain docs).
Availability
Tool Gateway is available on LangSmith Plus and Enterprise plans and runs on LangSmith Cloud in the GCP US, GCP EU, GCP APAC, and AWS US regions; it is not yet available on Azure US (LangChain docs). LangChain has not published a license designation, customer counts, or adoption figures for the beta, and no breaking changes accompany the release — it is a new managed service rather than a migration.


