OpenHeritage Public Search vs Rpf

In-depth architectural comparison of the OpenHeritage Public Search and Rpf 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 OpenHeritage Public Search 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 OpenHeritage Public Search Details

Choose Rpf 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 Rpf Details

Feature & Specification Comparison

Specification	OpenHeritage Public Search Developer Tools	Rpf Developer Tools
Summary	Public search of genealogy, archives, photos, memorials, cemeteries, research, and repositories.	Read and write RAGE Package Format archives
Category & Scope	Developer Tools	Developer Tools
Quality signal

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": {
    "openheritage-public-search": {
      "command": "npx",
      "args": [
        "-y",
        "skills"
      ]
    }
  }
}

{
  "mcpServers": {
    "rpf": {
      "command": "npx",
      "args": [
        "-y",
        "rpf"
      ]
    }
  }
}

Related MCP Server Comparisons