Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Mindstone-internal release-pipeline test connector; not for use. Single ping tool; no auth.
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": {
"canary": {
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-canary"
]
}
}
}Run this in your terminal
claude mcp add canary -- npx -y @mindstone/mcp-server-canaryPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"canary": {
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-canary"
]
}
}
}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": {
"canary": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-canary"
]
}
}
}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 registry name was verified with the GitHub account mindstone, 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.0.4) reached the registry 5 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, Microsoft Exchange Online 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.
Exchange Online admin for MSPs: forwarding audits, EWS posture and offboarding, no PowerShell
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.
Mindstone's internal release-pipeline test connector — not for use. It exists only to validate the rebel-oss release pipeline end-to-end. Single ping tool; no external dependencies, no auth, no bridge.
No required environment variables — the install completes without prompts.
Manual config for Claude Desktop / Claude Code / Goose / Continue.dev (Canary)
{
"mcpServers": { "Canary": { "command": "npx", "args": [ "-y", "@mindstone/mcp-server-canary" ], "env": {} } } }
Releasing a real connector for the first time through a brand-new pipeline (Trusted Publishing, GitHub Actions, mcp-publisher, registry sync, host-app catalog) couples two unknowns: the pipeline correctness AND the connector correctness. The canary decouples them — it exercises every step of the pipeline with a tool whose only behaviour is ping → pong v3: .
Once the pipeline has proven itself stable on the canary, real connectors can adopt the same path without piggy-backing on infrastructure debugging.
See docs/plans/260525_oss_release_automation.md (Mindstone-internal) for the full design.
pingEcho a message back wrapped as pong v3: .
| Field | Type | Required | Description |
|---|---|---|---|
message | string | yes | A short message to echo back. 1-200 chars. |
Example:
{
"tool": "ping", "arguments": { "message": "hello" } }
Response:
pong v3: hello
npx -y @mindstone/mcp-server-canary
This starts the server on stdio. Most MCP hosts will spawn this for you when you add @mindstone/mcp-server-canary as a stdio MCP server.
Pre-1.0 — this is the canary. Versions are stamped 0.0.x deliberately. Do not depend on this connector for any real workflow; its only purpose is to exercise the release machinery.