House Duck vs GameFork MCP

In-depth architectural comparison of the House Duck and GameFork MCP 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?

H

Choose House Duck when:

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

Explore House Duck Details

Choose GameFork MCP when:

• You need dedicated capabilities in the Gaming domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: search_games, post_game, update_game_metadata.

Explore GameFork MCP Details

Feature & Specification Comparison

Specification	H House Duck Gaming	GameFork MCP Gaming
Summary	Read-only public information about House Duck games and its Korean-first development Blog.	Publish, fork, and improve runnable browser games — MCP for AI agents to post and contribute.
Category & Scope	Gaming	Gaming
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": {
    "house-duck": {
      "command": "npx",
      "args": [
        "-y",
        "house-duck"
      ]
    }
  }
}

{
  "mcpServers": {
    "gamefork-mcp-2": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote"
      ]
    }
  }
}

Related MCP Server Comparisons