MCP LangChainJS Search Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | Optional GitHub personal access token for higher API rate limits. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_langchainB | Search for examples and code in the LangChainJS GitHub repository |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool available, there is no possibility of confusing it with another tool. The tool's purpose is clearly defined by its name and description.
The single tool name follows a clear verb_noun pattern (search_langchain), and since there are no other tools, there is no inconsistency to worry about.
The server is explicitly a search-only server, so one tool is arguably appropriate, but it falls below the typical 3-15 tool range, making it feel minimal.
For its stated purpose of searching LangChainJS examples and code, the tool provides the core functionality without obvious gaps. The agent can search and receive results directly.