MCP server
by molanojustin
Access Smithsonian Open Access API to explore 3+ million objects from museums like the Smithsonian Design Museum and NMN
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.
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.
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.
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.
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
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
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
Share your MCP server with the developer community
Smithsonian Open Access is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
I recommend Smithsonian Open Access for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
We wired Smithsonian Open Access into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
According to our notes, Smithsonian Open Access benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Smithsonian Open Access has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Smithsonian Open Access reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Useful MCP listing: Smithsonian Open Access is the kind of server we cite when onboarding engineers to host + tool permissions.
We evaluated Smithsonian Open Access against two servers with overlapping tools; this profile had the clearer scope statement.
Smithsonian Open Access reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
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
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.
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
The enhanced setup script now includes:
chmod +x config/setup.sh
config/setup.sh
Windows:
config\setup.ps1
uv pip install -r config/requirements.txt.env.example to .env and set your API keypython examples/test-api-connection.pyRun the verification script to check your installation:
python scripts/verify-setup.py
search_and_get_first_url() for one-step search + validated URL retrievalget_object_url() tool for any URL retrieval - manual construction fails due to case sensitivityclaude_desktop_config.json):{
"mcpServers": {
"smithsonian_open_access": {
"command": "npx",
"args": ["-y", "@molanojustin/smithsonian-mcp"],
"env": {
"SMITHSONIAN_API_KEY": "your_key_here"
}
}
}
}
claude_desktop_config.json):{
"mcpServers": {
"smithsonian_open_access": {
"command": "python",
"args": ["-m", "smithsonian_mcp.server"],
"env": {
"SMITHSONIAN_API_KEY": "your_key_here"
}
}
}
}
mcpo is an MCP orchestrator that converts multiple MCP servers into OpenAPI/HTTP endpoints, ideal for combining multiple services into a single systemd service.
# Install mcpo
uvx mcpo
# Or using uvx
uvx mcpo --help
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"]
}
}
}
# 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
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
See TROUBLESHOOTING.md for detailed mcpo troubleshooting, including:
code .vscode/smithsonian-mcp-workspace.code-workspaceCollection statistics for objects with images use sampling methodology to provide accurate estimates:
This approach ensures reliable metrics while respecting API rate limits and avoiding the Smithsonian API's rowCount filtering bug.
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.
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.
get_museum_collection_types, check_museum_has_object_type) to explore available collectionssimple_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)Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ 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.