Skip to main content
Glama

Related Servers

Alternatives to pbi-doc-generator

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      MCP server for Power BI Desktop and .pbip projects, enabling DAX queries, model documentation, measure management, refresh, .pbix-to-.pbip conversion, and PBIR visual editing.
      140
      365 PyPI
      33
      Apache 2.0
    • A
      license
      B
      quality
      B
      maintenance
      MCP server for interacting with local Power BI Desktop and .pbip projects, enabling DAX queries, model documentation, measure editing, and PBIR visual management via natural language.
      90
      365 PyPI
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for connecting to Microsoft Fabric and Power BI semantic models, enabling workspace browsing, dataset management, TMSL retrieval, DAX queries, model creation/editing, and includes a Best Practice Analyzer with 71 rules.
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides full lineage graph analysis for Power BI .pbix files, enabling source-to-visual-field traversal. Exposes REST and MCP endpoints for building, searching, and exporting lineage graphs.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A read-only MCP server that reports BI pipeline readiness, blockers, and the next allowed action for governed Power BI workflows. It never writes files, executes warehouse work, or grants human approvals.
      6
      6 npm
      2
      Apache 2.0

    TDQS

    A3.5/5.0

    Scored across 8 tools

    Disambiguation4/5

    Each tool has a reasonably distinct job: catalog_summary gives counts, list_models enumerates models, and inspect_model drills into one model's blueprint. The only fuzzy pairs are list_models vs inspect_model (depth vs enumeration) and measure_lineage vs source_impact (both lineage, but scoped to measures vs upstream sources), and the descriptions clarify both well enough.

    Naming Consistency4/5

    All names are snake_case with a uniform pbi_ prefix and use domain vocabulary consistently. There is a minor deviation between verb-first names (pbi_list_models, pbi_inspect_model, pbi_generate_portal) and noun-first names (pbi_catalog_summary, pbi_measure_lineage, pbi_health_audit, pbi_source_impact), but the pattern remains readable and predictable.

    Tool Count5/5

    Eight tools is a well-scoped set for a Power BI documentation/lineage server, with each tool covering a distinct read or generate capability. Nothing feels redundant or padded.

    Completeness4/5

    The surface covers discovery, inspection, DAX/M search, lineage, impact analysis, health auditing, and portal generation, which is strong coverage for documentation workflows. Minor gaps exist: no standalone report or workspace listing (reports appear only as downstream entities), no per-model export, and no tool to trigger a catalog scan/refresh.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data