LangSmith MCP Server

List LangSmith projects with optional filtering and detail level control.

Fetches projects from LangSmith, optionally filtering by name and controlling the level of detail returned. Can return either simplified project information or full project details. In case a dataset id or name is provided, you don't need to provide a project name.

🧩 PURPOSE

This function provides a convenient way to list and explore LangSmith projects. It supports:

• Filtering projects by name (partial match)

• Limiting the number of results

• Choosing between simplified or full project information

• Automatically extracting deployment IDs from nested project data

⚙️ PARAMETERS

limit : int, default 5 Maximum number of projects to return (as string, e.g., "5"). This can be adjusted by agents or users based on their needs.

project_name : str, optional Filter projects by name using partial matching. If provided, only projects whose names contain this string will be returned. Example: project_name="Chat" will match "Chat-LangChain", "ChatBot", etc.

more_info : str, default "false" Controls the level of detail returned: - "false" (default): Returns simplified project information with only essential fields: name, project_id, and agent_deployment_id (if available) - "true": Returns full project details as returned by the LangSmith API

reference_dataset_id : str, optional The ID of the reference dataset to filter projects by. Either this OR reference_dataset_name must be provided (but not both).

reference_dataset_name : str, optional The name of the reference dataset to filter projects by. Either this OR reference_dataset_id must be provided (but not both).

📤 RETURNS

List[dict] A list of project dictionaries. The structure depends on more_info:

🧪 EXAMPLES

1️⃣ List first 5 projects (simplified)

2️⃣ Search for projects with "Chat" in the name

3️⃣ Get full project details

4️⃣ Find a specific project with full details

🧠 NOTES FOR AGENTS

• Use more_info="false" for quick project discovery and listing

• Use more_info="true" when you need detailed project information

• The agent_deployment_id field is automatically extracted from nested project data when available, making it easy to identify agent deployments

• Projects are filtered to exclude reference projects by default

• The function uses name_contains for filtering, so partial matches work