Compatible with every major AI agent and IDE
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 VS Code Copilot?
GitHub Copilot Agent mode brings Smithsonian Open Access data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 3 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Smithsonian Open Access in VS Code Copilot
Smithsonian Open Access and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Smithsonian Open Access to VS Code Copilot 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 VS Code Copilot
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 VS Code Copilot 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 VS Code Copilot
Every tool call from VS Code Copilot 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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
EmojisWorld
3 toolsUniversal emoji intelligence — search emojis, list categories, and get random icons via AI.

SMS Masivo
10 toolsSend bulk SMS campaigns across Latin America with delivery tracking, contact segmentation, and competitive local pricing.

Callpicker
9 toolsTrack and analyze inbound calls with attribution data that shows which marketing channels drive your best phone leads.

MediaSilo (Legacy)
11 toolsShare and review video content with creative teams using secure media workspaces, annotations, and approval workflows.
