Analytixus

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

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

{

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

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

   {

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

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)

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

Tools

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.