Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
RevRule by Payload: read entitlement graphs, review payout evidence, dry-run revenue events.
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.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
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.
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.
These 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 7, 2026
The publisher (payload-tools) is not the repo owner (Payloadhq); someone else may have listed it
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 0 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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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 (1.1.0) reached the registry 22 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, LexPact UK Contracts
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.
Generate UK-law contracts: NDA, service, freelance, recruiter terms of business, IR35.
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.
An MCP server (stdio transport, Node.js standard library only, zero dependencies) that exposes RevRule, Payload's revenue-entitlement engine, to AI agents.
RevRule turns revenue sharing into declarative entitlement rules on the Payload rail: define who gets paid what, and every payout carries evidence linked back to the original entitlement ledger entry and its on-chain settlement. This server is a read + dry-run surface: there are deliberately no write/submit tools in v1. Every call goes to the live Payload rail (https://payload-rail.fly.dev) authenticated with your own rail API key (a free self-serve key from the console is enough to evaluate).
| Tool | Upstream route | What it does |
|---|---|---|
revrule_get_graph | GET /v1/graphs/{graph_id} | Fetch one of your RevRule revenue entitlement graphs by id: its participants, rules, and ledger wiring. Read-only. |
revrule_list_payout_evidence | GET /v1/graphs/{graph_id}/payout-evidence | List payout evidence recorded for a graph: verified payouts linked back to the original entitlement ledger entries (transaction hash, log index, block data, authorizing signature). Read-only. |
revrule_simulate_event | POST /v1/graphs/{graph_id}/simulate | Dry-run a revenue event against a graph's rules and see what the rules would produce, with zero side effects: nothing is recorded, no payout is prepared or submitted. The tool wraps the supplied event as {event: ...} for the production rail; simulation has no side effects. |
Install the revrule v1.1.0 MCPB bundle in an MCPB-compatible client, or run from source below. The published bundle declares the supported MCP tools. This direct release is the verified installation path while third-party directory listings are revalidated.
git clone https://github.com/Payloadhq/revrule-mcp
cd revrule-mcp node mcp/index.js
Or run it straight from GitHub with npx:
npx -y github:Payloadhq/revrule-mcp
MCP client configuration (stdio):
{
"mcpServers": { "revrule": { "command": "node", "args": ["/path/to/revrule-mcp/mcp/index.js"], "env": { "PAYLOAD_RAIL_API_KEY": "your-rail-api-key" } } } }
| Variable | Required | Default | Purpose |
|---|---|---|---|
PAYLOAD_RAIL_API_KEY | Required for tool calls | — | Your own Payload rail API key. A free self-serve key from the console works for evaluation; the paid license covers production use. Sent to the rail only as a Bearer Authorization header. |
PAYLOAD_RAIL_URL | Optional | https://payload-rail.fly.dev | Payload rail base URL. |
Fail-closed: with no API key configured, the server still starts and lists its tools, and every tool call returns a clear API key not configured error. The key never leaves your machine except as the Authorization header to the rail.
Free. You can evaluate RevRule end to end without paying:
revrule_get_graph, revrule_list_payout_evidence) and the zero-side-effect dry run (revrule_simulate_event) work against your own graphs. A paid entitlement is not required to evaluate.Paid. The RevRule license is $99 one-time. It is the production product: run your real revenue graphs on the rail with the entitlement ledger and payout evidence as your system of record, instead of evaluating in the sandbox.
RevRule computes who is owed what and records the evidence. It does not execute payments and it never holds funds; your own systems and payment partners move the money.
MIT — see LICENSE.
RevRule is a product of Payload, separate from Veyline (Payload's authorization layer) and from callx402 by Payload, the MCP client layer for x402-priced actions.