Smithsonian Open Access▌
by molanojustin
Access Smithsonian Open Access API to explore 3+ million objects from museums like the Smithsonian Design Museum and NMN
Provides access to the Smithsonian Institution's Open Access collections through their API, enabling search across 3+ million cultural objects from museums like NMNH, NPG, and SAAM with filters for object type, creator, materials, and licensing status, plus detailed object retrieval with metadata, images, and 3D models.
Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.
best for
- / Researchers studying cultural history and artifacts
- / Educators creating museum-based lesson content
- / Developers building cultural heritage applications
- / Art historians analyzing Smithsonian collections
capabilities
- / Search across 3+ million Smithsonian collection objects
- / Filter by object type, creator, materials, and licensing status
- / Retrieve detailed object metadata and descriptions
- / Access high-resolution images and 3D models
- / Browse collections from multiple Smithsonian museums
- / Query cultural and historical artifacts
what it does
Search and retrieve cultural artifacts, artworks, and museum objects from the Smithsonian Institution's 3+ million item Open Access collection. Get detailed metadata, images, and 3D models from museums like NMNH, NPG, and SAAM.
about
Smithsonian Open Access is a community-built MCP server published by molanojustin that provides AI assistants with tools and capabilities via the Model Context Protocol. Access Smithsonian Open Access API to explore 3+ million objects from museums like the Smithsonian Design Museum and NMN It is categorized under analytics data.
how to install
You can install Smithsonian Open Access in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
license
MIT
Smithsonian Open Access is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
readme
Smithsonian Open Access MCP Server
A Model Context Protocol (MCP) server that provides AI assistants with access to the Smithsonian Institution's Open Access collections. This server allows AI tools like Claude Desktop to search, explore, and analyze over 3 million collection objects from America's national museums.
Quick Start
Option 1: npm/npx Installation (Easiest)
The npm package includes automatic Python dependency management and works across platforms:
# Install globally
npm install -g @molanojustin/smithsonian-mcp
# Or run directly with npx (no installation needed)
npx -y @molanojustin/smithsonian-mcp
# Set your API key
export SMITHSONIAN_API_KEY=your_key_here
# Start the server
smithsonian-mcp
Option 2: Automated Setup (Recommended for Python users)
The enhanced setup script now includes:
- ✅ API key validation - Tests your key before saving
- ✅ Service installation - Auto-install as system service
- ✅ Claude Desktop config - Automatic configuration
- ✅ Health checks - Verify everything works macOS/Linux:
chmod +x config/setup.sh
config/setup.sh
Windows:
config\setup.ps1
Option 3: Manual Setup
- Get API Key: api.data.gov/signup (free)
- Install:
uv pip install -r config/requirements.txt - Configure: Copy
.env.exampleto.envand set your API key - Test:
python examples/test-api-connection.py
Verify Setup
Run the verification script to check your installation:
python scripts/verify-setup.py
Features
Core Functionality
- Search Collections: 3+ million objects across 24 Smithsonian museums
- Object Details: Complete metadata, descriptions, and provenance
- On-View Status - Find objects currently on physical exhibit
- Image Access: High-resolution images (CC0 licensed when available)
- Museum Information: Browse all Smithsonian institutions
- Collection Statistics: Comprehensive metrics with per-museum breakdowns (sampling-based estimates)
AI Integration
- 16 MCP Tools: Smart discovery, comprehensive search, museum-specific queries, exhibition status, contextual data access, and proactive collection type discovery
- Proactive Discovery: New tools help AI assistants understand API scope and available object types before searching, preventing confusion about archival vs. museum materials
- Smart Context: Contextual data sources for AI assistants including enhanced statistics
- Rich Metadata: Complete object information and exhibition details
- Exhibition Planning - Tools to find and explore currently exhibited objects
- Collection Analytics: Per-museum statistics with sampling-based accuracy
- Multi-Model Compatible: Works well with both advanced and simpler AI models through simplified tool interfaces
URL Validation & Anti-Guessing
- Easiest Solution: Use
search_and_get_first_url()for one-step search + validated URL retrieval - Mandatory Tool Usage: LLM must use
get_object_url()tool for any URL retrieval - manual construction fails due to case sensitivity - Flexible Identifiers: Supports Accession Numbers (F1900.47), Record IDs (fsg_F1900.47), and Internal IDs (ld1-...)
- URL Validation: Automatically selects authoritative record_link over API identifiers, handles case sensitivity
Integration
Claude Desktop
Option 1: Using npm/npx (Recommended)
- Configure (
claude_desktop_config.json):
{
"mcpServers": {
"smithsonian_open_access": {
"command": "npx",
"args": ["-y", "@molanojustin/smithsonian-mcp"],
"env": {
"SMITHSONIAN_API_KEY": "your_key_here"
}
}
}
}
Option 2: Using Python installation
- Configure (
claude_desktop_config.json):
{
"mcpServers": {
"smithsonian_open_access": {
"command": "python",
"args": ["-m", "smithsonian_mcp.server"],
"env": {
"SMITHSONIAN_API_KEY": "your_key_here"
}
}
}
}
- Test: Ask Claude "What Smithsonian museums are available?"
mcpo Integration (MCP Orchestrator)
mcpo is an MCP orchestrator that converts multiple MCP servers into OpenAPI/HTTP endpoints, ideal for combining multiple services into a single systemd service.
Installation
# Install mcpo
uvx mcpo
# Or using uvx
uvx mcpo --help
Configuration
Create a examples/mcpo-config.json file:
{
"mcpServers": {
"smithsonian_open_access": {
"command": "python",
"args": ["-m", "smithsonian_mcp.main"],
"env": {
"SMITHSONIAN_API_KEY": "your_api_key_here"
}
},
"memory": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-memory"]
},
"time": {
"command": "uvx",
"args": ["mcp-server-time", "--local-timezone=America/New_York"]
}
}
}
Running with mcpo
# Start mcpo with hot-reload
mcpo --config examples/mcpo-config.json --port 8000 --hot-reload
# With API key authentication
mcpo --config examples/mcpo-config.json --port 8000 --api-key "your_secret_key"
# Access endpoints:
# - Smithsonian: http://localhost:8000/smithsonian_open_access
# - Memory: http://localhost:8000/memory
# - Time: http://localhost:8000/time
# - API docs: http://localhost:8000/docs
Systemd Service
Create /etc/systemd/system/mcpo.service:
[Unit]
Description=MCP Orchestrator Service
After=network.target
[Service]
Type=simple
User=your-user
WorkingDirectory=/path/to/your/config
Environment=PATH=/path/to/venv/bin
ExecStart=/path/to/venv/bin/mcpo --config examples/mcpo-config.json --port 8000
Restart=always
RestartSec=10
[Install]
WantedBy=multi-user.target
# Enable and start service
sudo systemctl enable mcpo
sudo systemctl start mcpo
sudo systemctl status mcpo
Troubleshooting mcpo
See TROUBLESHOOTING.md for detailed mcpo troubleshooting, including:
- ModuleNotFoundError solutions
- Connection closed errors
- Port conflicts
- Path configuration issues
VS Code
- Open Workspace:
code .vscode/smithsonian-mcp-workspace.code-workspace - Run Tasks: Debug, test, and develop the MCP server
- Claude Code: AI-assisted development with Smithsonian data
Available Data
- 19 Museums: NMNH, NPG, SAAM, NASM, NMAH, and more
- 3+ Million Objects: Digitized collection items
- CC0 Content: Public domain materials for commercial use
- Rich Metadata: Creators, dates, materials, dimensions
- High-Resolution Images: Professional photography
Data Accuracy & Sampling
Collection statistics for objects with images use sampling methodology to provide accurate estimates:
- Sample Size: Up to 1000 objects per query for statistical significance
- Methodology: Counts actual returned objects instead of relying on potentially buggy API totals
- Coverage: Includes per-museum breakdowns with individual sampling for each institution
- Transparency: All sampled counts are clearly marked as "(est.)" in outputs
This approach ensures reliable metrics while respecting API rate limits and avoiding the Smithsonian API's rowCount filtering bug.
Current API Limitations
Image URLs Not Available: The Smithsonian Open Access API currently does not provide image URLs or media data in detailed content responses. While the search API can filter objects by media type (e.g., online_media_type:Images), the actual image URLs are not included in the detailed object data returned by the content API. This appears to be a change in the API since the available documentation was published.
- Objects will show as having 0 images even when filtered for image content
- Image statistics are estimates based on search filtering, not actual media availability
- The system gracefully handles this limitation and continues to provide all other metadata
API Scope: Diverse Museum Collections: The Smithsonian Open Access API provides access to diverse collections across 24 Smithsonian museums, with each museum having distinct object types reflecting their unique focus areas. The discovery tools now correctly identify museum-specific collections with comprehensive object type intelligence gathered through systematic sampling.
- SAAM (American Art): Paintings, decorative arts, sculptures, drawings
- NASM (Air & Space): Aircraft, avionics, spacecraft, aviation equipment
- NMAH (American History): Historical artifacts, inventions, cultural objects
- CHNDM (Design Museum): Design objects, textiles, furniture, graphics
- Use discovery tools (
get_museum_collection_types,check_museum_has_object_type) to explore available collections - Each museum's collection reflects its institutional mission and expertise
MCP Tools
Search & Discovery
simple_explore- Smart diverse sampling across museums and object types (recommended for general discovery)continue_explore- Get more results about the same topic while avoiding duplicatessearch_collections- Advanced search with filters (prioritizes museum-specific results when unit_code specified)search_and_get_first_url- Easiest option: Search and get validated URL in one step (prevents manual URL construction)get_object_details- Detailed object informationget_object_url- Get validated object URLs with flexible identifier support (MANDATORY: never construct URLs manually)- `
FAQ
- What is the Smithsonian Open Access MCP server?
- Smithsonian Open Access is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for Smithsonian Open Access?
- This profile displays 53 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.7 out of 5—verify behavior in your own environment before production use.
Use Cases▌
Extended AI Capabilities
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Context Enhancement
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Workflow Automation
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Implementation Guide▌
Prerequisites
- ›Claude Desktop 0.7.0+ or Cursor IDE with MCP support
- ›Basic understanding of MCP architecture and capabilities
- ›Access credentials for integrated services (if required)
- ›Willingness to experiment and iterate on configuration
Time Estimate
15-60 minutes depending on server complexity
Installation Steps
- 1.Install MCP server: npm install -g [package-name] or via GitHub
- 2.Add server configuration to ~/.claude/mcp.json
- 3.Provide required credentials and configuration
- 4.Restart Claude Desktop to load new server
- 5.Test basic functionality with simple prompts
- 6.Explore capabilities and experiment with use cases
- 7.Document successful patterns for reuse
Troubleshooting
- ⚠MCP server not loading: Check config syntax, verify installation
- ⚠Connection errors: Check network, firewall, credentials
- ⚠Feature not working: Read server docs, check required parameters
- ⚠Performance issues: Monitor resource usage, check for network latency
- ⚠Conflicts with other servers: Check port assignments, namespace collisions
Best Practices▌
✓ Do
- +Read server documentation thoroughly before setup
- +Start with simple use cases to validate functionality
- +Test in non-production environment first
- +Monitor resource usage and performance
- +Keep servers updated for bug fixes and new features
- +Document configuration for team members
- +Use environment variables for sensitive configuration
✗ Don't
- −Don't grant overly permissive access to MCP servers
- −Don't skip reading security considerations in docs
- −Don't expose sensitive data without proper controls
- −Don't run untrusted MCP servers without code review
- −Don't ignore error messages—investigate root cause
💡 Pro Tips
- ★Combine multiple MCP servers for powerful workflows
- ★Create custom MCP servers for your specific needs
- ★Share successful configurations with team
- ★Use MCP inspector for debugging
- ★Join MCP community for tips and troubleshooting
Technical Details▌
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
- Model Context Protocol (MCP)
- JSON-RPC 2.0
- stdio or HTTP transport
Compatibility
- Claude Desktop
- Cursor IDE
- Custom MCP clients
When to Use This▌
✓ Use When
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid When
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.
Integration▌
- →Tool composition: Chain multiple MCP tools in workflows
- →Context augmentation: Provide AI with relevant external data
- →Action delegation: Let AI execute tasks on external systems
- →Bidirectional sync: Keep AI context and external systems in sync
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
List & Promote Your MCP Server
Share your MCP server with the developer community
Ratings
4.7★★★★★53 reviews- ★★★★★Amina Ramirez· Dec 16, 2024
Smithsonian Open Access is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
- ★★★★★Isabella Sharma· Dec 12, 2024
I recommend Smithsonian Open Access for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★Kabir Gonzalez· Dec 4, 2024
We wired Smithsonian Open Access into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
- ★★★★★Amina Sanchez· Nov 27, 2024
According to our notes, Smithsonian Open Access benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Olivia Sethi· Nov 23, 2024
Smithsonian Open Access has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Chinedu Farah· Nov 23, 2024
Smithsonian Open Access reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Tariq Flores· Nov 7, 2024
Useful MCP listing: Smithsonian Open Access is the kind of server we cite when onboarding engineers to host + tool permissions.
- ★★★★★Isabella Abebe· Nov 3, 2024
We evaluated Smithsonian Open Access against two servers with overlapping tools; this profile had the clearer scope statement.
- ★★★★★Amina Bansal· Oct 26, 2024
Smithsonian Open Access reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Aditi Tandon· Oct 22, 2024
Smithsonian Open Access is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
showing 1-10 of 53