Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Write a freelance service contract: scope, deliverables, rate, termination, liability, signatures.
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.
MCP_LICENSE_KEYValues marked secret are keys to your account. Never share them or paste them into a chat.
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
Fill in the empty values before running it.
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 9, 2026
The registry name was verified with the GitHub account theluckystrike, 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: MCP_LICENSE_KEY
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.22.5) reached the registry 26 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, agentPickup
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ 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.
Find pickup shops near you, order, pay by card or USDC (x402), and get the QR to collect in person.
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.
In the [official MCP Registry](https://registry.modelcontextprotocol.io/v0.1/servers/io.github.theluckystrike%2Fservice-agreement/versions/latest) (io.github.theluckystrike/service-agreement). An mcp service agreement writer for freelancers who are about to start client work and do not want to copy a rotting template off the internet again. Give it the parties, the scope of services, the deliverables, the rate and payment terms, start and end dates, a termination notice period, a liability cap and the governing jurisdiction, and it stores the agreement and renders clean Markdown, or print-ready HTML, with a signature block for both sides. A before-you-send-it checklist lists missing fields and flags one-sided gaps neutrally, like an agreement with no termination clause. A built-in clause library covers IP assignment, confidentiality, late payment interest, kill fee and revision rounds, filled with your agreement's own details. Every render carries a one-line note that it is a template, not legal advice. Everything stays on this machine; there is no account and no network call.
Built by theluckystrike.
npm publish for @theluckystrike/mcp-service-agreement is pending, so npx -y @theluckystrike/mcp-service-agreement returns 404 today. Until then, a clone+build is the working path.
macOS ~/Library/Application Support/Claude/claude_desktop_config.json, Windows %APPDATA%\Claude\claude_desktop_config.json:
{
"mcpServers": { "service-agreement": { "command": "npx", "args": ["-y", "@theluckystrike/mcp-service-agreement"] } } }
claude mcp add service-agreement -- npx -y @theluckystrike/mcp-service-agreement
~/.cursor/mcp.json (global) or .cursor/mcp.json (project), same entry as Claude Desktop.
| tool | what it does |
|---|---|
agreement_create | Write an agreement: parties, scope, deliverables, rate and payment terms, dates, termination notice, liability cap, jurisdiction. Stores it and returns the rendered Markdown. Returns SA-YYYY-NNNN |
agreement_get | Read one agreement in full by SA number or client name, with its status history |
agreement_list | List agreements newest first; filter by status and client |
agreement_update_status | Move the agreement exactly one step -- draft, sent, signed, expired -- stamping date and note into its history |
clause_library | The five built-in clauses: IP assignment, mutual confidentiality, late payment interest, kill fee, revision rounds. Pro: full texts with the agreement's variables filled in |
agreement_render | Render for signing: Markdown, or self-contained HTML with print CSS (Pro). Includes the signature block and the template-not-legal-advice line |
agreement_checklist | The before-you-send-it checklist: missing fields and one-sided gaps flagged neutrally |
license_status / license_activate | Free or Pro, and the key |
| Free | Pro | |
|---|---|---|
| Active agreements | 3 | Unlimited |
| Core template (parties, services, deliverables, payment, term, termination, liability, jurisdiction, signatures) | Yes | Yes |
| Markdown rendering | Yes | Yes |
| Before-you-send checklist | Yes | Yes |
| Clause library | Titles and summaries | Full texts, variables filled |
| HTML rendering, print-ready | No | Yes |
The document is never metered. Three active agreements covers a working freelancer's live engagements, and an agreement stops counting the moment it expires, so writing, reading, checklists and Markdown stay free for good. What Pro adds is the full clause library, print-ready HTML, and unlimited active agreements.
Get Pro: https://mcp.zovo.one/buy/service-agreement, $19 one-time for this server, or $39 for the bundle.
Every rendered agreement ends with one line: "This agreement is a template, not legal advice." The checklist flags gaps neutrally, what the agreement says as written, for both parties, and never tells anyone what the law is or what to do.
All data stays local, in ${XDG_DATA_HOME:-~/.local/share}/mcp-servers/service-agreement/. Two files: agreements.json, counter.json. Nothing is sent anywhere, there is no account, no API key and no network call in this server at all. License keys are verified offline.
Built by theluckystrike. https://github.com/theluckystrike
Any MCP client (Claude, Cursor, Windsurf, VS Code) can read this repository's documentation directly via GitMCP - no install: