Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Reach a real person: quote their door, browse who is reachable, knock, and read the reply.
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.
THREE_WS_API_KEY, THREE_WS_BASE, THREE_WS_TIMEOUT_MSValues marked secret are keys to your account. Never share them or paste them into a chat.
You 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": {
"knock": {
"command": "npx",
"args": [
"-y",
"@three-ws/knock-mcp"
],
"env": {
"THREE_WS_API_KEY": "your-value",
"THREE_WS_BASE": "your-value",
"THREE_WS_TIMEOUT_MS": "your-value"
}
}
}
}Run this in your terminal
claude mcp add knock --env THREE_WS_API_KEY=your-value --env THREE_WS_BASE=your-value --env THREE_WS_TIMEOUT_MS=your-value -- npx -y @three-ws/knock-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"knock": {
"command": "npx",
"args": [
"-y",
"@three-ws/knock-mcp"
],
"env": {
"THREE_WS_API_KEY": "your-value",
"THREE_WS_BASE": "your-value",
"THREE_WS_TIMEOUT_MS": "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": {
"knock": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@three-ws/knock-mcp"
],
"env": {
"THREE_WS_API_KEY": "your-value",
"THREE_WS_BASE": "your-value",
"THREE_WS_TIMEOUT_MS": "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.
THREE_WS_BASE envTHREE_WS_TIMEOUT_MS 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 7, 2026
The registry name was verified with the GitHub account nirholas, 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: THREE_WS_API_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.1.0) reached the registry 37 days 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, Python MCP
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.
Local-only Python MCP server for the Files.com API.
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.
Let an agent reach a real person.
Knock is a priced door to a human. Every three.ws account can publish one at three.ws/knock/ , and the owner sets what one message from a stranger costs. Paying that price buys exactly one message through: it lands in their inbox, and their 3D companion walks on screen wherever they are on the site and delivers it out loud, naming the sender and the amount. The USDC settles directly to the recipient.
This MCP server gives any agent client (Claude Code, Claude Desktop, Cursor, Windsurf, or your own) the tools to find a reachable person, knock, and read the answer.
On a free door, knock_send sends immediately, because nothing moves.
On a priced door, knock_send does not pay and cannot pay. It returns the recipient, the amount, the token, the chain and the endpoint, and stops. The human approves the spend and pays from the wallet they already control, with @three-ws/knock or any other x402 client.
That is deliberate. An MCP server with a key in an environment variable should not be able to move a person's money on its own.
Claude Code:
claude mcp add knock -- npx -y @three-ws/knock-mcp
Any MCP client, by config:
{
"mcpServers": { "knock": { "command": "npx", "args": ["-y", "@three-ws/knock-mcp"] } } }
Add THREE_WS_API_KEY only if you also want the two owner-side tools:
{
"mcpServers": { "knock": { "command": "npx", "args": ["-y", "@three-ws/knock-mcp"], "env": { "THREE_WS_API_KEY": "sk_live_…" } } } }
Node 20+.
| Tool | Credential | What it does |
|---|---|---|
knock_quote | none | What one person charges for a single message, which chains they take it on, the length limit, and the endpoint. |
knock_directory | none | Everyone reachable right now, cheapest first. |
knock_send | none | Get one message through. Free doors send; priced doors are quoted for a human to approve. |
knock_receipt | none | What became of a knock you sent: pending, read, replied (with the reply), or dismissed. |
knock_inbox | THREE_WS_API_KEY | The knocks your door has taken, each with what the sender paid, plus totals. |
knock_act | THREE_WS_API_KEY | Reply to, mark read, dismiss, or block one of them. |
The owner tools are account-scoped server-side. They can never read or change another account.
You: Find someone on three.ws who takes questions about x402, and ask them
how their Solana facilitator handles fee payers.
The agent calls knock_directory, picks a door, calls knock_quote to get the live price, and comes back with:
nirholas (@nirholas) charges $0.05 USDC on solana.
Endpoint: https://three.ws/api/x402/knock?to=nirholas The payment settles directly to the recipient. Approve?
You approve and pay from your own wallet:
npx @three-ws/knock send nirholas \
"How does your Solana facilitator handle the fee payer?" \ --from "Ada (research agent)" --subject "x402 fee payer" --payer ./payer.mjs
Their companion walks on screen and says: *"Ada paid $0.05 to reach you: x402 fee payer."* When they answer, the agent reads it back with knock_receipt on the receipt URL. No account on either side beyond the door owner's.
| Variable | Required | Default | Purpose |
|---|---|---|---|
THREE_WS_API_KEY | for knock_inbox / knock_act only | none | API key or OAuth token for the account whose door you manage. Aliases: THREE_WS_TOKEN, THREE_WS_BEARER. |
THREE_WS_BASE | no | https://three.ws | Override only when self-hosting. |
THREE_WS_TIMEOUT_MS | no | 20000 | Per-request timeout. |
node src/index.js # stdio
npm run inspect # MCP Inspector npm test # the tool surface and the no-wallet rule
Apache-2.0