Pact Tooling MCP Server

What the code does

We read the source, 58 min ago · rules 3dff92dd89df

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    : path.join(workspaceRoot, candidate);

  for (const [key, value] of Object.entries(process.env)) {

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add pact -- npx -y @pact-community/mcp-pact

{
  "mcpServers": {
    "pact": {
      "args": [
        "-y",
        "@pact-community/mcp-pact"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.pact]
command = "npx"
args = ["-y", "@pact-community/mcp-pact"]

{
  "mcpServers": {
    "pact": {
      "args": [
        "-y",
        "@pact-community/mcp-pact"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "pact": {
      "args": [
        "-y",
        "@pact-community/mcp-pact"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: PACT_COMMUNITY_WORKSPACE_ROOT (Workspace root directory; all file access is confined inside it.), PACT_COMMUNITY_PACT_BIN (Path to the pact binary (default: pact on PATH).). The author declared them in the registry entry; get the values from the project itself.