Pact Tooling runs on your own machine — the client starts it, so there is no endpoint to ping. 41 installs a week from npm. Last commit 4 Oct 2026.
Pact 5 tooling: REPL test runs, trap scanning, gas estimation, interface diff, format checks.
What the code does
We read the source, 4 d ago · rules 995398eba69f
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.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
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 -e 'PACT_COMMUNITY_WORKSPACE_ROOT=<PACT_COMMUNITY_WORKSPACE_ROOT>' -- npx -y @pact-community/mcp-pact{
"mcpServers": {
"pact": {
"command": "npx",
"args": [
"-y",
"@pact-community/mcp-pact"
],
"env": {
"PACT_COMMUNITY_WORKSPACE_ROOT": "<PACT_COMMUNITY_WORKSPACE_ROOT>"
}
}
}
}[mcp_servers.pact]
command = "npx"
args = ["-y", "@pact-community/mcp-pact"]
env = { PACT_COMMUNITY_WORKSPACE_ROOT = "<PACT_COMMUNITY_WORKSPACE_ROOT>" }{
"mcpServers": {
"pact": {
"command": "npx",
"args": [
"-y",
"@pact-community/mcp-pact"
],
"env": {
"PACT_COMMUNITY_WORKSPACE_ROOT": "<PACT_COMMUNITY_WORKSPACE_ROOT>"
}
}
}
}{
"servers": {
"pact": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@pact-community/mcp-pact"
],
"env": {
"PACT_COMMUNITY_WORKSPACE_ROOT": "<PACT_COMMUNITY_WORKSPACE_ROOT>"
}
}
}
}Put your own value in place of
<PACT_COMMUNITY_WORKSPACE_ROOT> (Workspace root directory; all file access is confined inside it).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
PACT_COMMUNITY_PACT_BIN (Path to the pact binary (default: pact on PATH)).
Alternatives to Pact Tooling
same job, measured the same wayCheck, format, run and test Renyi programs; the project map with effects, diffs and chunks.
Translation QA: automated checks, AI evaluation, linguistic review, and visual in-context testing.
MCP server for API testing: HTTP requests, cURL generation, health checks.
Country verification research, integration planning and synthetic tests. No live identity checks.
Proves software work: triages failing tests, checks whether a test can fail, and reads migrations.
Guarded AI mobile Appium testing, security scanning, verification, and fix-retest MCP tools.
Desktop UI automation for AI agents: verified clicks, UI Automation, OCR, scenario runs, recording
Deployment-readiness checks for document-QA and extraction AI: grounding, extraction, CI gate.
Pact Tooling — questions
Answers built from our own checks of this server.