## Overview
<!-- Brief description of what documentation is being added/updated -->
## Type of change
**Type:** [Update existing documentation]
## Related issues/PRs
<!--
Link to related issues, feature PRs, or discussions (if applicable)
To automatically close an issue when this PR is merged, use closing
keywords:
- "closes #123" or "fixes #123" or "resolves #123"
For regular references without auto-closing, just use:
- "#123" or "See issue #123"
Examples:
- closes#456 (will auto-close issue #456 when PR is merged)
- See #789 for context (will reference but not auto-close issue #789)
-->
- GitHub issue:
- Feature PR:
<!-- For LangChain employees, if applicable: -->
- Linear issue:
- Slack thread:
## Checklist
<!-- Put an 'x' in all boxes that apply -->
- [ ] I have read the [contributing guidelines](README.md)
- [ ] I have tested my changes locally using `docs dev`
- [ ] All code examples have been tested and work correctly
- [ ] I have used **root relative** paths for internal links
- [ ] I have updated navigation in `src/docs.json` if needed
(Internal team members only / optional): Create a preview deployment as
necessary using the [Create Preview Branch
workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml)
## Additional notes
<!-- Any other information that would be helpful for reviewers -->
## Overview
<!-- Brief description of what documentation is being added/updated -->
## Type of change
**Type:** Update existing documentation
## Related issues/PRs
<!--
Link to related issues, feature PRs, or discussions (if applicable)
To automatically close an issue when this PR is merged, use closing
keywords:
- "closes #123" or "fixes #123" or "resolves #123"
For regular references without auto-closing, just use:
- "#123" or "See issue #123"
Examples:
- closes#456 (will auto-close issue #456 when PR is merged)
- See #789 for context (will reference but not auto-close issue #789)
-->
- GitHub issue:
- Feature PR:
<!-- For LangChain employees, if applicable: -->
- Linear issue:
- Slack thread:
## Checklist
<!-- Put an 'x' in all boxes that apply -->
- [ ] I have read the [contributing guidelines](README.md)
- [ ] I have tested my changes locally using `docs dev`
- [ ] All code examples have been tested and work correctly
- [ ] I have used **root relative** paths for internal links
- [ ] I have updated navigation in `src/docs.json` if needed
(Internal team members only / optional): Create a preview deployment as
necessary using the [Create Preview Branch
workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml)
## Additional notes
<!-- Any other information that would be helpful for reviewers -->
---------
Co-authored-by: Mason Daugherty <github@mdrxy.com>
Co-authored-by: Mason Daugherty <mason@langchain.dev>
## Overview
We have recently published the `langchain-parallel` integration,
allowing developers to use Parallel's search, extract, and chat features
with LangChain.
- GitHub repo:
https://github.com/parallel-web/langchain-parallel/tree/main
- Docs: https://docs.parallel.ai/integrations/langchain
This PR adds net new documentation for this integration to the LangChain
docs.
## Type of change
**Type:** New documentation page
## Related issues/PRs
Discussions on Slack in `langchain-parallel-shared`.
## Checklist
<!-- Put an 'x' in all boxes that apply -->
- [x] I have read the [contributing guidelines](README.md)
- [x] I have tested my changes locally using `docs dev`
- [x] All code examples have been tested and work correctly
- [x] I have used **root relative** paths for internal links
- [x] I have updated navigation in `src/docs.json` if needed
(Internal team members only / optional): Create a preview deployment as
necessary using the [Create Preview Branch
workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml)
## Additional notes
<!-- Any other information that would be helpful for reviewers -->
---------
Co-authored-by: Mason Daugherty <mason@langchain.dev>
Co-authored-by: Mason Daugherty <github@mdrxy.com>
Added section on Model Context Protocol (MCP) support and its benefits.
## Overview
This PR makes the langchain-mcp-adapters package easier to find. It adds
a new “Model Context Protocol (MCP)” section at the top of the
Integrations Overview page.
MCP support was only previously mentioned in a tip block. This made it
hard for developers to find when looking for integration options. This
update shows that MCP is an important integration. It also explains its
purpose and value for users of LangChain and LangGraph.
## Type of change
**Type:** Update existing documentation
## Related issues/PRs
Fixes#32395
## Checklist
<!-- Put an 'x' in all boxes that apply -->
- [x] I have read the [contributing guidelines](README.md)
- [x] I have tested my changes locally using `docs dev`
- [x] All code examples have been tested and work correctly
- [x] I have used **root relative** paths for internal links
- [x] I have updated navigation in `src/docs.json` if needed
- I have gotten approval from the relevant reviewers
- (Internal team members only / optional) I have created a preview
deployment using the [Create Preview Branch
workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml)
* significant cleanup of API ref -- only listing init functions, also
cleaning up tables of refs to various middlewares
* breaking out middleware page into a middleware section with
* overview
* custom middlewares
* prebuilt middlewares
* custom middleware has consolidated content in python re "decorator vs
class based" syntax
* opted to keep config options bc we don't have great API refs for js
still todo:
* general editing
* I think we really want to focus on the "one liner" intros to each
prebuilt
* determine structure for individual middleware sections (do we like
what's here? maybe we don't need the extended examples?)
* need help w/ structure on the index page -- need more conceptual copy
I think?
* we have a diff HITL page that only uses this middleware, what to do
about consolidation there?
* api refs for js
---------
Co-authored-by: Lauren Hirata Singh <lauren@langchain.dev>
E. Eshetu