Skip to main content
Tool Gateway is in beta.
Tool Gateway serves tools from any number of MCP servers at one MCP URL. It calls each tool with credentials that LangSmith stores for you. In this quickstart, you add two MCP servers and connect your accounts. Then you put a selection of their tools in a tool kit and call those tools from an MCP client.

Before you begin

You need:
  • A LangSmith Plus or Enterprise plan.
  • A workspace role that can add servers. Workspace Admins and Workspace Editors can both add personal servers.
  • A personal access token. Creating servers and tool kits requires a user credential. A service key does not work for these steps.
  • Your workspace ID. Every API request sends it in the X-Tenant-Id header.
  • Accounts on two services that offer a remote MCP server. This quickstart uses Linear and Notion. To use other services, substitute their MCP URLs and tool names. If you follow the Linear example, use a test Linear workspace, because the kit includes a tool that can create issues.
  • An MCP client that supports Streamable HTTP and lets you set a custom header, which carries your LangSmith API key. This quickstart uses Claude Code. To call the tools without a client, you can send HTTP requests with curl instead.
  • jq, if you follow the API steps. The commands use it to save IDs from each response.
If you do not have a Linear or Notion account, use the public LangChain docs MCP server instead. Add it as a Public server ("connection": {"type": "none"}) with the URL https://docs.langchain.com/mcp. Skip Step 2 for it, because it needs no sign-in, and add its search_docs_by_lang_chain tool to your kit.
Set these environment variables so you can paste the commands on this page as is. If your organization is not in the GCP US region, set LANGSMITH_ENDPOINT to your region’s URL from Base URL.
To check that your key and workspace ID work, request the list of MCP servers and print only the HTTP status code:
The command prints 200 when your setup works.

Step 1. Add MCP servers

Register each MCP server once, along with the kind of credential it needs. Both example servers, Linear and Notion, use OAuth.
  1. In LangSmith, go to Tools > MCP servers.
  2. Select Personal, then click Add MCP server.
  3. Enter Linear as the name and https://mcp.linear.app/mcp as the URL, and select OAuth.
  4. Repeat for Notion, with the URL https://mcp.notion.com/mcp.
Both servers appear with the status Not connected.
If adding a server returns “This MCP server isn’t supported yet”, the server does not publish OAuth settings that Tool Gateway can use. If the server needs no sign-in, add it as Public ("connection": {"type": "none"}) instead. For every server type, see Add MCP servers.

Step 2. Connect your accounts

Sign in to each service once. Tool Gateway stores your tokens and attaches them to every later call that acts as you. Calls from an MCP client that uses your API key act as you.
  1. On Tools > MCP servers, click Connect on the Linear row.
  2. In the tab that opens, approve access in Linear. A LangSmith page confirms that authentication succeeded.
  3. Repeat for Notion.
Both servers now show the status Connected.
This quickstart connects your own accounts. To connect credentials for an agent, a profile, or the whole workspace, see Connect accounts.

Step 3. Create a tool kit

A tool kit is a curated set of tools, from any number of servers, that Tool Gateway serves to an agent at one MCP URL. This kit holds Linear’s list_issues and save_issue tools and Notion’s notion-search tool.
  1. Go to Tools > Tool kits and click Create tool kit.
  2. Enter Quickstart kit as the name, and set who can use it to Personal.
  3. In the tool picker, filter by server and select list_issues and save_issue from Linear and notion-search from Notion.
  4. Click Review tool selection, then Create tool kit.
The kit’s panel lists the tools as agents see them, and shows the kit’s MCP URL. The kit ID is the path segment after /kits/ in that URL. Save it:
The kit is personal because this quickstart’s servers are personal. A workspace kit cannot include personal servers. Kit names must be unique, so if Quickstart kit is taken, choose another name.
Agents see each tool under the server’s name as a prefix, for example, linear_list_issues, linear_save_issue, and notion_notion-search. For tool naming and other kit settings, see Create tool kits.

Step 4. Call tools from an MCP client

A tool kit is a standard Streamable HTTP MCP endpoint. Your agent or coding assistant connects to it as an MCP client. The client sends your LangSmith API key, and Tool Gateway attaches your stored Linear and Notion tokens to each call.
Add the kit to Claude Code, with your API key in the X-Api-Key header:
Run claude mcp list and confirm that quickstart-kit shows as connected. Then start Claude Code, and ask it to search Notion for a topic, or to list your Linear issues. Each call runs on the service with your account.The kit’s panel on Tools > Tool kits shows this command with your kit’s URL filled in. It also shows setup for Cursor and Managed Deep Agents. For other clients, see Connect an MCP client.

Next steps

You now have one MCP URL that serves tools from two services, each called with your own account, without any authentication code in your client. Everything in this quickstart was personal. Tool Gateway is most useful when you share this setup:
  1. Register servers once for the whole workspace, or turn on built-in servers.
  2. Give each agent a kit with only the tools it needs.
  3. Let every user or agent connect their own account, and choose whose credentials each call uses.
  4. Set policies and record traces, so you control and can review every tool call.