Master MCP Aggregator

Master MCP Aggregator (goldensuite-mcp)

goldensuite-mcp is a Python package that imports each Suite sub-package's MCP tool list and dispatcher and composes them into one mcp.server.Server. You point an MCP client at one endpoint and get the full Golden Suite — entity resolution, data quality scanning, transforms, pipeline orchestration, schema mapping.

Install

pip install goldensuite-mcp
goldensuite-mcp serve --transport http --port 8300

Or via the published container:

docker run -p 8300:8300 ghcr.io/benzsevern/goldensuite-mcp:latest

Tool collisions: first-wins

Tool names register on a first-wins basis. Registration order:

1. goldenmatch — entity resolution (headline package; its tools win collisions)
2. goldencheck — data quality scanning
3. goldenflow — transforms & standardizers
4. goldenpipe — pipeline orchestrator
5. infermap — schema mapping

If two packages register a tool with the same name, the later one is shadowed. Shadowed tools are logged at WARNING level when the server starts, so deployers can see exactly what happened:

WARNING goldensuite_mcp.server: tool collision: 'profile' from goldenflow shadowed by earlier goldencheck (first-wins)

If you need a shadowed tool, use that package's standalone MCP server instead.

Architecture

                 ┌──────────────────────────────────────────┐
                 │   goldensuite-mcp Server                  │
                 │   (one mcp.server.Server instance)        │
                 └─────────────┬────────────────────────────┘
                               │ aggregates
        ┌──────────────────────┼──────────────────────┐
        ▼                      ▼                      ▼
   goldenmatch.mcp       goldencheck.mcp        goldenflow.mcp     ...
   TOOLS + dispatch      TOOLS + dispatch       TOOLS + handle_tool

Each sub-package exposes its TOOLS list and a dispatcher at module scope (goldenmatch.mcp.server.dispatch, goldencheck.mcp.server._TOOL_HANDLERS, etc.). The aggregator imports those, normalizes Tool format (some are Tool objects, some are dicts), and binds tool names to the right dispatcher.

No subprocess overhead, no IPC. All tool calls execute in-process.

Standalone vs aggregator

Use case	Recommend
Need only one Suite package's tools	<package> mcp-serve (standalone)
Want everything in one MCP endpoint	goldensuite-mcp serve
Care about tool collisions	Read the WARNING logs at startup, or use standalone
Need different versions of sub-packages on different endpoints	Use standalone

Claude Desktop / Claude Code config

{
  "mcpServers": {
    "goldensuite": {
      "command": "goldensuite-mcp",
      "args": ["serve"]
    }
  }
}

Source

packages/python/goldensuite-mcp/