Harvard Art vs Url

A side-by-side look at the Harvard Art and Url MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Harvard Art logoHarvard ArtArt & Culture · Local subprocess (stdio)Harvard Art Museums MCP.51GoodAuth: not declaredUrl logoUrlDeveloper Tools · Local subprocess (stdio)URL parsing & building MCP.49FairAuth: not declared

Verdict: choose Harvard Art for art & culture work as a local process; choose Url for developer tools as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Harvard Art logoChoose Harvard Art when

  • You need dedicated capabilities in the Art & Culture domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like search, object.
Explore Harvard Art

Url logoChoose Url when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like parse_url, build_url, parse_query.
Explore Url

Feature & specification comparison

Rows where the two servers differ are marked.

SpecHarvard Art logoHarvard ArtUrl logoUrl
CategoryArt & CultureDeveloper Tools
Quality signal51/100 · Good49/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars20
Directory activity 2 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
Tools23

Tools & capabilities

Harvard Art tools 2

  • searchSearch the Harvard Art Museums collection by keyword. Returns matching items with ids (pass an id to object), titles, creators, dates and image links.
  • objectFetch full details for one Harvard Art Museums item by id — a Harvard Art Museums object id (numeric, from search).

Url tools 3

  • parse_urlParse a URL into its components (keyless, offline): protocol, host, hostname, port, path, query (as an object), fragment, origin, and any userinfo.
  • build_urlBuild a URL string from components. Provide at least `hostname` (and optionally protocol, port, path, hash) plus a `query` object of key/value pairs.
  • parse_queryParse a query string (with or without a leading "?") into an object; repeated keys become arrays.

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.

Harvard Art

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "harvard-art": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-harvard-art"
      ]
    }
  }
}

Url

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "url": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-url"
      ]
    }
  }
}

Frequently asked questions

Harvard Art is categorized under Art & Culture and uses a local stdio subprocess. Url belongs to Developer Tools and uses a local stdio subprocess. Pick Harvard Art for art & culture work and Url for developer tools.

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.

Harvard Art has no declared pricing — check the project's own site. Url 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 harvard-art and url as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Harvard Art has a quality signal of 51/100 (Good) with 2 views, 0 installs and 2 GitHub stars. Url has 49/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.