Metmuseum MCP vs SyncSo
A side-by-side look at the Metmuseum MCP and SyncSo MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Metmuseum MCP for art & culture work as a local process; choose SyncSo for art & culture over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Metmuseum MCP when
- You need dedicated capabilities in the Art & Culture domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
list-departments, search-museum-objects, get-museum-object.
Choose SyncSo when
- You need dedicated capabilities in the Art & Culture domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Art & Culture | Art & Culture |
| Quality signal | 64/100 · Good | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 35 | 2 |
| Directory activity | 7 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 4 | Not listed |
| Full listing | View Metmuseum MCP | View SyncSo |
Tools & capabilities
Metmuseum MCP tools 4
list-departmentsList all departments in the Metropolitan Museum of Art (Met Museum)search-museum-objectsSearch for objects in the Metropolitan Museum of Art (Met Museum). Will return Total objects found, followed by a paginated list of Object Ids. If the Met Explorer app (open-met-explorer) is open and the user is referring to its existing results, prefer using those results from context instead of calling this tool. The parameter title should be set to true if you want to search for objects by title. The parameter hasImages is false by default, but can be set to true to return only objects with images. Additional optional filters are available for highlights, tags, on-view status, artist/culture match, medium, geographic location, and date range. Use page and pageSize to paginate results.get-museum-objectGet a museum object by its ID, from the Metropolitan Museum of Art Collection. Use this when the user asks for deeper details on a specific object ID.open-met-explorerOpen the interactive Met Explorer app for browsing and filtering objects. For exploration intents, pass q so the app can run a live search on open. After opening, keep your chat handoff short and UI-focused. For deeper details on a specific object ID, prefer get-museum-object.
SyncSo 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.
Metmuseum MCP
{
"mcpServers": {
"mikechao-metmuseum-mcp": {
"command": "npx",
"args": [
"-y",
"metmuseum-mcp"
]
}
}
}
SyncSo
{
"mcpServers": {
"syncso": {
"url": "https://rtdb.syncso.com/partner/mcp"
}
}
}
Frequently asked questions
Metmuseum MCP is categorized under Art & Culture and uses a local stdio subprocess. SyncSo belongs to Art & Culture and uses a remote HTTP/SSE transport. Pick Metmuseum MCP for art & culture work and SyncSo 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.
Metmuseum MCP is listed as free. Auth: no auth required. SyncSo 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 mikechao-metmuseum-mcp and syncso as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Metmuseum MCP has a quality signal of 64/100 (Good) with 7 views, 0 installs and 35 GitHub stars. SyncSo has 41/100 (Fair) with 1 views, 0 installs and 2 GitHub stars.