Move remote MCP server section to overall agent builder tool documentation #1917
Conversation
|
Mintlify preview ID generated: preview-rahulo-1765832164-f48691a |
lnhsingh
left a comment
lnhsingh
left a comment
There was a problem hiding this comment.
Is there an argument for combining all of the tool server doc into the Tools doc?
| sidebarTitle: MCP framework | ||
| --- | ||
|
|
||
| The LangSmith Tool Server is our MCP Framework that powers the tools available in the LangSmith Agent Builder. This framework enables you to build and deploy custom tools that can be integrated with your agents. It provides a standardized way to create, deploy, and manage tools with built-in authentication and authorization. |
There was a problem hiding this comment.
| The LangSmith Tool Server is our MCP Framework that powers the tools available in the LangSmith Agent Builder. This framework enables you to build and deploy custom tools that can be integrated with your agents. It provides a standardized way to create, deploy, and manage tools with built-in authentication and authorization. | |
| The LangSmith Tool Server is our MCP framework that powers the tools available in the LangSmith Agent Builder. This framework enables you to build and deploy custom tools that can be integrated with your agents. It provides a standardized way to create, deploy, and manage tools with built-in authentication and authorization. |
|
|
||
| The handler runs on every request and must return a dict with `identity` (and optionally `permissions`). | ||
|
|
||
| ## Using remote MCP servers |
There was a problem hiding this comment.
I think there should still probably be a link to the MCP server config info. Maybe there should be a new section here? Like the following:
## Related
- [MCP server tools](/langsmith/agent-builder-tools#mcp-server-tools)
There was a problem hiding this comment.
Maybe we can add a note that if you are using the agent builder, you can configure the tool server instance we set up for you as part of the agent builder in order to use your custom MCP servers
|
I think the tool server docs and the agent builder tools docs should be separate because they're separate features, and typically you would use one or the other, not both at the same time (the tool server is integrated with the agent builder under the hood, but that's not visible if you're using or even configuring agent builder) |
|
Mintlify preview ID generated: preview-rahulo-1765991181-6c293c6 |
| args = ["-m", "mcp_server_math"] | ||
| ``` | ||
|
|
||
| All tools from connected MCP servers are exposed through your server's `/mcp` endpoint. MCP tools are prefixed with their server name to avoid conflicts (e.g., `weather.get_forecast`, `math.add`). |
There was a problem hiding this comment.
I should have updated it myself but it's an _ now not a .
| ### How it works | ||
|
|
||
| - Agent Builder discovers tools from remote MCP servers via the standard MCP protocol. | ||
| - Headers configured in your workspace are automatically attached when fetching tools or calling them. |
There was a problem hiding this comment.
Might be good to mention here that the headers can be used for authentication
2 participants
Overview
This section was in the Tool Server framework documentation, but I think it makes more sense alongside the documentation for tools for the agent builder.
Type of change
Type: Update existing documentation
Checklist
docs dev(Internal team members only / optional): Create a preview deployment as necessary using the Create Preview Branch workflow