How to Use the Met Museum MCP in LangChain

Q: Can I trace Met Museum tool calls in LangChain using LangSmith?

Yes, every time your agent calls getobject or searchobjects, LangSmith logs the inputs, outputs, and latency. Just look at the data—it makes it easy to debug why a specific historical query failed or took longer than expected.

Q: How does the chain handle empty search results from the museum?

When searchobjects returns an empty list, the ReAct agent detects the empty payload and halts the chain. It can then automatically reformulate the query or ask the user for clarification without throwing an execution error.

Build composable LangChain reasoning chains that search, catalog, and trace historical data queries from the Met Museum.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Met Museum MCP to LangChain

Create your Vinkius account to connect Met Museum to LangChain and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Met Museum with LangChain

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Chained Artifact Discovery using LangChain

`search_objects` functions as the first link in your reasoning chain via this MCP Server. Your LangChain agent evaluates user queries, searches the museum's database, and automatically forwards the resulting IDs to the next step. This multi-step pipeline allows the output of your search to feed directly into other tools. The agent takes the ID array and immediately calls `get_object` to compile a detailed report, keeping the entire execution path visible in LangSmith.

Department-Filtered Reasoning Chains

`list_departments` provides the structured context your agent needs to make accurate decisions. Instead of guessing categories, the agent pulls the official department list to validate user intent before executing a search. This filtering step prevents broken chains and reduces API errors. Your agent matches user queries against actual department IDs, ensuring that subsequent searches target the correct historical collections.

High-Volume Cataloging Pipelines

`list_objects` retrieves large batches of object IDs to fuel your automated cataloging pipelines. The agent loops through these IDs, calling `get_object` to fetch specific details like artist, medium, and image URLs. This MCP server runs efficiently within LangGraph or standard LangChain chains. You can monitor latency, token count, and tool inputs for every single artifact retrieved, giving you full observability over your data ingestion.

Setup guide

Set up Met Museum MCP in LangChain

Prerequisites

Python 3.10+ installed
langchain-mcp-adapters + langgraph packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install langchain-mcp-adapters langgraph langchain-openai. The MCP adapters package converts MCP tools into native LangChain BaseTool objects.
2

Connect via HTTP transport
Use MultiServerMCPClient with "transport": "http" pointing to your Vinkius endpoint. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.
3

Create a ReAct agent
Pass the discovered tools to create_react_agent() from LangGraph. The agent automatically routes Met Museum tool calls through the MCP protocol.
4

Run with any LLM
Swap ChatOpenAI for ChatAnthropic, ChatGoogleGenerativeAI, or any LangChain-compatible model. The MCP tools work identically across all providers.

agent.py

from langchain_mcp_adapters.client import MultiServerMCPClient
from langgraph.prebuilt import create_react_agent
from langchain_openai import ChatOpenAI

async with MultiServerMCPClient({
    "met-museum-mcp": {
        "transport": "http",
        "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
    }
}) as client:
    tools = client.get_tools()

    agent = create_react_agent(
        ChatOpenAI(model="gpt-4o"),
        tools,
    )
    result = await agent.ainvoke({
        "messages": "List recent Met Museum transactions"
    })
    print(result["messages"][-1].content)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Met Museum. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Met Museum now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Met Museum MCP in LangChain

You use the MultiServerMCPClient from the langchain-mcp-adapters package to connect to the server's SSE or HTTP endpoint. Once connected, you call client.get_tools() and pass them directly to your agent executor.

Yes, every time your agent calls `get_object` or `search_objects`, LangSmith logs the inputs, outputs, and latency. Just look at the data—it makes it easy to debug why a specific historical query failed or took longer than expected.

Yes, you can aggregate this server alongside other sources using the multi-server client. Your LangChain agent will dynamically decide whether to pull art history data from the museum or query a different database in the same chain.

When `search_objects` returns an empty list, the ReAct agent detects the empty payload and halts the chain. It can then automatically reformulate the query or ask the user for clarification without throwing an execution error.

This MCP Server only handles public museum metadata, department listings, and object IDs. Vinkius runs the connection inside an ephemeral, zero-trust sandbox, ensuring your private chain configurations and prompt histories are never exposed.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript