Skip to content

Conversation

@rahul-langchain
Copy link
Contributor

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

(Internal team members only / optional): Create a preview deployment as necessary using the Create Preview Branch workflow

@github-actions github-actions bot added langsmith For docs changes to LangSmith internal labels Dec 15, 2025
@github-actions
Copy link
Contributor

Mintlify preview ID generated: preview-rahulo-1765832164-f48691a

Copy link
Collaborator

@lnhsingh lnhsingh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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)

</Card>
</CardGroup>

## Using remote MCP servers
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
## Using remote MCP servers
## MCP server tools

?

title: Tools
sidebarTitle: Tools
---
## Built-in Tools
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need to add an intro sentence/section above Built-in Tools

@rahul-langchain
Copy link
Contributor Author

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

internal langsmith For docs changes to LangSmith

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants