Watchlist tracking
Reviewed for relevance and future tracking value.
MCP100 Assessment
Watchlist / Tracking
Why we’re tracking it
Follow-up value is specific to LangChain adapters for local and remote MCP tools, multimodal results and elicitation: Do elicitation pauses and multimodal outputs remain compatible with supported LangChain peer versions?
Reviewed · Documentation review; complete setup workflow not independently tested
Best fit
Connecting LangChain.js agents to MCP tools, resources and prompts
What we know
TypeScript adapter that manages MCP connections and converts MCP tools for LangChain agents.
Maintenance / activity evidence
- @langchain/mcp-adapters 2.0.0 published 2026-10-01T01:16:28.271Z
Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.
Verification gaps / watch-outs
- Installation and comprehensive security have not been independently audited.
- Delegated to connected MCP servers. Writes: Depends on connected tools.
- Token/OAuth per target server.
- Sensitive access: Depends on target credentials/data
- The adapter itself is infrastructure; downstream servers determine real authority.
Full authority, access and evidence limits are available in Review context and Access & risk.
Popularity
· 999.4k package downloads / 30 days
Downloads observed Sep 25, 2026.
30-day package downloads intentionally left null because the package-stats provider ran out of credits during Batch 3 QA.
30-day package downloads intentionally left null because the package-stats provider ran out of credits during Batch 3 QA.
All limitations / Review context
Do elicitation pauses and multimodal outputs remain compatible with supported LangChain peer versions?
The bounded review of the publisher's documented LangChain adapters for local and remote MCP tools, multimodal results and elicitation and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.
- The adapter itself is infrastructure; downstream servers determine real authority.
- Delegated to connected MCP servers.
- Token/OAuth per target server.
- Tool calls/results pass between LangChain and servers.
- Reviewed write actions: Depends on connected tools
- Sensitive access: Depends on target credentials/data
- Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
- Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
- Documented tool authority and any remote data handling must be checked before installation or use.
- Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
- Exact repository identity/shared star metric
- Requires current Node/LangChain peer versions.
- Permissions remain downstream-server defined.
Original activity observations
- @langchain/mcp-adapters 2.0.0 published 2026-10-01T01:16:28.271Z
Technical identity
npm/@langchain/mcp-adapters- Exact implementation source
- https://www.npmjs.com/package/@langchain/mcp-adapters ↗
- Reviewed resource type
- SDK
- Package identity
- @langchain/mcp-adapters
Evidence & Sources
- Evidence basis
- Recorded source evidence
- Setup runtime verification
- Not independently runtime-tested by MCP100 for this setup workflow.
Reviewed · Latest source observation
- Package registry ↗
@langchain/mcp-adapters
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
Setup · Watchlist
SDK setup
Publisher instructions.
Source evidence observed .
Additional setup details required — see the specific gaps below.
Install SDK / application integration
Publisher instructionsDeveloper library/integration. Install in an application; not a plug-and-play MCP Server. Review publisher README. Not a standalone local MCP server; application integration required.
publisher documented install or connect · Publisher instructions
npm install @langchain/mcp-adapters @langchain/core @langchain/langgraphConfigure / authenticate
MCP100 setup guideInside a Node LangChain.js app instantiate MCPAdapter with specific real MCP server URL or local command; use await adapter.listTools(), invoke a read-only tool, and await adapter.close() in finally. The adapter package is a client SDK, not an MCP server.
Check connection
Suggested checkSDK: instantiate MCP adapters in an application and perform a read-only tools listing against a configured test server. This package is not a standalone MCP server. SDK/plugin validation means app import/initialization or feature availability, not an MCP client tools/list test unless the consuming app actually exposes a server.
Remove / uninstall / revoke
MCP100 setup guideLangChain.js MCP Adapters is an application dependency, not a runnable MCP server: call `await adapter.close()` in application teardown and remove `@langchain/mcp-adapters` via `npm uninstall @langchain/mcp-adapters` when unused; remove any server connections from app configuration separately.
MCP client unregister, stopping hosted processes, package uninstall, OAuth disconnect and token revocation are distinct actions.
A claude mcp remove command is only valid for Claude Code when the local registration actually has that name. Other MCP hosts require their own UI/config cleanup.
Separate credential guidance / limitations: Not applicable to the adapter library; connected server secrets must be revoked through those services.
Package / application cleanup · matching installation environment · MCP100 composed guide
npm uninstall @langchain/mcp-adapters
Official Documentation & Sources
What it does
TypeScript adapter that manages MCP connections and converts MCP tools for LangChain agents.
- Capability
- Developer Tools
- Resource type
- SDK
- Industry
- Software & Technology
- Best fit
- Connecting LangChain.js agents to MCP tools, resources and prompts
Representative uses
- Connect one/many MCP servers
- Load tools into LangChain
- Use token/OAuth auth
- Handle MCP elicitation/user-input flows
Limitations
- Requires current Node/LangChain peer versions.
- Permissions remain downstream-server defined.
Reviewed access
Access & risk
Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.
- Authentication
- Token/OAuth per target server.
- Permissions
- Delegated to connected MCP servers.
- Data handling
- Tool calls/results pass between LangChain and servers.
- Cost
- unknown
- Risk and cautions
- The adapter itself is infrastructure; downstream servers determine real authority.
Access scope and cautions
- Write actions
- Depends on connected tools
- Sensitive access
- Depends on target credentials/data
- Risk level
- moderate
FAQ
Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.
Which tasks are documented for this implementation?
What setup and authentication are documented?
Can it modify data or perform write operations?
What data-handling boundary should I consider?
What limitations and risks should I check before use?
Is this an official MCP?
LangChain is listed as First-party MCP in MCP100’s current evidence.