Open Museum MCP vs Electron.dance
A side-by-side look at the Open Museum MCP and Electron.dance MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Open Museum MCP for art & culture work as a local process; choose Electron.dance for art & culture. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Open Museum MCP when
- You need dedicated capabilities in the Art & Culture domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
Choose Electron.dance when
- You need dedicated capabilities in the Art & Culture domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Art & Culture | Art & Culture |
| Quality signal | 60/100 · Good | 33/100 · Emerging |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 13 | 0 |
| Directory activity | 4 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Open Museum MCP | View Electron.dance |
Tools & capabilities
Open Museum MCP tools
No tool names declared yet. Check the project README from the listing page.
Electron.dance tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Open Museum MCP
{
"mcpServers": {
"cfpramod-open-museum-mcp": {
"command": "npx",
"args": [
"-y",
"open-museum-mcp"
]
}
}
}
Electron.dance
No confirmed install command for Electron.dance yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Open Museum MCP is categorized under Art & Culture and uses a local stdio subprocess. Electron.dance belongs to Art & Culture and uses an install path we have not confirmed yet. Pick Open Museum MCP for art & culture work and Electron.dance for art & culture.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Electron.dance has no confirmed install command yet — follow its own setup instructions.
Open Museum MCP is listed as free. Auth: api key required. Electron.dance has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add cfpramod-open-museum-mcp and electron-dance as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Open Museum MCP has a quality signal of 60/100 (Good) with 4 views, 0 installs and 13 GitHub stars. Electron.dance has 33/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars.