4,500+ servers built on MCP Fusion
Vinkius
Harvard Art Museums logo
Vinkius
LlamaIndex logo

How to Use the Harvard Art Museums MCP in LlamaIndex

Index the Harvard Art Museums collection into searchable vector stores using LlamaIndex.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Harvard Art Museums MCP on Cursor AI Code Editor MCP Client Harvard Art Museums MCP on Claude Desktop App MCP Integration Harvard Art Museums MCP on OpenAI Agents SDK MCP Compatible Harvard Art Museums MCP on Visual Studio Code MCP Extension Client Harvard Art Museums MCP on GitHub Copilot AI Agent MCP Integration Harvard Art Museums MCP on Google Gemini AI MCP Integration Harvard Art Museums MCP on Lovable AI Development MCP Client Harvard Art Museums MCP on Mistral AI Agents MCP Compatible Harvard Art Museums MCP on Amazon AWS Bedrock MCP Support
MCP Servers - Free for Subscribers
LlamaIndex

Connect Harvard Art Museums MCP to LlamaIndex

Create your Vinkius account to connect Harvard Art Museums to LlamaIndex 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

Embed museum artifacts into vector stores

The `search_museum_objects` tool pulls raw artifact metadata so LlamaIndex can embed it into a vector store. You are not just making isolated API calls. Your application ingests thousands of museum records and transforms them into a unified, queryable knowledge base. When you need deep context on a specific piece, the agent triggers `get_object_details`. LlamaIndex takes that rich provenance data and indexes it alongside your local art history documents. You get semantic search across both live API responses and your own files.

Ground LlamaIndex queries with MCP Server data

The `search_exhibitions` tool feeds historical event data directly into your RAG pipeline. Instead of hallucinating curation histories, your agent retrieves actual exhibition dates and themes from the museum. It grounds every answer in real institutional records. You can cross-reference these events by indexing the output of `search_museum_people`. LlamaIndex maps the relationships between artists and the shows they featured in. The framework turns flat JSON responses into a highly connected semantic graph.

Index physical gallery layouts

The `list_museum_galleries` tool retrieves the physical floor plans and room assignments of the Harvard Art Museums. Your LlamaIndex application indexes these locations to answer spatial queries. Users can ask which rooms contain specific art movements, and the agent searches the vector store to find the match. We included `check_api_status` to ensure your indexing jobs do not fail silently. Your script verifies the endpoint is alive before attempting to pull and embed thousands of gallery records. You save compute costs by catching downtime early.

Setup guide

Set up Harvard Art Museums MCP in LlamaIndex

Prerequisites

  • Python 3.10+ installed
  • llama-index-tools-mcp package
  • Active Vinkius subscription with a valid endpoint token
  1. 1

    Install dependencies

    Run pip install llama-index-tools-mcp llama-index-llms-openai. The MCP tools package provides BasicMCPClient and McpToolSpec.

  2. 2

    Connect with BasicMCPClient

    Point BasicMCPClient to your Vinkius endpoint URL. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. Supports SSE and Streamable HTTP transports.

  3. 3

    Convert to LlamaIndex tools

    Call mcp_tool_spec.to_tool_list_async() to convert all Harvard Art Museums MCP tools into native FunctionTool objects that any LlamaIndex agent can use.

  4. 4

    Run with any LLM

    Create a FunctionAgent with the tools and your preferred LLM. Swap OpenAI for Anthropic, Gemini, or any LlamaIndex-supported provider.

agent.py
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

# Connect to the MCP
mcp_client = BasicMCPClient(
    "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)
mcp_tool_spec = McpToolSpec(client=mcp_client)

# Convert MCP tools to LlamaIndex tools
tools = await mcp_tool_spec.to_tool_list_async()

# Create and run the agent
agent = FunctionAgent(
    tools=tools,
    llm=OpenAI(model="gpt-4o"),
    system_prompt="You have access to Harvard Art Museums tools.",
)
response = await agent.run("List recent Harvard Art Museums data")

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Harvard Art Museums. 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.

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 Harvard Art Museums MCP in LlamaIndex

Install `llama-index-tools-mcp` via pip. Initialize a `BasicMCPClient` with your Vinkius URL, then wrap it in an `McpToolSpec`. Call `to_tool_list_async()` and pass the result to your `FunctionAgent`.
It pulls the data using the server tools and you handle the embedding. You query the API, store the JSON responses, and run them through your chosen embedding model to build the index.
The MCP server itself does not cache responses. Once LlamaIndex ingests the data into your vector store, you query that local index without hitting the museum's API again.
Yes. You can apply an `allowed_tools` filter when setting up the tool spec. This restricts the agent to specific endpoints if you only care about physical spaces.
This server handles public exhibition histories, artist biographies, and gallery metadata. Vinkius enforces a zero-trust architecture. Authentication happens at the edge, and the server drops all context immediately after returning the payload.

Start using the Harvard Art Museums MCP today

We host it, we monitor it, we maintain it. You just paste one token.

Built & Managed by Vinkius 30s setup 6 tools

We've already built the connector for Harvard Art Museums. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 6 tools are live and waiting. You're up and running in seconds.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.