How to Use the Cooper Hewitt MCP in LlamaIndex

Q: How do I index Cooper Hewitt object data with LlamaIndex?

You load the tools using McpToolSpec and call getobjectinfo to fetch raw metadata. Then, you convert the JSON response into a standard document Node and insert it directly into your vector store index.

Q: Can LlamaIndex query Cooper Hewitt exhibitions dynamically during a search?

Yes, your agent can call listexhibitions at query time to fetch live museum data. This lets your RAG pipeline combine static vector data with real-time exhibition schedules and room listings.

Q: How do I limit which Cooper Hewitt tools LlamaIndex can access?

You use the allowedtools filter when initializing the client to restrict access. For example, you can expose only searchobjects and getobjectimages while blocking test tools like testerror.

Q: Can I use the museum's color palettes for image-based RAG?

Yes, by pulling image metadata with getobjectimages and color data with getobjectcolors. You can index these fields to let users search your knowledge base using visual attributes.

Index Cooper Hewitt museum data and design history directly into your LlamaIndex vector stores for grounded RAG.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Cooper Hewitt MCP to LlamaIndex

Create your Vinkius account to connect Cooper Hewitt 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

Setup Cooper Hewitt with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Index Museum Color Palettes into LlamaIndex Vector Stores

Feeding physical color palettes into your index is straightforward when this MCP Server runs `get_object_colors`. Your agent queries the museum's collection, extracts the exact color hex codes, and stores them as searchable vector embeddings. Here's the thing: instead of guessing design trends, your RAG application queries this indexed color data to find historical matches. You get grounded answers based on actual design history records rather than hallucinated color combinations.

Build Searchable Knowledge Bases from Exhibition Records

Pulling complete historical exhibition records is handled directly when this MCP Server exposes `get_exhibition_objects` and `get_exhibition_info`. The agent reads these museum lists and indexes them as nodes for semantic search. Users can then query your index to find which design pieces were displayed together in specific rooms. This turns raw museum API responses into a structured, searchable knowledge base of design history.

Grounded RAG Queries Using Faceted Museum Searches

Retrieving deeply categorized design objects is simple because this MCP Server provides `search_objects_faceted`. Your agent indexes these faceted results to allow precise filtering on your vector queries. By combining live API searches with your local index, your agent answers complex design questions with zero hallucination. It matches user queries against actual object records retrieved directly from the museum database.

Setup guide

Set up Cooper Hewitt MCP in LlamaIndex

Prerequisites

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

1

Install dependencies
Run pip install llama-index-tools-mcp llama-index-llms-openai. The MCP tools package provides BasicMCPClient and McpToolSpec.
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

Convert to LlamaIndex tools
Call mcp_tool_spec.to_tool_list_async() to convert all Cooper Hewitt MCP tools into native FunctionTool objects that any LlamaIndex agent can use.
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 Cooper Hewitt tools.",
)
response = await agent.run("List recent Cooper Hewitt data")

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 Cooper Hewitt. 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 Cooper Hewitt 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 Cooper Hewitt MCP in LlamaIndex

You load the tools using `McpToolSpec` and call `get_object_info` to fetch raw metadata. Then, you convert the JSON response into a standard document Node and insert it directly into your vector store index.

Yes, your agent can call `list_exhibitions` at query time to fetch live museum data. This lets your RAG pipeline combine static vector data with real-time exhibition schedules and room listings.

You use the `allowed_tools` filter when initializing the client to restrict access. For example, you can expose only `search_objects` and `get_object_images` while blocking test tools like `test_error`.

Yes, by pulling image metadata with `get_object_images` and color data with `get_object_colors`. You can index these fields to let users search your knowledge base using visual attributes.

Your search terms and indexed museum records remain entirely inside your local vector store and the secure, ephemeral V8 sandbox. No design metadata, object queries, or exhibition histories are stored or shared with external parties.

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