What's the difference between MCP and LangChain?

MCP is an open protocol for exposing tools and data sources to any compatible client, not tied to one framework; LangChain is an orchestration library that, since version 1.4, ships a built-in client for consuming an MCP server’s tools rather than an alternative to MCP itself.

MCP describes itself as “an open-source standard for connecting AI applications to external systems,” the standard other clients, Claude and ChatGPT among them, build support for independently. LangChain used to reach MCP servers through a separate langchain-mcp-adapters package; that’s now folded into LangChain itself, in a langchain.mcp namespace built on FastMCP, requiring langchain[mcp]>=1.4.0. It’s still marked beta: importing from it raises a warning, and the interface can still change.

MCP and LangChain aren’t really the same kind of thing to begin with: MCP is a protocol for where a tool’s definition and execution live, not a framework for building the agent around it. Adding LangChain’s MCP client doesn’t change what a tool call looks like to the model; it only changes where the tool it’s calling actually runs.

sources

keep reading

More on this.

Two ways to run Tessary.

Tessary is an open-source agent reliability platform. Cloud and self-hosted run the same workflow on the OpenTelemetry traces your agent already emits.

Tessary Cloud

We host it for you. Send your first trace with nothing to deploy and no model key.

what's includedper organization
traces
10,000 per calendar month
stored trace data
1 GB
retention
30 days
model credit
$10, one-time, for triage and root-cause analysis
credit card
not required

Self-hosted Tessary

Run the open-source code on your own infrastructure with one command. Add your own model key for triage and root-cause analysis.

Self-host Tessary for me by following https://github.com/tessaryai/tessary/blob/main/setup.md

docker compose -f oci://docker.io/tessaryai/tessary:compose up -d -y