Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Protocol feature showcase: echo, math, resources, images, sampling and elicitation demos.
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.
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": {
"allfeatures": {
"command": "npx",
"args": [
"-y",
"@reneturcios/allfeatures",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add allfeatures -- npx -y @reneturcios/allfeatures mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"allfeatures": {
"command": "npx",
"args": [
"-y",
"@reneturcios/allfeatures",
"mcp"
]
}
}
}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": {
"allfeatures": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/allfeatures",
"mcp"
]
}
}
}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 6, 2026
The registry name was verified with the GitHub account CloudCorpRecords, 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.
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 (0.1.0) reached the registry 9 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, BankBridge
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.
Works in any MCP agent, including local models. Read-only bank accounts, spending, investments.
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.
allfeatures is a showroom for the MCP protocol itself. Rather than doing one job well, it exercises the moving parts a client and server need to agree on: plain text results, images, annotations, embedded resources, resource links, structured content, a long-running call, and the three features that only work when the connected client helps out — sampling, roots and elicitation. If you are building a client, point it at allfeatures and watch each feature light up (or fail honestly, with a clear error, when your client does not offer it).
npx @reneturcios/allfeatures echo hello
Or run the container image:
docker run -i ghcr.io/cloudcorprecords/allfeatures
The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.
Only the two tools that make sense without a client are exposed as commands:
allfeatures echo hello there # hello there
allfeatures add 2 3 # 5 allfeatures add -1.5 0.5 # -1 allfeatures --version # 0.1.0
Exit codes: 0 on success, 1 when the arguments cannot be handled (for example, add given non-numeric input), 2 for usage errors.
One bin serves both faces. The mcp subcommand starts a stdio MCP server:
npx -y @reneturcios/allfeatures mcp
MCP client configuration:
{
"mcpServers": { "allfeatures": { "command": "npx", "args": ["-y", "@reneturcios/allfeatures", "mcp"] } } }
| Tool | Input | What it returns |
|---|---|---|
echo | message (string, required) | The message, unchanged, as text. |
add | a, b (numbers, required) | The sum, as text. |
longRunningOperation | duration (number, optional, seconds, default 10), steps (number, optional, default 5) | Waits the duration split across the steps, then a completion note. |
printEnv | — | The server process environment as JSON text. |
sampleLLM | prompt (string, required), maxTokens (number, optional) | A completion sampled from the client's model (see below). |
getTinyImage | — | A 1x1 transparent PNG as image content, plus a short text note. |
annotatedMessage | messageType ("error" / "success" / "debug", required), includeImage (boolean, optional) | A text message whose annotations (audience and priority) depend on the type; the tiny image is attached when includeImage is true. Errors are priority 1 for user and assistant, successes are priority 0.7 for the user, debug notes are priority 0.3 for the assistant. |
getResourceReference | resourceId (number, required) | An embedded text resource with URI demo://resource/ . |
getResourceLinks | count (number, required, 1–10) | That many resource_link items. Counts outside 1–10 are an error. |
structuredContent | location (string, required) | Fixed sample weather (72°F, Sunny, 45% humidity) for the location, as structuredContent with matching JSON text alongside. |
listRoots | — | The client's roots, as JSON text (see below). |
startElicitation | — | The outcome of asking the user for a short response (see below). |
zip | — | An embedded blob resource (application/zip) holding a real, minimal ZIP archive with one stored file, hello.txt. The archive is assembled byte by byte — CRC32, local header, central directory — with no archive library. |
sampleLLM, listRoots and startElicitation cannot be answered by the server alone: they ask the connected client to do something (sample its model, list its roots, prompt its user). allfeatures only sends those requests when the client advertised the matching capability during initialisation. When it did not, the tool returns an error result saying exactly that — the server never invents a plausible-looking answer.
npm install
npm run build # tsc -> dist/ npm test # node test runner over test/*.test.ts, no network npm run dev # run the CLI from source via tsx
MIT — see LICENSE.