swagger-contract-testing vs Pact Tooling
swagger-contract-testing is a plugin bundle for AI coding tools published by pactflow. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Pact Tooling is an MCP server published by Pact-Community-Organization. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  swagger-contract-testing |  Pact Tooling |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.1.0 Forks (GitHub): 4 Stars (GitHub): 7 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.2 Downloads/month (npm): 134 Downloads/week (npm): 30 Forks (GitHub): 3 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | swagger-contract-testing | Pact Tooling |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 7 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 4 (better) | 3 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@smartbear/mcp) | On your machine (@pact-community/mcp-pact) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | 2, secrets among them: 0 |
| Hooks it runs (differs) | 2 | Not published |
| Parts of the bundle (differs) | 11 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/pactflow/pactflow-agent-skills | github.com/pact-community-organization/pact-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
swagger-contract-testing
AI assistant skills and agents for PactFlow contract testing. Covers the full contract testing lifecycle — from writing and reviewing Pact consumer/provider tests to publishing contracts, running can-i-deploy checks, and managing your PactFlow workspace. Includes: - PactFlow skill — expert assistant for Pact and PactFlow; uses the SmartBear MCP server to generate and review tests with AI, publish contracts, verify providers, record deployments, and manage environments, webhooks, and secrets. - Drift skill — expert assistant for Drift, PactFlow's OpenAPI contract testing CLI; helps write test cases, configure lifecycle hooks, debug failures, and publish results for Bi-Directional Contract Testing (BDCT). - OpenAPI Parser skill — parses complex OpenAPI specs (anyOf/oneOf/allOf, discriminators, $ref chains, enums, regex patterns) and generates comprehensive Drift test cases covering every schema combination. - Specialized agents — pact-generator (writes Pact tests from code or specs), pact-reviewer (audits tests
Pact Tooling
Pact 5 tooling: REPL test runs, trap scanning, gas estimation, interface diff, format checks.
How to run each
swagger-contract-testing As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install swagger-contract-testing@claude-communityPact Tooling As a local MCP server: npm package
claude mcp add --env "PACT_COMMUNITY_WORKSPACE_ROOT=<YOUR_PACT_COMMUNITY_WORKSPACE_ROOT>" --transport stdio pact -- npx -y @pact-community/mcp-pactRequires: PACT_COMMUNITY_WORKSPACE_ROOT
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only swagger-contract-testing asks for
PACT_BROKER_BASE_URLPACT_BROKER_TOKEN (secret)
Only Pact Tooling asks for
PACT_COMMUNITY_PACT_BINPACT_COMMUNITY_WORKSPACE_ROOT
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: swagger-contract-testing · What it can do: Pact Tooling · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.