Analytixus DnAML repository access (read/write nodes, tree navigation, search) via MCP.
Runs on your machine from its package; the steps are below.
At most: moves money, runs code or commands, deletes data, or sends messages for you.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Published to NuGet as `Analytixus.Mcp` — run it with your .NET MCP host.
Analytixus is a metadata-driven development platform built around DnAML (Data and Analytics Markup Language) — you model your data sources, transformations, and documentation once, and generate SQL, pipelines, and docs from that single model instead of maintaining them by hand.
This MCP server exposes an Analytixus DnAML repository to any MCP-compatible client — Claude Desktop, Cursor, VS Code Copilot Chat, or your own tooling — so an AI assistant can read and write your metadata model directly.
This repository hosts documentation and configuration guidance for the Analytixus MCP server. The server itself is distributed as a self-contained executable and as a .NET tool (see below).
maxDepth on the tree tool to keep large repositories manageable.Option 1 — self-contained download (no runtime required). Pre-built archives for Windows, macOS, and Linux are available on request from the Analytixus team.
Option 2 — .NET global tool (requires the .NET 8 runtime):
dotnet tool install --global Analytixus.Mcp
This installs the analytixus-mcp command.
Add to claude_desktop_config.json:
%APPDATA%\Claude\claude_desktop_config.json~/Library/Application Support/Claude/claude_desktop_config.json~/.config/Claude/claude_desktop_config.json{
"mcpServers": {
"analytixus": {
"command": "analytixus-mcp",
"args": ["--stdio"],
"env": {
"ANALYTIXUS_SOLUTION_PATH": "/path/to/your/dnaml-solution",
"ANALYTIXUS_SOLUTION_NAME": "YourSolutionName"
}
}
}
}
(If you installed the self-contained archive instead of the .NET tool, use the full path to the
extracted Analytixus.Mcp executable as command.)
Option A — via the MCP Servers gallery (recommended):
Open the Extensions panel (Ctrl+Shift+X), switch to the MCP Servers tab, search for
Analytixus, and click Install + Enable.
VS Code adds an entry to your user-level mcp.json automatically — but without the required
environment variables yet.
Open mcp.json and add an env key to the installed entry — leave command, args,
gallery, and version exactly as VS Code wrote them:
%APPDATA%\Code\User\mcp.json~/Library/Application Support/Code/User/mcp.json~/.config/Code/User/mcp.json{
"servers": {
"de.analytixus/analytixus-mcp": {
"type": "stdio",
"command": "dnx",
"args": ["Analytixus.Mcp@0.8.5", "--yes"],
"gallery": "https://api.mcp.github.com",
"version": "0.8.5",
"env": {
"ANALYTIXUS_SOLUTION_PATH": "/path/to/your/dnaml-solution",
"ANALYTIXUS_SOLUTION_NAME": "YourSolutionName"
}
}
}
}
(The version number in args and version is whatever VS Code installed — keep it as-is.)
Option B — manual config (install the .NET global tool first:
dotnet tool install --global Analytixus.Mcp):
Add to mcp.json:
{
"servers": {
"analytixus": {
"type": "stdio",
"command": "analytixus-mcp",
"args": ["--stdio"],
"env": {
"ANALYTIXUS_SOLUTION_PATH": "/path/to/your/dnaml-solution",
"ANALYTIXUS_SOLUTION_NAME": "YourSolutionName"
}
}
}
}
These extensions manage their own MCP server lists independently of VS Code's built-in mcp.json.
Open each extension's MCP settings and add a server entry with command: analytixus-mcp,
args: ["--stdio"], and the same env variables shown above.
claude mcp add --env ANALYTIXUS_SOLUTION_PATH=/path/to/your/dnaml-solution \
--env ANALYTIXUS_SOLUTION_NAME=YourSolutionName --scope user \
analytixus -- analytixus-mcp --stdio
| Variable | Purpose |
|---|---|
ANALYTIXUS_SOLUTION_PATH | Path to the DnAML solution's root folder. |
ANALYTIXUS_SOLUTION_NAME | Name of the solution — pins this server instance to it. |
ANALYTIXUS_LOG_LEVEL | Trace|Debug|Info|Warn|Error|Fatal (default Info). |
| Tool | Purpose |
|---|---|
solutions_list | Registered solutions (only the pinned one when ANALYTIXUS_SOLUTION_* is set) |
repository_get_tree | Repository tree of a solution. Use maxDepth (e.g. 1) on large repositories to limit output |
repository_search | Search nodes by name and/or node type; returns a hierarchical result including parents |
repository_search_content | Search by DnAML content (text) and/or section presence (hasColumns, hasOrigins, hasReferences, hasDocumentation, hasLoad, hasConsumers); each hit reports why it matched |
repository_read_node, repository_read_node_recursive | Read a node (or a node with all descendants) as DnAML or XML |
repository_write_node | Validate and write DnAML to an existing node (renames are detected) |
repository_add_folder, repository_add_source, repository_add_node_under_folder, repository_add_node_under_source | Create folders, sources and nodes |
repository_delete_node, repository_delete_folder_recursive, repository_delete_source_recursive | Delete (irreversible) |
get_dnaml_reference | DnAML syntax reference |
solution_add, solution_delete, solution_rename | Solution management — only exposed when the server is not pinned to one solution |
Logs are written to logs/ next to the tool. In --stdio mode stderr only receives Warn and
above (never stdout — that is the JSON-RPC channel).
Visit analytixus.de for more about the Analytixus platform.