Analytixus

de.analytixusPublished by analytixus.dev0.8.5Updated Oct 31, 2026

Analytixus DnAML repository access (read/write nodes, tree navigation, search) via MCP.

VerifiedSTDIODesktop onlyDeveloper ToolsData & Analytics

Overview

AI-generated overview

Exposes an Analytixus DnAML metadata repository to an AI assistant so it can browse, search, read and write data-model nodes.

What you can do
  • Browse solutions and the repository tree of a DnAML model, with depth limits for large repositories
  • Search nodes by name or type, and search DnAML content or section presence such as columns, origins, references and documentation
  • Read a node, or a node with all descendants, as DnAML or XML
  • Create folders, sources and nodes, and validate and write DnAML to existing nodes
  • Delete nodes, folders and sources, and add, rename or delete solutions when not pinned to one
  • Look up DnAML syntax reference
When to use it
Useful when you work with Analytixus DnAML solutions and want an assistant to inspect, search, document or edit the metadata model directly instead of hand-editing files. Best suited to teams already modelling data sources and transformations in Analytixus.
Requirements
Runs locally over stdio. Either the self-contained executable (available on request from Analytixus) or the .NET global tool Analytixus.Mcp, which needs the .NET 8 runtime. Set ANALYTIXUS_SOLUTION_PATH and ANALYTIXUS_SOLUTION_NAME to pin the server to a solution; ANALYTIXUS_LOG_LEVEL is optional. Desktop clients only.
Before you install
The server can write and delete repository content: node writes are validated but deletions of nodes, folders and sources are irreversible, and solution add, rename and delete are exposed when the server is not pinned to a single solution. Point ANALYTIXUS_SOLUTION_PATH at a version-controlled or backed-up solution, and review destructive calls before approving them.

Installation

In SourceWeft

  1. Open Analytixus in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Analytixus MCP Server

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

What it does

  • Browse the repository tree — list solutions, sources, and objects in a DnAML model.
  • Search the repository — find nodes by name or type, or by DnAML content and sections (columns, origins, references, documentation, load, consumers); results keep their parent context. Use maxDepth on the tree tool to keep large repositories manageable.
  • Read and write DnAML nodes — fetch a single object's definition, create or update objects under a source or folder.
  • Solution management — list available solutions, add/rename/delete them.

Installation

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

bash
dotnet tool install --global Analytixus.Mcp

This installs the analytixus-mcp command.

Configuration

Claude Desktop

Add to claude_desktop_config.json:

  • Windows: %APPDATA%\Claude\claude_desktop_config.json
  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Linux: ~/.config/Claude/claude_desktop_config.json
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.)

VS Code (Copilot Chat)

Option A — via the MCP Servers gallery (recommended):

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

  2. Open mcp.json and add an env key to the installed entry — leave command, args, gallery, and version exactly as VS Code wrote them:

    • Windows: %APPDATA%\Code\User\mcp.json
    • macOS: ~/Library/Application Support/Code/User/mcp.json
    • Linux: ~/.config/Code/User/mcp.json
    json
    {  "servers": {    "de.analytixus/analytixus-mcp": {      "type": "stdio",      "command": "dnx",      "args": ["[email protected]", "--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:

json
{  "servers": {    "analytixus": {      "type": "stdio",      "command": "analytixus-mcp",      "args": ["--stdio"],      "env": {        "ANALYTIXUS_SOLUTION_PATH": "/path/to/your/dnaml-solution",        "ANALYTIXUS_SOLUTION_NAME": "YourSolutionName"      }    }  }}

Roo Code / Cline / other VS Code AI extensions

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 Code (CLI)

bash
claude mcp add --env ANALYTIXUS_SOLUTION_PATH=/path/to/your/dnaml-solution \  --env ANALYTIXUS_SOLUTION_NAME=YourSolutionName --scope user \  analytixus -- analytixus-mcp --stdio

Environment variables

VariablePurpose
ANALYTIXUS_SOLUTION_PATHPath to the DnAML solution's root folder.
ANALYTIXUS_SOLUTION_NAMEName of the solution — pins this server instance to it.
ANALYTIXUS_LOG_LEVELTrace|Debug|Info|Warn|Error|Fatal (default Info).

Tools

ToolPurpose
solutions_listRegistered solutions (only the pinned one when ANALYTIXUS_SOLUTION_* is set)
repository_get_treeRepository tree of a solution. Use maxDepth (e.g. 1) on large repositories to limit output
repository_searchSearch nodes by name and/or node type; returns a hierarchical result including parents
repository_search_contentSearch 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_recursiveRead a node (or a node with all descendants) as DnAML or XML
repository_write_nodeValidate 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_sourceCreate folders, sources and nodes
repository_delete_node, repository_delete_folder_recursive, repository_delete_source_recursiveDelete (irreversible)
get_dnaml_referenceDnAML syntax reference
solution_add, solution_delete, solution_renameSolution 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).

Learn more

Visit analytixus.de for more about the Analytixus platform.

Source: README.md at commit 5143df9

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

4
  1. v0.8.5LatestOct 10, 2026
  2. v0.8.4Oct 10, 2026
  3. v0.8.3Sep 30, 2026
  4. v0.8.2Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts