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 CrewAI?
When paired with CrewAI, Smithsonian Open Access becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Smithsonian Open Access tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Smithsonian Open Access in CrewAI
Smithsonian Open Access and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Smithsonian Open Access to CrewAI 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 CrewAI
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 CrewAI 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 CrewAI
Every tool call from CrewAI 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.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.
Explore More MCP Servers
View all →
VineRadar
6 toolsSearch wine and vineyards — audit varietals and vintages via AI.

IPRoyal (Proxy Services)
10 toolsManage proxies via IPRoyal — monitor traffic, rotate credentials, and manage whitelisted IPs.

Stadia Maps
10 toolsEquip your AI with advanced geospatial routing and mapping logic. Calculate distances, geocode coordinates, and plot optimized trips securely.

Taboola
10 toolsManage Taboola advertising campaigns, ads, and performance reports directly from any AI agent.
