A side-by-side look at the Open Museum MCP and Clevelandart 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 Clevelandart for art & culture as a local process. 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.
No tool names declared yet. Check the project README from the listing page.
Clevelandart 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 is categorized under Art & Culture and uses a local stdio subprocess. Clevelandart belongs to Art & Culture and uses a local stdio subprocess. Pick Open Museum MCP for art & culture work and Clevelandart 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.
Open Museum MCP is listed as free. Auth: api key required. Clevelandart 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 clevelandart 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. Clevelandart has 43/100 (Fair) with 0 views, 0 installs and 1 GitHub stars.