Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Query, validate, preview, and generate source from *.dtct data contracts and *.ngin templates.
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.
DATUMA_KYou 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": {
"datuma-k": {
"command": "npx",
"args": [
"-y",
"@marthvon/datuma-k-mcp"
],
"env": {
"DATUMA_K": "your-value"
}
}
}
}Run this in your terminal
claude mcp add datuma-k --env DATUMA_K=your-value -- npx -y @marthvon/datuma-k-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"datuma-k": {
"command": "npx",
"args": [
"-y",
"@marthvon/datuma-k-mcp"
],
"env": {
"DATUMA_K": "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": {
"datuma-k": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@marthvon/datuma-k-mcp"
],
"env": {
"DATUMA_K": "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.
DATUMA_K 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 marthvon, 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 (1.0.0) reached the registry 2 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, FlyDocs
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.
Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.
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.
stdio MCP server for agents using the installed datuma_k binary in an app repo. It does not link the compiler crate. Set DATUMA_K to the binary if it is not on PATH.
Published to npm as @marthvon/datuma-k-mcp and to the MCP Registry as io.github.marthvon/datuma-k.
Cursor / Claude example (mcp.json):
{
"mcpServers": { "datuma_k": { "command": "npx", "args": ["-y", "@marthvon/datuma-k-mcp"] } } }
datuma_k must be on PATH. If it is not, point DATUMA_K at the binary:
{
"mcpServers": { "datuma_k": { "command": "npx", "args": ["-y", "@marthvon/datuma-k-mcp"], "env": { "DATUMA_K": "/ABS/PATH/TO/datuma_k/target/release/datuma_k" } } } }
cd mcp
npm install npm run build
Then use "command": "node" with "args": ["/ABS/PATH/TO/datuma_k/mcp/dist/index.js"].
The process cwd should be the datuma_k project (the directory with .env), or pass root on each tool call.
| Tool | Binary | Notes |
|---|---|---|
list_project | (files + .env) | Directories and contract/template paths |
query_contracts | datuma_k catalog | Optional trait / model / field / attribute / type |
validate | datuma_k check | Parse + data/keywords.md required |
preview | datuma_k preview | Plan without writing |
generate | datuma_k run | Writes generated spans |
advise_ngin | (local rules) | When to use ngin vs handwritten code |
infer_patterns | catalog + keywords.md | Traits, widgets, association review notes, sync risks, aliases |
datuma://language/dtctdatuma://language/ngindatuma://language/standardsdatuma://docs/keywordsdatuma://docs/practicesdatuma://docs/when-nginadd-model, add-field, scaffold-ngin, should-use-ngin, infer-contract-patterns
npm test
Two registries, in this order. npm hosts the tarball; the MCP Registry hosts only metadata and verifies it against the published npm package, so npm must go first or the second publish fails with Registry validation failed for package.
| Name | Where | Set in |
|---|---|---|
@marthvon/datuma-k-mcp | npm package | package.json name |
io.github.marthvon/datuma-k | MCP Registry server | package.json mcpName and server.json name — these two must match, or the registry rejects the publish |
The io.github.marthvon/ prefix is not cosmetic: GitHub device-flow auth only grants that namespace. A different prefix needs DNS or HTTP auth.
brew install mcp-publisher # or a binary from the registry releases page
npm login # npm account, scope @marthvon
npm requires 2FA to publish. If the account does not have it, npm publish fails with 403 ... Two-factor authentication or granular access token with bypass 2fa enabled is required, before it ever looks at the tarball. Check with npm profile get; enable with npm profile enable-2fa auth-and-writes or on npmjs.com, and keep the recovery codes.
Bump the version in three places — the registry rejects a version it has already seen, and a mismatch between the npm package version and server.json packages[0].version fails verification:
package.json → versionserver.json → versionserver.json → packages[0].versionThen:
npm test # tsc + node --test
mcp-publisher validate # checks server.json against the live registry, publishes nothing npm publish --otp=123456 # prepublishOnly runs the build; drop --otp to be prompted mcp-publisher login github # device code → github.com/login/device mcp-publisher publish
mcp-publisher login persists a token, so day-to-day releases are npm publish then mcp-publisher publish.
Verify:
npm view @marthvon/datuma-k-mcp version
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.marthvon/datuma-k"
files in package.json limits the tarball to dist, resources, and README.md. resources/ is required at runtime — server.ts resolves it as dist/../resources — so dropping it from files produces a package that installs cleanly and fails on every resource read. Confirm with npm pack --dry-run before publishing.
| Error | Cause |
|---|---|
403 ... Two-factor authentication ... is required | 2FA disabled on the npm account. See above. |
403 ... you do not have access | The @marthvon scope belongs to an org; confirm membership with npm org ls marthvon. |
Registry validation failed for package | npm publish did not happen yet, or mcpName in package.json does not match name in server.json. |
Invalid or expired Registry JWT token | Re-run mcp-publisher login github. |
You do not have permission to publish this server | Server name does not start with io.github. /. |
expected length <= 100 on body.description | server.json description is capped at 100 characters. The npm description is not. |