datuma_k MCP

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.

Install

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"
      }
    }
  }
}

From source

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.

Tools

| 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 |

Resources

• datuma://language/dtct
• datuma://language/ngin
• datuma://language/standards
• datuma://docs/keywords
• datuma://docs/practices
• datuma://docs/when-ngin

Prompts

add-model, add-field, scaffold-ngin, should-use-ngin, infer-contract-patterns

Tests

npm test