Google Workspace MCP vs Met Museum MCP Server

In-depth architectural comparison of the Google Workspace MCP and Met Museum MCP Server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Google Workspace MCP when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Google Workspace MCP Details

Choose Met Museum MCP Server when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Met Museum MCP Server Details

Feature & Specification Comparison

Specification	Google Workspace MCP Developer Tools	Met Museum MCP Server Developer Tools
Summary	Google Workspace Admin via MCP. Manage users, groups, aliases, org units.	MET Museum collection via MCP — 500K+ artworks, metadata, provenance, open-access images.
Category & Scope	Developer Tools	Developer Tools

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "google-workspace-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/inspector"
      ]
    }
  }
}

{
  "mcpServers": {
    "met-museum-mcp-server": {
      "command": "bunx",
      "args": [
        "@cyanheads/met-museum-mcp-server@latest"
      ]
    }
  }
}

Related MCP Server Comparisons