Can I use Microsoft Power BI as a CLI?

Yes. KosmoKrator exposes a Microsoft Power BI CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Microsoft Power BI through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Microsoft Power BI tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Microsoft Power BI credentials stored?

Microsoft Power BI credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Microsoft Power BI MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

analytics

Microsoft Power BI MCP Integration for Codex

Connect Microsoft Power BI to Codex through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 7 read 0 write Manual OAuth token auth

Submit Microsoft Power BI feedback View package source

Connect Microsoft Power BI to Codex

Use KosmoKrator as a local MCP proxy for Codex so coding sessions can reach selected integrations with explicit write policy.

Register kosmo mcp:serve as a local stdio server and choose the integration allowlist. The gateway is local, scoped to this integration, and starts with --write=deny so Codex can inspect read-capable tools without receiving write access by default.

Microsoft Power BI MCP Config for Codex

Keep write access denied or ask-based unless the workspace is trusted.

{
  "mcpServers": {
    "kosmokrator-powerbi": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=powerbi",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=powerbi --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Microsoft Power BI instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Microsoft Power BI Tools Visible to Codex

Codex sees stable MCP tool names generated from the Microsoft Power BI integration catalog.

MCP tool	Source function	Type	Description
`integration__powerbi__powerbi_list_workspaces`	`powerbi.powerbi_list_workspaces`	Read	List Power BI workspaces (groups) the authenticated user has access to. Returns workspace IDs and names that can be used to query datasets and reports.
`integration__powerbi__powerbi_get_workspace`	`powerbi.powerbi_get_workspace`	Read	Get details for a specific Power BI workspace (group) by its ID.
`integration__powerbi__powerbi_list_datasets`	`powerbi.powerbi_list_datasets`	Read	List datasets within a Power BI workspace. Returns dataset IDs, names, and configuration details.
`integration__powerbi__powerbi_get_dataset`	`powerbi.powerbi_get_dataset`	Read	Get details for a specific Power BI dataset within a workspace, including schema and refresh configuration.
`integration__powerbi__powerbi_list_reports`	`powerbi.powerbi_list_reports`	Read	List reports within a Power BI workspace. Returns report IDs, names, embed URLs, and associated dataset IDs.
`integration__powerbi__powerbi_get_report`	`powerbi.powerbi_get_report`	Read	Get details for a specific Power BI report within a workspace, including embed URL and associated dataset.
`integration__powerbi__powerbi_get_current_user`	`powerbi.powerbi_get_current_user`	Read	Get the authenticated user's Power BI profile, including display name and email address.

Related Microsoft Power BI Pages

Microsoft Power BI CLIUse direct JSON commands instead of MCP discovery. Microsoft Power BI MCPFull gateway reference and MCP tool names. KosmoKrator for CodexClient-level gateway setup.