Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Chainweb HTTP API: local sim, pre-signed send, poll, table reads, SPV proofs, module deploys.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
PACT_COMMUNITY_WORKSPACE_ROOT, PACT_COMMUNITY_CHAINWEB_MODE, PACT_COMMUNITY_CHAINWEB_PROFILE, PACT_COMMUNITY_CHAINWEB_BASE_URL, PACT_COMMUNITY_CHAINWEB_NETWORK_IDYou need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"chainweb": {
"command": "npx",
"args": [
"-y",
"@pact-community/mcp-chainweb"
],
"env": {
"PACT_COMMUNITY_WORKSPACE_ROOT": "your-value",
"PACT_COMMUNITY_CHAINWEB_MODE": "your-value",
"PACT_COMMUNITY_CHAINWEB_PROFILE": "your-value",
"PACT_COMMUNITY_CHAINWEB_BASE_URL": "your-value",
"PACT_COMMUNITY_CHAINWEB_NETWORK_ID": "your-value"
}
}
}
}Run this in your terminal
claude mcp add chainweb --env PACT_COMMUNITY_WORKSPACE_ROOT=your-value --env PACT_COMMUNITY_CHAINWEB_MODE=your-value --env PACT_COMMUNITY_CHAINWEB_PROFILE=your-value --env PACT_COMMUNITY_CHAINWEB_BASE_URL=your-value --env PACT_COMMUNITY_CHAINWEB_NETWORK_ID=your-value -- npx -y @pact-community/mcp-chainwebFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"chainweb": {
"command": "npx",
"args": [
"-y",
"@pact-community/mcp-chainweb"
],
"env": {
"PACT_COMMUNITY_WORKSPACE_ROOT": "your-value",
"PACT_COMMUNITY_CHAINWEB_MODE": "your-value",
"PACT_COMMUNITY_CHAINWEB_PROFILE": "your-value",
"PACT_COMMUNITY_CHAINWEB_BASE_URL": "your-value",
"PACT_COMMUNITY_CHAINWEB_NETWORK_ID": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"chainweb": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@pact-community/mcp-chainweb"
],
"env": {
"PACT_COMMUNITY_WORKSPACE_ROOT": "your-value",
"PACT_COMMUNITY_CHAINWEB_MODE": "your-value",
"PACT_COMMUNITY_CHAINWEB_PROFILE": "your-value",
"PACT_COMMUNITY_CHAINWEB_BASE_URL": "your-value",
"PACT_COMMUNITY_CHAINWEB_NETWORK_ID": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
PACT_COMMUNITY_CHAINWEB_PROFILE envPACT_COMMUNITY_CHAINWEB_BASE_URL envPACT_COMMUNITY_CHAINWEB_NETWORK_ID envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account Pact-Community-Organization, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: PACT_COMMUNITY_WORKSPACE_ROOT, PACT_COMMUNITY_CHAINWEB_MODE
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.2.3) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, NexusWindows
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Windows computer use in the background: desktop apps driven without your mouse or keyboard.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Model Context Protocol servers that give your AI agent safe, auditable access to the Pact 5 development loop on Kadena Chainweb.
Run REPL tests, scan modules for critical language traps, estimate gas, and query or submit to Chainweb nodes — from Claude, Cursor, VS Code, or any MCP-compatible client. Every tool runs behind a strict, tested security baseline, and no tool ever touches a private key.
{
"mcpServers": { "pact": { "command": "npx", "args": ["-y", "@pact-community/mcp-pact"], "env": { "PACT_COMMUNITY_WORKSPACE_ROOT": "/path/to/your/project" } } } }
| Server | Install | Tools | What it does |
|---|---|---|---|
Pact Tooling — @pact-community/mcp-pact | 6 | REPL test runs, critical-trap scanning, gas estimation, interface diff, format checks | |
Chainweb API — @pact-community/mcp-chainweb | 11 | /local simulation, pre-signed /send, poll, table reads, SPV proofs, module deploys |
Both are listed in the official MCP registry as io.github.Pact-Community-Organization/pact and io.github.Pact-Community-Organization/chainweb.
Using VS Code with GitHub Copilot? Install with a single click:
The button opens VS Code and pre-fills the configuration. You can also search the MCP Servers view, or add from the command line:
code --add-mcp '{"name":"pact","command":"npx","args":["-y","@pact-community/mcp-pact"],"env":{"PACT_COMMUNITY_WORKSPACE_ROOT":"${workspaceFolder}","PACT_COMMUNITY_PACT_BIN":"pact"}}'
On VS Code Insiders, use
vscode-insiders:in the links orcode-insiderson
the command line.
claude mcp add pact -e PACT_COMMUNITY_WORKSPACE_ROOT=/path/to/your/project \
-- npx -y @pact-community/mcp-pact
Add both servers to your client configuration:
{
"mcpServers": { "pact": { "command": "npx", "args": ["-y", "@pact-community/mcp-pact"], "env": { "PACT_COMMUNITY_WORKSPACE_ROOT": "/path/to/your/project", "PACT_COMMUNITY_PACT_BIN": "pact" } }, "chainweb": { "command": "npx", "args": ["-y", "@pact-community/mcp-chainweb"], "env": { "PACT_COMMUNITY_WORKSPACE_ROOT": "/path/to/your/project", "PACT_COMMUNITY_CHAINWEB_MODE": "devnet", "PACT_COMMUNITY_CHAINWEB_PROFILE": "devnet", "PACT_COMMUNITY_CHAINWEB_BASE_URL": "http://localhost:8081", "PACT_COMMUNITY_CHAINWEB_NETWORK_ID": "development" } } } }
Each server's README documents its full tool list and environment variables: Pact Tooling · Chainweb API.
pact on your PATH, and verify with pact --version.PACT_COMMUNITY_WORKSPACE_ROOT at your contract project.contracts/token.pact for critical Pact 5 traps"* — flags non-binary +, DB reads inside enforce, built-in shadowing, and more.tests/token.repl and summarize the failures"* — executes the file with the real Pact interpreter and parses the results.token.pact against token-v2.pact"* — reports added/removed/changed functions and whether the change is breaking.Everything in Pact Tooling works with just the CLI — no node required. Chainweb API works against any Chainweb-compatible node: point PACT_COMMUNITY_CHAINWEB_BASE_URL at your devnet, or use the read-only testnet06 / mainnet profiles to query public networks.
Both servers enforce the same tested baseline (details in SECURITY.md):
chainweb_send, chainweb_deploy_module, and chainweb_continue_pact require transactions to be signed externally (Ledger, @kadena/client, …) and passed in pre-signed.testnet06 and mainnet profiles block every write tool with PROFILE_WRITE_BLOCKED.| Server | Local devnet | Testnet | Mainnet |
|---|---|---|---|
| Pact Tooling | ✅ | — | — |
| Chainweb API | ✅ | ✅ read-only | ✅ read-only |
git clone https://github.com/Pact-Community-Organization/pact-mcp.git
cd pact-mcp pnpm install pnpm build pnpm test
Requires Node.js >= 20.11 and pnpm >= 9. See CONTRIBUTING.md for workflow, coding standards, and how to add or change a tool.
Apache-2.0