@powerui/mcp

Model Context Protocol server for Power UI — bridges AI clients (Claude Desktop, Claude Code, Cursor, etc.) to your Power UI account so an agent can list, load, save, and edit your Power BI themes alongside whatever else you're doing.

What it does

Once installed, your AI client gets 17 new tools:

• Account assets: list_themes, load_theme, save_theme, list_palettes, create_palette, update_palette, open_in_studio
• Theme styling: create_theme, modify_theme, set_title_style, set_effects_style, set_visual_property, set_page_background, set_wallpaper, get_visual_controls
• Output: inject_theme (writes a Power BI theme JSON into a .pbip report's RegisteredResources/), export_theme (returns the JSON)

A typical session: "build me a report from these CSVs using my Acme brand theme" → agent calls load_theme({slug: "acme"}), hands the result to your Power BI report builder, calls inject_theme(report_path) when done. "Now make titles bigger and save as Acme Q4" → set_title_style, save_theme({name: "Acme Q4"}).

Install

You need a Power UI Pro account and an API key. Create one at powerui.com/settings/api-keys.

Add this to your MCP client's config (e.g. claude_desktop_config.json, .mcp.json, or Cursor's MCP settings):

{
  "mcpServers": {
    "powerui": {
      "command": "npx",
      "args": ["-y", "@powerui/mcp@latest"],
      "env": {
        "POWERUI_API_KEY": "pwu_live_..."
      }
    }
  }
}

Restart your AI client. Tools should appear automatically.

Configuration

| env var | default | purpose | | --- | --- | --- | | POWERUI_API_KEY | (required) | API key minted from your Power UI dashboard | | POWERUI_API_URL | https://www.powerui.com | override for self-hosted / staging |

Requirements

• Node 18+
• A Power UI Pro plan (API keys require a paid account)

Links

• Power UI
• Issues
• Source

License

MIT