Skip to main content
Glama
tghanchidnx

mdx-mcp

by tghanchidnx

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MDX_MCP_CUBEYesCube name
MDX_MCP_USERNoUsername for basic auth (optional)
MDX_MCP_CATALOGYesDatabase catalog name
MDX_MCP_ENDPOINTYesXMLA endpoint URL
MDX_MCP_PASSWORDNoPassword for basic auth (optional, alternative to MDX_MCP_PASSWORD_FILE)
ANTHROPIC_API_KEYYesAPI key for Claude (default LLM provider)
MDX_MCP_PASSWORD_FILENoPath to password file (optional, alternative to MDX_MCP_PASSWORD)

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
mdx_introspectA

Return the cube's 'skills' block: measures, dimensions, hierarchies for grounding.

mdx_askA

Answer a natural-language question with a verified MDX result.

Introspects the cube, generates k candidate MDX queries, executes them read-only, and returns the self-consistency verdict: {status: answer|abstain|clarify, value, mdx, agreement, errors, ...}. Never guesses a number when candidates disagree or fail.

mdx_runB

Execute a provided MDX query (read-only; SELECT/WITH only) and return the cell value.

mdx_explainB

Explain a given MDX query in plain language (what it measures, slices, and returns).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 4 tools

Disambiguation5/5

Each tool serves a distinct function: answering questions, explaining queries, introspecting cube schema, and executing user-provided queries. No overlap in purpose.

Naming Consistency5/5

All tools follow the consistent mdx_verb pattern with verbs (ask, explain, introspect, run) that clearly indicate their action.

Tool Count5/5

Four tools is appropriate for the domain, covering the core interactions with an MDX cube without being excessive or insufficient.

Completeness5/5

The tool set provides a complete workflow: introspect to understand the cube, ask to get answers, explain to understand queries, and run to execute arbitrary MDX. No obvious gaps.

Maintenance

ActivityStale
ResponsivenessNo issues