Smithsonian MCP Server

Model Context Protocol (MCP) server for Smithsonian Open Access collections

Local serverstdioPython

What is the Smithsonian MCP MCP server?

Smithsonian MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Smithsonian MCP directly instead of describing what you should do. Model Context Protocol (MCP) server for Smithsonian Open Access collections.

What you get

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.

Setting it up

The server ships on npm as Installation, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What the assistant can call

Once Smithsonian MCP is connected, these are the calls the assistant has available:

  • Installation — The Installation tool exposed by this server
  • Configuration — The Configuration tool exposed by this server
  • Development — The Development tool exposed by this server
  • Windows — The Windows tool exposed by this server

Configuration and credentials

You will need one environment variable: SMITHSONIAN_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the smithsonian mcp mcp server does with a few real requests.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Smithsonian MCP's toolset — Installation, Configuration, Development and 1 more — is a fair guide to whether it matches your workflow. It is maintained by molanojustin; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Smithsonian MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
InstallationThe Installation tool exposed by this server.
ConfigurationThe Configuration tool exposed by this server.
DevelopmentThe Development tool exposed by this server.
WindowsThe Windows tool exposed by this server.

How to install the Smithsonian MCP MCP server

{
  "mcpServers": {
    "smithsonian_open_access": {
      "command": "npx",
      "args": ["-y", "@molanojustin/smithsonian-mcp"],
      "env": {
        "SMITHSONIAN_API_KEY": "your_key_here"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
SMITHSONIAN_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Smithsonian MCP to Installation.
  • Use Smithsonian MCP to Configuration.
  • Use Smithsonian MCP to Development.

Frequently asked questions

It connects Smithsonian MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (Installation, Configuration, Development, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Smithsonian MCP directly.