In-depth architectural comparison of the Gramps Web MCP and Getabrain 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.
At a Glance & Executive Verdict
Gramps Web MCP
Research · Remote HTTP/SSE
Quality: 43/100 (Fair) | Auth: other
Getabrain MCP Server
Research · Local stdio
Quality: 64/100 (Good) | Auth: API Key required
Verdict Summary: Choose Gramps Web MCP if you need specialized Research tools running via a hosted cloud SSE transport. Choose Getabrain MCP Server if your workspace requires Research integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Gramps Web MCP when:
You need dedicated capabilities in the Research domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: other (Free / Open Source).
You have access to required keys: GRAMPS_API_URL, GRAMPS_USERNAME, GRAMPS_PASSWORD, GRAMPS_TREE_ID.
Primary tools included: 57 tools for genealogy records, Full-text search and paginated browsing, Ancestor, descendant, relationship, and timeline queries.
Gramps Web MCP is categorized under Research and uses a remote streaming HTTP/SSE transport. In contrast, Getabrain MCP Server belongs to Research using local stdio subprocess. Select Gramps Web MCP when you need capabilities focused on research and Getabrain MCP Server when you require tools for research.