Allows AI agents to query, validate, preview, and generate source code from dtct data contracts and ngin templates.
Also known as marthvon/datuma_k, datuma-k, @marthvon/datuma-k-mcp
- Stars
- 0
- Tools
- 7
- Downloads, 30 days
- —
- Latest version
- 1.0.0
- Last commit
- Sep 21, 2026
- License
- AGPL-3.0
What is datuma_k MCP?
datuma_k allows AI agents to query, validate, preview, and generate source code from dtct data contracts and ngin templates. It exposes 7 tools, such as list_project, query_contracts, validate.
Summary generated from the project's README
About datuma_k MCP server
Managing dtct data contracts and ngin templates through an AI agent is what this server enables. It acts as a bridge between your local development environment and an AI client like Claude or Cursor by utilizing an existing datuma_k binary installed in your application repository. This setup allows agents to interact directly with your project files and configuration.
Developers use specific tools to query contracts, validate syntax, and preview changes before they are committed. The server provides capabilities to generate source code via the run command and offers advice on whether to use ngin templates or handwritten code. To function, the datuma_k binary must be available on your system path, or you can specify its location using the DATUMA_K environment variable. The agent operates within your project directory to access necessary files and environment settings.
What you can do with it
- 1Querying existing data contractsAsk the AI to find specific models or fields within your data contract catalog.
- 2Validating contract syntaxHave the agent check your data contracts for errors using the local validation tool.
- 3Generating source codeInstruct the agent to write generated spans based on your current templates.
- 4Deciding between template typesRequest guidance on when it is appropriate to use ngin templates versus manual coding.
Written from the project's README. Every use case is checked against a quote from it.
How to install datuma_k MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall datuma_k MCP in Claude Code
$ claude mcp add datuma-k -- npx -y @marthvon/datuma-k-mcpInstall datuma_k MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"datuma-k": {
"command": "npx",
"args": [
"-y",
"@marthvon/datuma-k-mcp"
]
}
}
}Install datuma_k MCP in VS Code
.vscode/mcp.json
{
"servers": {
"datuma-k": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@marthvon/datuma-k-mcp"
]
}
}
}Install datuma_k MCP in VS Code CLI
$ code --add-mcp '{"name":"datuma-k","type":"stdio","command":"npx","args":["-y","@marthvon/datuma-k-mcp"]}'Install datuma_k MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"datuma-k": {
"command": "npx",
"args": [
"-y",
"@marthvon/datuma-k-mcp"
]
}
}
}Install datuma_k MCP in Codex
$ codex mcp add datuma-k -- npx -y @marthvon/datuma-k-mcpInstall datuma_k MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.datuma-k] command = "npx" args = ["-y", "@marthvon/datuma-k-mcp"]
Install datuma_k MCP in Gemini CLI
$ gemini mcp add -s user datuma-k npx -- -y @marthvon/datuma-k-mcpInstall datuma_k MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"datuma-k": {
"command": "npx",
"args": [
"-y",
"@marthvon/datuma-k-mcp"
]
}
}
}datuma_k MCP tools 7
Detected from the READMElist_projectquery_contractsvalidatepreviewgenerateadvise_ngininfer_patterns
| list_project | — | |
| query_contracts | — | |
| validate | — | |
| preview | — | |
| generate | — | |
| advise_ngin | — | |
| infer_patterns | — |
Configuration
DATUMA_KAbsolute path to the datuma_k binary. Omit if datuma_k is already on PATH.
| Name | Description | |
|---|---|---|
| DATUMA_K | Absolute path to the datuma_k binary. Omit if datuma_k is already on PATH. |
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablemarthvon/datuma_k is public and reachablegithub.com/marthvon/datuma_k ↗Pass
- Package names this repository as its source@marthvon/datuma-k-mcp names marthvon/datuma_k as sourcenpmjs.com/package/@marthvon/datuma-k-mcp ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)AGPL-3.0spdx.org/licenses/AGPL-3.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-09-21github.com/marthvon/datuma_k ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @marthvon/datuma-k-mcpPass
- No critical advisory in the package or its dependencies4 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model7 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubdatuma_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/dtctdatuma://language/ngindatuma://language/standardsdatuma://docs/keywordsdatuma://docs/practicesdatuma://docs/when-ngin
Prompts
add-model, add-field, scaffold-ngin, should-use-ngin, infer-contract-patterns
Tests
npm test
Publishing
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.
One-time setup
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.
Release
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].version
Then:
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"
What ships
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.
Troubleshooting
| 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.<your-github-username>/. |
expected length <= 100 on body.description |
server.json description is capped at 100 characters. The npm description is not. |
datuma_k MCP questions
How do I add datuma_k MCP to Claude Code?
Run claude mcp add datuma-k -- npx -y @marthvon/datuma-k-mcp in your terminal. Add --scope user to make it available in every project.
How do I add datuma_k MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does datuma_k MCP provide?
It exposes 7 tools, including list_project, query_contracts, validate, preview, generate.
How do I configure the server if the datuma_k binary is not in my PATH?
You can point the DATUMA_K environment variable to the absolute path of your binary in the mcp.json configuration.
Where should the process be executed from?
The process current working directory should be the datuma_k project directory containing the .env file, or you can pass the root path in each tool call.