Bring Museum Records
to Cursor
Learn how to connect Smithsonian Open Access to Cursor and start using 3 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Smithsonian Open Access MCP Server?
Connect to the Smithsonian Open Access repository and bring millions of museum records, scientific data, and historical artifacts directly into your AI workspace. This server provides programmatic access to the Smithsonian's Enterprise Digital Asset Network (EDAN).
What you can do
- Global Search — Query millions of records across all Smithsonian units using the
search_recordstool to find images, specimens, and artifacts. - Detailed Metadata — Use
get_contentto retrieve comprehensive descriptions, provenance, and digital asset links for specific museum objects. - Categorized Discovery — Narrow your research to specific fields like art, history, or science using the
search_categorytool for more precise results. - Research & Education — Instantly pull primary source data for academic research, educational content, or creative projects.
How it works
- Subscribe to this server
- Enter your Smithsonian API Key
- Start exploring the world's largest museum, education, and research complex through Claude, Cursor, or any MCP client
Who is this for?
- Researchers & Academics — quickly gather metadata and primary source information for scholarly work
- Educators — find high-quality museum records and images to enhance learning materials
- Developers & Creatives — integrate authentic historical and scientific data into applications and digital experiences
Built-in capabilities (3)
Retrieve a specific museum record by its unique identifier
Search within specific categories or units
Search for museum records across all Smithsonian units
Why Cursor?
Cursor's Agent mode turns Smithsonian Open Access into an in-editor superpower. Ask Cursor to generate code using live data from Smithsonian Open Access and it fetches, processes, and writes. all in a single agentic loop. 3 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Smithsonian Open Access in Cursor
Smithsonian Open Access and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Smithsonian Open Access to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Smithsonian Open Access in Cursor
The Smithsonian Open Access MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 3 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Smithsonian Open Access for Cursor
Every tool call from Cursor to the Smithsonian Open Access MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I search for specific historical figures across all Smithsonian museums?
Yes! Use the search_records tool with your query (e.g., 'Abraham Lincoln'). It will return matching records, images, and artifacts from across all Smithsonian units.
How do I get the full metadata for a specific museum object?
Use the get_content tool with the unique identifier (ID) of the record. This will fetch detailed metadata, including descriptions, dates, and media links.
Is it possible to limit my search to just art or science categories?
Yes, the search_category tool allows you to specify a category (like 'art', 'history', or 'science') along with your search query to get more targeted results.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
GitScrum
16 toolsManage workspaces, projects, workflows, and labels via GitScrum — browse your organizational structure and configure boards directly from any AI agent.
Steam Economy & Market Intelligence
8 toolsThe definitive server for Steam assets — track skin prices, inventory values, and market trends via AI.
WhoisXML
4 toolsAccess comprehensive domain intelligence, WHOIS records, IP geolocation, and email verification directly from your AI agent.
Deep Diff Engine
1 toolsFind every single change between two JSON objects — additions, deletions, and edits with exact structural paths. Stop relying on AI to 'spot the difference'.