How to Use the Met Museum MCP in Cursor

Q: Can I use Cursor to build an app using Met Museum data?

Yes, the server exposes tools like getobject and searchobjects to fetch live data. Cursor uses these responses to write accurate, production-ready code.

Q: Do I need to write custom fetch scripts to search the Met Museum in Cursor?

No, your agent uses searchobjects directly to find items. It writes the resulting JSON payloads straight into your workspace files.

Q: How do I inspect specific department IDs inside my code?

You ask Cursor to run listdepartments. The agent returns the raw IDs so you can hardcode or map them in your configuration files.

Generate code with live art historical metadata by connecting Cursor directly to the museum's database.

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 Cursor

Create your Vinkius account to connect Met Museum to Cursor 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 Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Write code using real Met Museum API responses

The `get_object` tool fetches real-time metadata payloads for any specific artwork in the collection. Cursor's agent uses this live structure to generate accurate TypeScript interfaces or database schemas instead of relying on mock data. This direct connection removes the guesswork from your development. You get exact field names, data types, and image URL formats written directly into your active files.

Query the Met Museum MCP Server in Agent Mode

The `search_objects` tool finds artwork IDs matching your specific queries directly from your editor. Cursor uses this tool to build test suites or populate local databases with real museum records. This MCP Server allows your agent to run searches, collect IDs, and write the output straight into your project files. It eliminates context switching entirely while you build art-focused applications.

Map department structures inside your editor

The `list_departments` tool outputs the full list of valid museum departments and their corresponding IDs. Cursor reads this raw data to validate your application's filtering logic during development. By calling `list_objects` alongside this tool, your agent verifies that your queries target active categories. You write clean, error-free integration code on the first try.

Setup guide

Set up Met Museum MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the Met Museum MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent Met Museum transactions." If the MCP tools are loaded correctly, Cursor will call the Met Museum tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "met-museum-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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 Cursor

Yes, the server exposes tools like `get_object` and `search_objects` to fetch live data. Cursor uses these responses to write accurate, production-ready code.

The server routes requests through Vinkius's managed infrastructure to handle connection stability. Your agent calls `list_objects` through this MCP integration without hitting local blockages.

No, your agent uses `search_objects` directly to find items. It writes the resulting JSON payloads straight into your workspace files.

You ask Cursor to run `list_departments`. The agent returns the raw IDs so you can hardcode or map them in your configuration files.

No, only specific search parameters and object IDs are transmitted to fetch the public metadata. Your local codebase and workspace configurations never leave your machine.

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