@luquimbo/bi-superpowers 4.1.3 → 4.1.4

package/.claude-plugin/marketplace.json

@@ -6,7 +6,7 @@
   },
   "metadata": {
     "description": "AI-powered skills for Power BI Desktop development. Works with Claude Code, GitHub Copilot, Codex, Gemini CLI, and Kilo Code.",
-    "version": "4.1.3",
+    "version": "4.1.4",
     "repository": "https://github.com/luquimbo/bi-superpowers"
   },
   "plugins": [

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "bi-superpowers",
   "description": "Claude Code plugin for Power BI, Microsoft Fabric, and semantic model workflows powered by the official Microsoft MCP servers.",
-  "version": "4.1.3",
+  "version": "4.1.4",
   "author": {
     "name": "Lucas Sanchez"
   },

package/.claude-plugin/skill-manifest.json

@@ -1,6 +1,6 @@
 {
   "name": "bi-superpowers",
-  "version": "4.1.3",
+  "version": "4.1.4",
   "skillCount": 4,
   "skills": [
     {

package/.plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "spec": "open-plugin-spec@1",
   "name": "bi-superpowers",
-  "version": "4.1.3",
+  "version": "4.1.4",
   "description": "Claude Code plugin for Power BI, Microsoft Fabric, and semantic model workflows powered by the official Microsoft MCP servers.",
   "author": {
     "name": "Lucas Sanchez"

package/AGENTS.md

@@ -131,11 +131,12 @@ The shared v4.1.x contract is:
 - **2 MCP servers** — `powerbi-modeling-mcp`, `microsoft-learn`
 
 Agent-specific behavior:
-- **Claude Code** — `super kickoff` can also generate a project-local plugin with slash commands: `/bi-start`, `/project-kickoff`, `/pbi-connect`, `/report-design`
-- **GitHub Copilot** — uses the installed skills + MCP config via natural-language prompts
-- **Codex** — uses the installed skills + MCP config via natural-language prompts
-- **Gemini CLI** — uses the installed skills + MCP config via natural-language prompts
-- **Kilo Code** — uses the installed skills + MCP config via natural-language prompts
+- **All agents** — the primary install is user-level via `super install`, not repo-local.
+- **Claude Code** — `super kickoff` can optionally generate a project-local plugin with slash commands: `/bi-start`, `/project-kickoff`, `/pbi-connect`, `/report-design`.
+- **GitHub Copilot** — uses the installed user-level skills + MCP config via natural-language prompts.
+- **Codex** — uses the installed user-level skills + MCP config via natural-language prompts. Do not run `super kickoff` for Codex setup.
+- **Gemini CLI** — uses the installed user-level skills + MCP config via natural-language prompts.
+- **Kilo Code** — uses the installed user-level skills + MCP config via natural-language prompts.
 
 `/report-design` has one extra runtime prerequisite on every agent: **Windows + Power BI Desktop (standalone) + Python 3.10+ + `pipx` + `pbi-cli-tool`**. The bundled Node scripts handle visual/theme authoring, but the current flow still uses `pbi` for connect, page ops, and validate. If that stack is not available yet, start with `bi-start`, `project-kickoff`, or `pbi-connect`.
 
@@ -194,13 +195,14 @@ Los 4 skills quedan disponibles como MCP prompts.
 
 ## Plugin System
 
-BI Agent Superpowers generates a native Claude Code plugin from a single source of truth.
+BI Agent Superpowers installs skills and MCP configuration at the user level for all supported agents. It can also generate a native Claude Code plugin from the same source of truth when a user explicitly wants repo-local Claude Code plugin files.
 
 ### Output Targets
 
 | Target | Format | Output |
 |--------|--------|--------|
-| Claude Code / 1code.dev | Plugin | `.claude-plugin/`, `commands/`, `skills/`, `.mcp.json` |
+| All agents | User-level skills + MCP config | `~/.agents/skills`, agent-specific MCP config |
+| Claude Code / 1code.dev | Optional local plugin | `.claude-plugin/`, `commands/`, `skills/`, `.mcp.json` |
 | Claude Desktop | MCPB extension | `bi-superpowers.mcpb` (via `super build-desktop`) |
 
 ### Plugin Structure (generated by kickoff/recharge)

package/CHANGELOG.md

@@ -5,6 +5,22 @@ All notable changes to BI Agent Superpowers will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [4.1.4] — 2026-04-24
+
+### Fixed
+
+- `super mcp-setup` no longer creates repo-local `.mcp.json` files in arbitrary
+  projects. It now only runs against an existing local Claude Code plugin unless
+  the user explicitly passes a local plugin target.
+- `super recharge` now refuses to generate local Claude Code plugin files in an
+  uninitialized repo, pointing users back to the user-level `super install`
+  workflow instead.
+- CLI help, install docs, and `pbi-connect`/`bi-start` skill guidance now make
+  `super install --all --yes` the primary multi-agent path for Claude Code,
+  GitHub Copilot, Codex, Gemini CLI, and Kilo Code. `super kickoff`,
+  `super recharge`, and `super mcp-setup` are documented as optional local
+  Claude Code plugin commands only.
+
 ## [4.1.3] — 2026-04-23
 
 ### Fixed

package/README.md

@@ -118,7 +118,9 @@ After that, start a new session and run:
 /bi-start
 ```
 
-### Optional Local Claude Code Plugin
+### Advanced: Optional Local Claude Code Plugin
+
+This is only for Claude Code users who deliberately want repo-local slash-command plugin files. Codex, GitHub Copilot, Gemini CLI, and Kilo Code should use `super install` above; do not run `super kickoff` for those agents.
 
 Inside a Power BI project repo:
 
@@ -162,7 +164,7 @@ Run these Claude Code plugin commands:
 After installation, start the plugin with /bi-start and tell me if any restart or reload is needed.
 ```
 
-If you also want project-local plugin files in the current repo:
+If you also want project-local plugin files in the current repo for Claude Code only:
 
 ```text
 Set up BI Agent Superpowers for this project as a local Claude Code plugin.
@@ -199,6 +201,8 @@ npm install -g @luquimbo/bi-superpowers
 super install --agent codex --yes
 
 After it finishes, verify that the shared skills were installed under ~/.agents/skills and that the Codex MCP config was updated. Then summarize the installed skills and MCP servers.
+
+Do not run super kickoff or super mcp-setup for Codex; those commands are only for optional repo-local Claude Code plugin files.
 ```
 
 ### Gemini CLI
@@ -385,8 +389,8 @@ Common commands:
 
 ```bash
 super install          # Install 4 skills + 2 MCPs for selected agents
-super kickoff          # Generate a local Claude Code plugin in the current repo
-super recharge         # Regenerate local plugin artifacts after source changes
+super kickoff          # Advanced: generate optional local Claude Code plugin files
+super recharge         # Regenerate optional local Claude Code plugin artifacts
 super powers           # List available skills
 super scan             # Compare source skills with generated artifacts
 super checkup          # Validate skill content
@@ -403,6 +407,8 @@ super help             # Show full CLI help
 
 Generated by `super kickoff` or `super recharge`:
 
+This tree is optional and Claude Code specific. It is not required for Codex, GitHub Copilot, Gemini CLI, or Kilo Code because those agents use the user-level install created by `super install`.
+
 ```text
 project/
 ├─ .claude-plugin/
@@ -521,7 +527,7 @@ This means `pbi-cli-tool` is not optional for `report-design` today.
 
 ```bash
 super upgrade
-super install --yes
+super install --all --yes
 ```
 
 If you created a project-local plugin:

package/bin/cli.js

@@ -11,9 +11,9 @@
  * Architecture:
  * - Skills are authored once in src/content/skills/ and copied out to
  *   each supported agent by `super install`.
- * - `super kickoff` generates a full Claude Code plugin tree in a
+ * - `super kickoff` optionally generates a local Claude Code plugin tree in a
  *   user project (skills + commands + MCP config).
- * - `super recharge` regenerates that plugin after local edits.
+ * - `super recharge` regenerates an existing local Claude Code plugin after edits.
  *
  * Supported agents: Claude Code, GitHub Copilot, Codex, Gemini CLI, Kilo Code.
  * License: MIT. This project is fully open source — no activation, no keys.
@@ -150,18 +150,18 @@ Open-source toolkit for Power BI Desktop development across 5 AI coding agents:
 Claude Code · GitHub Copilot · Codex · Gemini CLI · Kilo Code.
 
 Quick Start:
-  super install              # Install skills + MCPs for all your AI agents
-  super kickoff              # Generate the Claude Code plugin in a project
+  super install --all --yes  # Install skills + MCPs user-level for all agents
+  super powers               # List the skills and MCPs available
 
 Usage:
   super <command> [options]
 
 Primary commands:
-  install           Install the 4 skills + 2 MCPs across your AI agents
-  kickoff [path]    Generate the full Claude Code plugin in a project
-  recharge [path]   Regenerate the plugin after editing source skills
+  install           Install the 4 skills + 2 MCPs user-level across your AI agents
+  kickoff [path]    Optional: generate a repo-local Claude Code plugin
+  recharge [path]   Optional: regenerate an existing repo-local Claude Code plugin
   build-desktop     Build the .mcpb extension for Claude Desktop
-  mcp-setup         Configure the official Microsoft MCP servers
+  mcp-setup         Refresh MCP config for an existing Claude Code local plugin
   powers            List available skills and MCPs
   upgrade           Update to the latest version on npm
   about             Show installation info
@@ -178,13 +178,14 @@ Options:
 Examples:
   super install                    # Interactive installer for all agents
   super install --all --yes        # Non-interactive install for every agent
+  super install -a codex           # Install user-level skills + MCPs for Codex
   super install -a claude-code     # Install only for Claude Code
-  super kickoff                    # Initialize plugin in current directory
-  super kickoff ./my-project       # Initialize in a specific directory
-  super kickoff --dry-run          # Preview what would be created
-  super recharge                   # Regenerate plugin after editing skills
+  super kickoff                    # Claude Code only: create local plugin files
+  super kickoff ./my-project       # Claude Code only: initialize in a repo
+  super kickoff --dry-run          # Preview local Claude Code plugin files
+  super recharge                   # Regenerate existing local Claude Code plugin
   super build-desktop              # Build .mcpb for Claude Desktop
-  super mcp-setup                  # Configure the local Power BI Modeling MCP
+  super mcp-setup                  # Existing local Claude Code plugin only
 
 Open source — MIT licensed.
 Documentation: https://github.com/luquimbo/bi-superpowers
@@ -257,7 +258,7 @@ function parseSkillMetadata(content) {
 // ============================================
 
 /**
- * `super kickoff` — generate the Claude Code plugin in the target directory.
+ * `super kickoff` — generate an optional local Claude Code plugin in the target directory.
  *
  * What it does:
  *  1. Generates .claude-plugin/, .mcp.json, commands/, skills/ in the target.
@@ -278,10 +279,17 @@ async function initProject(args) {
   console.log(`
 BI Agent Superpowers v${VERSION}
 ================================
-Claude Code Plugin Setup
+Claude Code local plugin setup
 
 Initializing in: ${targetDir}
 Skills available: ${skills.length}
+
+This is not the multi-agent install path. For Codex, GitHub Copilot,
+Gemini CLI, Kilo Code, and user-level Claude Code installs, run:
+
+  super install --all --yes
+
+kickoff writes repo-local Claude Code plugin files only.
 `);
 
   if (dryRun) {
@@ -323,7 +331,7 @@ Skills available: ${skills.length}
 }
 
 /**
- * `super recharge` — regenerate the Claude Code plugin without prompts.
+ * `super recharge` — regenerate an existing local Claude Code plugin without prompts.
  *
  * Re-reads the saved tool preferences from .bi-superpowers.json (or falls
  * back to the default toolset) and regenerates everything. Useful after:
@@ -357,6 +365,23 @@ Regenerating configs from ${skills.length} skills...
     }
   }
 
+  if (!hasProjectLocalPlugin(targetDir)) {
+    console.log(`
+This repo does not contain a local Claude Code plugin generated by super kickoff.
+
+For Codex, GitHub Copilot, Gemini CLI, Kilo Code, and user-level Claude Code
+installs, refresh the user-level install instead:
+
+  super install --all --yes
+
+If you intentionally want repo-local Claude Code plugin files, run:
+
+  super kickoff
+`);
+    process.exitCode = 2;
+    return;
+  }
+
   const config = loadToolConfig(targetDir);
   const selectedTools = ensurePluginTool(config.tools || [...DEFAULT_TOOLS]);
 
@@ -508,6 +533,13 @@ function loadToolConfig(targetDir) {
   };
 }
 
+function hasProjectLocalPlugin(targetDir) {
+  return (
+    fs.existsSync(path.join(targetDir, CONFIG_FILE)) ||
+    fs.existsSync(path.join(targetDir, '.claude-plugin', 'plugin.json'))
+  );
+}
+
 /**
  * Dispatch to the tool-specific generator.
  */
@@ -525,6 +557,10 @@ function showCompletionMessage(targetDir, tools, skillCount) {
 
   Skills:     ${skillCount} skills generated
 
+  Note: this is a repo-local Claude Code plugin only.
+  Codex, GitHub Copilot, Gemini CLI, Kilo Code, and user-level Claude Code
+  installs use: super install --all --yes
+
 ────────────────────────────────────────────────────────────
   CLAUDE CODE
 ────────────────────────────────────────────────────────────

package/bin/commands/mcp-setup.js

@@ -1,8 +1,8 @@
 /**
  * MCP Setup Command
  * =================
- * Configures the official Microsoft MCP servers for the Claude Code plugin
- * and legacy adapter formats.
+ * Configures the official Microsoft MCP servers for an existing project-local
+ * Claude Code plugin and legacy adapter formats.
  *
  * Usage:
  *   super mcp-setup
@@ -103,6 +103,13 @@ function loadConfiguredTools(targetDir) {
   return ['claude-plugin'];
 }
 
+function hasLocalPluginMarker(targetDir) {
+  return (
+    fs.existsSync(path.join(targetDir, '.bi-superpowers.json')) ||
+    fs.existsSync(path.join(targetDir, '.claude-plugin', 'plugin.json'))
+  );
+}
+
 function readJson(filePath) {
   if (!fs.existsSync(filePath)) {
     return {};
@@ -157,8 +164,24 @@ function mcpSetupCommand(args, config) {
 
   if (options.deprecatedFlags.length > 0) {
     tui.warning(
-      `Deprecated flags ignored: ${options.deprecatedFlags.join(', ')}. MCP setup is now plugin-first and uses the official Microsoft servers.`
+      `Deprecated flags ignored: ${options.deprecatedFlags.join(', ')}. MCP setup now targets local Claude Code plugin configs and uses the official Microsoft servers.`
+    );
+  }
+
+  if (!options.tool && !hasLocalPluginMarker(targetDir)) {
+    tui.warning('mcp-setup is only for project-local Claude Code plugin configs.');
+    tui.info(
+      'For Codex, GitHub Copilot, Gemini CLI, Kilo Code, and Claude Code user-level installs, run:'
+    );
+    tui.listItem('super install --all --yes');
+    tui.info(
+      'That writes user-level skills and MCP config under your home directory without creating files in this repo.'
+    );
+    tui.info(
+      'If you intentionally need a local Claude Code plugin, run `super kickoff` first or pass `--tool claude-plugin`.'
     );
+    process.exitCode = 2;
+    return;
   }
 
   let configuredTools = loadConfiguredTools(targetDir);

package/bin/utils/mcp-detect.js

@@ -188,7 +188,7 @@ function getInstallInstructions() {
           'Ir a Extensions (Ctrl+Shift+X)',
           'Buscar "Power BI Modeling MCP"',
           'Instalar la extensión de Microsoft',
-          'Ejecutar: super mcp-setup',
+          'Ejecutar: super install --all --yes',
         ],
         link: 'https://aka.ms/powerbi-modeling-mcp-vscode',
       },

package/commands/bi-start.md

@@ -55,7 +55,7 @@ Interpret the single-line output:
     ```bash
     super upgrade
     ```
-    After it finishes, remind: _"Si instalaste skills en el perfil del agente, corré `super install --yes`. Si además usás un plugin local generado con `super kickoff`, corré `super recharge` dentro de ese repo."_
+  After it finishes, remind: _"Corré `super install --all --yes` para refrescar la instalación user-level de todos los agentes. Solo si además mantenés un plugin local de Claude Code generado con `super kickoff`, corré `super recharge` dentro de ese repo."_
 
   On `no` — respect it, continue to PHASE 1 silently. The update-state.json already tracks the user's snooze per `update-check.js` semantics.
 
@@ -86,7 +86,7 @@ Do these detections in order:
    ```
    (or equivalent). `$pbiDesktopRunning = true` if present.
 
-4. **MCP configured**: look for `.mcp.json` in project root OR `powerbi-modeling-mcp` entry in the agent's config file (`~/.claude.json`, `~/.codex/config.toml`, etc). Keep the check shallow — no need to deep-diff.
+4. **MCP configured**: look first for `powerbi-modeling-mcp` in the agent's user-level config file (`~/.claude.json`, `~/.codex/config.toml`, etc). Only check project-root `.mcp.json` when the user explicitly says they use a local Claude Code plugin. Keep the check shallow — no need to deep-diff.
 
 ### Emit the context in 3-4 lines max
 
@@ -180,7 +180,7 @@ Stop. Don't hover. The user will tell you what they want next.
 - **Project analysis or setup**: that's `/project-kickoff`. If the user says "analizar mi proyecto", "armar el modelo base", "arrancar uno nuevo desde cero", delegate.
 - **MCP wiring details**: that's `/pbi-connect`. bi-start just offers to dispatch it; the actual configuration work is in that skill.
 - **Report authoring**: that's `/report-design`. Same pattern.
-- **Running the update**: bi-start offers + dispatches `super upgrade`; the actual refresh path after eso (`/plugin update bi-superpowers`, `super install --yes`, o `super recharge`) is owned by `/bin/cli.js`.
+- **Running the update**: bi-start offers + dispatches `super upgrade`; the actual refresh path after eso (`/plugin update bi-superpowers`, `super install --all --yes`, o `super recharge` only for local Claude Code plugins) is owned by `/bin/cli.js`.
 
 ## Related Skills
 

package/commands/pbi-connect.md

@@ -36,10 +36,10 @@ Activate this skill when user mentions:
 - "can't connect to Power BI", "connection error", "MCP not working"
 
 ## Identity
-You are a **Power BI MCP Connection Specialist**. Your job is to help the user connect their AI agent to Power BI Desktop using the official Microsoft MCP servers shipped with bi-superpowers, with a plugin-first workflow.
+You are a **Power BI MCP Connection Specialist**. Your job is to help the user connect their AI agent to Power BI Desktop using the official Microsoft MCP servers shipped with bi-superpowers, with a user-level install workflow that works across projects.
 
 ## MANDATORY RULES
-1. **PLUGIN-FIRST.** Prefer `.mcp.json` in the Claude Code plugin root.
+1. **USER-LEVEL FIRST.** Prefer `super install --all --yes` or `super install --agent <agent> --yes`; this installs skills and MCP config under the user's home directory and applies across projects. `.mcp.json` is only for an optional repo-local Claude Code plugin.
 2. **OFFICIAL SERVERS ONLY.** Use `powerbi-modeling-mcp` (local) and `microsoft-learn` (HTTP). Do not invent or recommend unofficial MCPs.
 3. **WINDOWS LIMITATION.** Explain clearly that the local Modeling MCP is only available on Windows.
 4. **NO PORT INVENTION.** Do not suggest local port-based setups for the official Modeling MCP flow.
@@ -60,7 +60,8 @@ I'll help you connect your AI agent using the official Microsoft MCP servers.
 What do you need?
 
 1. Connect to Power BI Desktop on this machine (Windows)
-2. Verify that my plugin `.mcp.json` is configured correctly
+2. Verify that my agent MCP config is installed correctly
+3. Verify an optional local Claude Code plugin `.mcp.json`
 ```
 
 ---
@@ -83,11 +84,21 @@ Before we continue:
 
 ### If the user is on Windows and installed the extension
 
-Guide them to:
+Guide them to the user-level install:
 
-1. Run `bi-superpowers mcp-setup`
-2. Confirm `.mcp.json` contains `powerbi-modeling-mcp`
-3. Restart or refresh Claude Code
+1. Run `super install --all --yes`, or for one agent run `super install --agent codex --yes` / `super install --agent claude-code --yes` / etc.
+2. Confirm the agent config contains `powerbi-modeling-mcp` and `microsoft-learn`.
+3. Restart or refresh the AI agent so it reloads skills and MCP servers.
+
+Use these config locations:
+
+| Agent | Skill path | MCP config |
+| --- | --- | --- |
+| Claude Code | `~/.claude/skills` or `~/.agents/skills` | `~/.claude.json` |
+| GitHub Copilot | `~/.copilot/skills` | `~/.copilot/mcp-config.json` |
+| Codex | `~/.agents/skills` | `~/.codex/config.toml` |
+| Gemini CLI | `~/.gemini/skills` | `~/.gemini/settings.json` |
+| Kilo Code | `~/.kilo/skills` | `~/.kilo/mcp_settings.json` |
 
 Use this explanation:
 
@@ -99,18 +110,13 @@ and starts it with `--start`.
 
 If the user wants a config example, show:
 
-```json
-{
-  "powerbi-modeling-mcp": {
-    "type": "stdio",
-    "command": "node",
-    "args": ["${CLAUDE_PLUGIN_ROOT}/bin/mcp/powerbi-modeling-launcher.js"]
-  },
-  "microsoft-learn": {
-    "type": "http",
-    "url": "https://learn.microsoft.com/api/mcp"
-  }
-}
+```toml
+[mcp_servers.powerbi-modeling-mcp]
+command = "node"
+args = ["<package-dir>/bin/mcp/powerbi-modeling-launcher.js"]
+
+[mcp_servers.microsoft-learn]
+url = "https://learn.microsoft.com/api/mcp"
 ```
 
 ### If the user installed the executable manually
@@ -124,9 +130,11 @@ BI_SUPERPOWERS_POWERBI_MODELING_MCP_PATH
 Then re-run:
 
 ```bash
-super mcp-setup
+super install --all --yes
 ```
 
+If they are intentionally maintaining a repo-local Claude Code plugin, they can run `super mcp-setup` inside that plugin project instead.
+
 ### If the user is on macOS or Linux
 
 Say:
@@ -141,15 +149,41 @@ For live editing of a local semantic model, you need a Windows environment.
 
 ---
 
-## PHASE 2: Verify Plugin Config
+## PHASE 2: Verify Agent MCP Config
 
 If the user chooses option 2:
 
+Check the config for the agent they use:
+
+- Claude Code: `~/.claude.json`
+- GitHub Copilot: `~/.copilot/mcp-config.json`
+- Codex: `~/.codex/config.toml`
+- Gemini CLI: `~/.gemini/settings.json`
+- Kilo Code: `~/.kilo/mcp_settings.json`
+
+Confirm:
+
+- skills are installed under the agent's user-level skill directory
+- config includes `powerbi-modeling-mcp`
+- config includes `microsoft-learn`
+
+If anything is missing, recommend:
+
+```bash
+super install --agent <agent-id> --yes
+```
+
+Then restart or refresh the agent.
+
+## PHASE 3: Verify Optional Local Claude Code Plugin Config
+
+If the user chooses option 3, or explicitly says they use `super kickoff` / `claude --plugin-dir`:
+
 Check these files in order:
 
 1. `.claude-plugin/plugin.json`
 2. `.mcp.json`
-3. `.bi-superpowers.json` if present
+3. `.bi-superpowers.json`
 
 Confirm:
 
@@ -178,7 +212,8 @@ claude --plugin-dir .
 | --- | --- |
 | Modeling MCP missing on Windows | Install the Microsoft extension in VS Code or Cursor |
 | Modeling MCP installed manually | Set `BI_SUPERPOWERS_POWERBI_MODELING_MCP_PATH` |
-| Plugin not loading MCPs | Re-run `bi-superpowers mcp-setup` and restart Claude Code |
+| Agent not loading MCPs | Re-run `super install --agent <agent-id> --yes` and restart the agent |
+| Local Claude Code plugin not loading MCPs | Re-run `super mcp-setup` inside the plugin project and restart Claude Code |
 | macOS/Linux local modeling request | Use `microsoft-learn` for docs; live editing requires Windows |
 | User asks about Excel MCP | Explain Excel remains supported through skills and library content, not a default MCP |
 
@@ -190,7 +225,8 @@ claude --plugin-dir .
 | --- | --- | --- |
 | Recommend `uvx` for Modeling MCP | Not the official Microsoft installation path | Use the official executable via the local launcher |
 | Ask the user to find a localhost port | Not required in the new flow | Use the official Modeling MCP launcher |
-| Put plugin MCP config in `.claude/settings.json` first | Plugin-first flow uses `.mcp.json` | Prefer `.mcp.json` at the plugin root |
+| Run `super kickoff` for Codex/GitHub Copilot/Gemini/Kilo setup | `kickoff` creates repo-local Claude Code plugin files | Use `super install --agent <agent-id> --yes` |
+| Treat `.mcp.json` as the default install target | It is only for optional local Claude Code plugins | Use the agent's user-level MCP config |
 | Invent unofficial MCPs (remote, fabric, etc.) | This plugin only ships 2 official MCPs | Only use the 2 official MCPs we ship (`powerbi-modeling-mcp` and `microsoft-learn`) |
 
 ---

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@luquimbo/bi-superpowers",
-  "version": "4.1.3",
+  "version": "4.1.4",
   "description": "Open-source Power BI Desktop toolkit for Claude Code, GitHub Copilot, Codex, Gemini CLI, and Kilo Code. Ships 4 skills and 2 official Microsoft MCP servers.",
   "main": "bin/cli.js",
   "bin": {

package/skills/bi-start/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: "bi-start"
 description: "Use when the user asks about BI Start Skill, especially phrases like \"bi-start\", \"bi start\", \"/bi-start\", \"empezar\", \"comenzar\", \"arranco\"."
-version: "4.1.3"
+version: "4.1.4"
 ---
 
 <!-- Generated by BI Agent Superpowers. Edit src/content/skills/bi-start.md instead. -->
@@ -57,7 +57,7 @@ Interpret the single-line output:
     ```bash
     super upgrade
     ```
-    After it finishes, remind: _"Si instalaste skills en el perfil del agente, corré `super install --yes`. Si además usás un plugin local generado con `super kickoff`, corré `super recharge` dentro de ese repo."_
+  After it finishes, remind: _"Corré `super install --all --yes` para refrescar la instalación user-level de todos los agentes. Solo si además mantenés un plugin local de Claude Code generado con `super kickoff`, corré `super recharge` dentro de ese repo."_
 
   On `no` — respect it, continue to PHASE 1 silently. The update-state.json already tracks the user's snooze per `update-check.js` semantics.
 
@@ -88,7 +88,7 @@ Do these detections in order:
    ```
    (or equivalent). `$pbiDesktopRunning = true` if present.
 
-4. **MCP configured**: look for `.mcp.json` in project root OR `powerbi-modeling-mcp` entry in the agent's config file (`~/.claude.json`, `~/.codex/config.toml`, etc). Keep the check shallow — no need to deep-diff.
+4. **MCP configured**: look first for `powerbi-modeling-mcp` in the agent's user-level config file (`~/.claude.json`, `~/.codex/config.toml`, etc). Only check project-root `.mcp.json` when the user explicitly says they use a local Claude Code plugin. Keep the check shallow — no need to deep-diff.
 
 ### Emit the context in 3-4 lines max
 
@@ -182,7 +182,7 @@ Stop. Don't hover. The user will tell you what they want next.
 - **Project analysis or setup**: that's `/project-kickoff`. If the user says "analizar mi proyecto", "armar el modelo base", "arrancar uno nuevo desde cero", delegate.
 - **MCP wiring details**: that's `/pbi-connect`. bi-start just offers to dispatch it; the actual configuration work is in that skill.
 - **Report authoring**: that's `/report-design`. Same pattern.
-- **Running the update**: bi-start offers + dispatches `super upgrade`; the actual refresh path after eso (`/plugin update bi-superpowers`, `super install --yes`, o `super recharge`) is owned by `/bin/cli.js`.
+- **Running the update**: bi-start offers + dispatches `super upgrade`; the actual refresh path after eso (`/plugin update bi-superpowers`, `super install --all --yes`, o `super recharge` only for local Claude Code plugins) is owned by `/bin/cli.js`.
 
 ## Related Skills
 

package/skills/bi-start/scripts/update-check.js

@@ -47,7 +47,7 @@ const HTTPS_TIMEOUT_MS = 5000;
 // Rewritten at generation time when this helper is copied into
 // `skills/<name>/scripts/update-check.js`. In the canonical source under
 // `bin/commands/`, it stays null and we fall back to package.json.
-const BUNDLED_INSTALLED_VERSION = "4.1.3";
+const BUNDLED_INSTALLED_VERSION = "4.1.4";
 
 // ---------------------------------------------------------------------------
 // Argument parsing

package/skills/pbi-connect/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: "pbi-connect"
 description: "Use when the user asks about Power BI MCP Connection Skill, especially phrases like \"connect Power BI\", \"PBI connection\", \"MCP connection\", \"Power BI MCP\", \"modeling mcp\", \"Power BI Modeling MCP\"."
-version: "4.1.3"
+version: "4.1.4"
 ---
 
 <!-- Generated by BI Agent Superpowers. Edit src/content/skills/pbi-connect.md instead. -->
@@ -38,10 +38,10 @@ Activate this skill when user mentions:
 - "can't connect to Power BI", "connection error", "MCP not working"
 
 ## Identity
-You are a **Power BI MCP Connection Specialist**. Your job is to help the user connect their AI agent to Power BI Desktop using the official Microsoft MCP servers shipped with bi-superpowers, with a plugin-first workflow.
+You are a **Power BI MCP Connection Specialist**. Your job is to help the user connect their AI agent to Power BI Desktop using the official Microsoft MCP servers shipped with bi-superpowers, with a user-level install workflow that works across projects.
 
 ## MANDATORY RULES
-1. **PLUGIN-FIRST.** Prefer `.mcp.json` in the Claude Code plugin root.
+1. **USER-LEVEL FIRST.** Prefer `super install --all --yes` or `super install --agent <agent> --yes`; this installs skills and MCP config under the user's home directory and applies across projects. `.mcp.json` is only for an optional repo-local Claude Code plugin.
 2. **OFFICIAL SERVERS ONLY.** Use `powerbi-modeling-mcp` (local) and `microsoft-learn` (HTTP). Do not invent or recommend unofficial MCPs.
 3. **WINDOWS LIMITATION.** Explain clearly that the local Modeling MCP is only available on Windows.
 4. **NO PORT INVENTION.** Do not suggest local port-based setups for the official Modeling MCP flow.
@@ -62,7 +62,8 @@ I'll help you connect your AI agent using the official Microsoft MCP servers.
 What do you need?
 
 1. Connect to Power BI Desktop on this machine (Windows)
-2. Verify that my plugin `.mcp.json` is configured correctly
+2. Verify that my agent MCP config is installed correctly
+3. Verify an optional local Claude Code plugin `.mcp.json`
 ```
 
 ---
@@ -85,11 +86,21 @@ Before we continue:
 
 ### If the user is on Windows and installed the extension
 
-Guide them to:
+Guide them to the user-level install:
 
-1. Run `bi-superpowers mcp-setup`
-2. Confirm `.mcp.json` contains `powerbi-modeling-mcp`
-3. Restart or refresh Claude Code
+1. Run `super install --all --yes`, or for one agent run `super install --agent codex --yes` / `super install --agent claude-code --yes` / etc.
+2. Confirm the agent config contains `powerbi-modeling-mcp` and `microsoft-learn`.
+3. Restart or refresh the AI agent so it reloads skills and MCP servers.
+
+Use these config locations:
+
+| Agent | Skill path | MCP config |
+| --- | --- | --- |
+| Claude Code | `~/.claude/skills` or `~/.agents/skills` | `~/.claude.json` |
+| GitHub Copilot | `~/.copilot/skills` | `~/.copilot/mcp-config.json` |
+| Codex | `~/.agents/skills` | `~/.codex/config.toml` |
+| Gemini CLI | `~/.gemini/skills` | `~/.gemini/settings.json` |
+| Kilo Code | `~/.kilo/skills` | `~/.kilo/mcp_settings.json` |
 
 Use this explanation:
 
@@ -101,18 +112,13 @@ and starts it with `--start`.
 
 If the user wants a config example, show:
 
-```json
-{
-  "powerbi-modeling-mcp": {
-    "type": "stdio",
-    "command": "node",
-    "args": ["${CLAUDE_PLUGIN_ROOT}/bin/mcp/powerbi-modeling-launcher.js"]
-  },
-  "microsoft-learn": {
-    "type": "http",
-    "url": "https://learn.microsoft.com/api/mcp"
-  }
-}
+```toml
+[mcp_servers.powerbi-modeling-mcp]
+command = "node"
+args = ["<package-dir>/bin/mcp/powerbi-modeling-launcher.js"]
+
+[mcp_servers.microsoft-learn]
+url = "https://learn.microsoft.com/api/mcp"
 ```
 
 ### If the user installed the executable manually
@@ -126,9 +132,11 @@ BI_SUPERPOWERS_POWERBI_MODELING_MCP_PATH
 Then re-run:
 
 ```bash
-super mcp-setup
+super install --all --yes
 ```
 
+If they are intentionally maintaining a repo-local Claude Code plugin, they can run `super mcp-setup` inside that plugin project instead.
+
 ### If the user is on macOS or Linux
 
 Say:
@@ -143,15 +151,41 @@ For live editing of a local semantic model, you need a Windows environment.
 
 ---
 
-## PHASE 2: Verify Plugin Config
+## PHASE 2: Verify Agent MCP Config
 
 If the user chooses option 2:
 
+Check the config for the agent they use:
+
+- Claude Code: `~/.claude.json`
+- GitHub Copilot: `~/.copilot/mcp-config.json`
+- Codex: `~/.codex/config.toml`
+- Gemini CLI: `~/.gemini/settings.json`
+- Kilo Code: `~/.kilo/mcp_settings.json`
+
+Confirm:
+
+- skills are installed under the agent's user-level skill directory
+- config includes `powerbi-modeling-mcp`
+- config includes `microsoft-learn`
+
+If anything is missing, recommend:
+
+```bash
+super install --agent <agent-id> --yes
+```
+
+Then restart or refresh the agent.
+
+## PHASE 3: Verify Optional Local Claude Code Plugin Config
+
+If the user chooses option 3, or explicitly says they use `super kickoff` / `claude --plugin-dir`:
+
 Check these files in order:
 
 1. `.claude-plugin/plugin.json`
 2. `.mcp.json`
-3. `.bi-superpowers.json` if present
+3. `.bi-superpowers.json`
 
 Confirm:
 
@@ -180,7 +214,8 @@ claude --plugin-dir .
 | --- | --- |
 | Modeling MCP missing on Windows | Install the Microsoft extension in VS Code or Cursor |
 | Modeling MCP installed manually | Set `BI_SUPERPOWERS_POWERBI_MODELING_MCP_PATH` |
-| Plugin not loading MCPs | Re-run `bi-superpowers mcp-setup` and restart Claude Code |
+| Agent not loading MCPs | Re-run `super install --agent <agent-id> --yes` and restart the agent |
+| Local Claude Code plugin not loading MCPs | Re-run `super mcp-setup` inside the plugin project and restart Claude Code |
 | macOS/Linux local modeling request | Use `microsoft-learn` for docs; live editing requires Windows |
 | User asks about Excel MCP | Explain Excel remains supported through skills and library content, not a default MCP |
 
@@ -192,7 +227,8 @@ claude --plugin-dir .
 | --- | --- | --- |
 | Recommend `uvx` for Modeling MCP | Not the official Microsoft installation path | Use the official executable via the local launcher |
 | Ask the user to find a localhost port | Not required in the new flow | Use the official Modeling MCP launcher |
-| Put plugin MCP config in `.claude/settings.json` first | Plugin-first flow uses `.mcp.json` | Prefer `.mcp.json` at the plugin root |
+| Run `super kickoff` for Codex/GitHub Copilot/Gemini/Kilo setup | `kickoff` creates repo-local Claude Code plugin files | Use `super install --agent <agent-id> --yes` |
+| Treat `.mcp.json` as the default install target | It is only for optional local Claude Code plugins | Use the agent's user-level MCP config |
 | Invent unofficial MCPs (remote, fabric, etc.) | This plugin only ships 2 official MCPs | Only use the 2 official MCPs we ship (`powerbi-modeling-mcp` and `microsoft-learn`) |
 
 ---

package/skills/pbi-connect/scripts/update-check.js

@@ -47,7 +47,7 @@ const HTTPS_TIMEOUT_MS = 5000;
 // Rewritten at generation time when this helper is copied into
 // `skills/<name>/scripts/update-check.js`. In the canonical source under
 // `bin/commands/`, it stays null and we fall back to package.json.
-const BUNDLED_INSTALLED_VERSION = "4.1.3";
+const BUNDLED_INSTALLED_VERSION = "4.1.4";
 
 // ---------------------------------------------------------------------------
 // Argument parsing

package/skills/project-kickoff/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: "project-kickoff"
 description: "Use when the user asks about Project Kickoff Skill, especially phrases like \"I'm starting a brand-new BI project from scratch\", \"analizar proyecto\", \"analyze project\", \"project kickoff\", \"nuevo proyecto\", \"new project\"."
-version: "4.1.3"
+version: "4.1.4"
 ---
 
 <!-- Generated by BI Agent Superpowers. Edit src/content/skills/project-kickoff.md instead. -->

package/skills/project-kickoff/scripts/update-check.js

@@ -47,7 +47,7 @@ const HTTPS_TIMEOUT_MS = 5000;
 // Rewritten at generation time when this helper is copied into
 // `skills/<name>/scripts/update-check.js`. In the canonical source under
 // `bin/commands/`, it stays null and we fall back to package.json.
-const BUNDLED_INSTALLED_VERSION = "4.1.3";
+const BUNDLED_INSTALLED_VERSION = "4.1.4";
 
 // ---------------------------------------------------------------------------
 // Argument parsing

package/skills/report-design/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: "report-design"
 description: "Use when the user asks about Report Design Skill, especially phrases like \"crear reportes\", \"armar el reporte\", \"diseñar reporte\", \"report design\", \"create reports\", \"build dashboard\"."
-version: "4.1.3"
+version: "4.1.4"
 ---
 
 <!-- Generated by BI Agent Superpowers. Edit src/content/skills/report-design.md instead. -->

package/skills/report-design/scripts/update-check.js

@@ -47,7 +47,7 @@ const HTTPS_TIMEOUT_MS = 5000;
 // Rewritten at generation time when this helper is copied into
 // `skills/<name>/scripts/update-check.js`. In the canonical source under
 // `bin/commands/`, it stays null and we fall back to package.json.
-const BUNDLED_INSTALLED_VERSION = "4.1.3";
+const BUNDLED_INSTALLED_VERSION = "4.1.4";
 
 // ---------------------------------------------------------------------------
 // Argument parsing

package/src/content/base.md

@@ -142,7 +142,7 @@ AI Assistant → microsoft-learn HTTP MCP → learn.microsoft.com docs
 
 ### Practical guidance
 
-- Prefer `.mcp.json` in the plugin root over tool-specific MCP config files.
+- Prefer user-level agent MCP config files written by `super install`. Use project-root `.mcp.json` only when the user explicitly uses an optional local Claude Code plugin.
 - Never invent or hardcode local ports for the official Modeling MCP flow.
 - On macOS/Linux, explain that the local Modeling MCP is unavailable and fall back to `microsoft-learn` for docs. Live editing of a local model requires Windows.
 

package/src/content/routing.md

@@ -52,7 +52,7 @@ Scan current directory for relevant files:
 |----------------|-----------------|
 | `.pbix` / `.pbip` / `.tmdl` files | `/project-kickoff` (if not analyzed) |
 | `.xlsx` / `.xlsm` files | `/project-kickoff` |
-| No plugin `.mcp.json` found when user asks about Power BI | `/pbi-connect` |
+| Agent MCP config missing when user asks about Power BI | `/pbi-connect` |
 
 ### 4. CHECK KEYWORDS
 

package/src/content/skills/bi-start.md

@@ -49,7 +49,7 @@ Interpret the single-line output:
     ```bash
     super upgrade
     ```
-    After it finishes, remind: _"Si instalaste skills en el perfil del agente, corré `super install --yes`. Si además usás un plugin local generado con `super kickoff`, corré `super recharge` dentro de ese repo."_
+  After it finishes, remind: _"Corré `super install --all --yes` para refrescar la instalación user-level de todos los agentes. Solo si además mantenés un plugin local de Claude Code generado con `super kickoff`, corré `super recharge` dentro de ese repo."_
 
   On `no` — respect it, continue to PHASE 1 silently. The update-state.json already tracks the user's snooze per `update-check.js` semantics.
 
@@ -80,7 +80,7 @@ Do these detections in order:
    ```
    (or equivalent). `$pbiDesktopRunning = true` if present.
 
-4. **MCP configured**: look for `.mcp.json` in project root OR `powerbi-modeling-mcp` entry in the agent's config file (`~/.claude.json`, `~/.codex/config.toml`, etc). Keep the check shallow — no need to deep-diff.
+4. **MCP configured**: look first for `powerbi-modeling-mcp` in the agent's user-level config file (`~/.claude.json`, `~/.codex/config.toml`, etc). Only check project-root `.mcp.json` when the user explicitly says they use a local Claude Code plugin. Keep the check shallow — no need to deep-diff.
 
 ### Emit the context in 3-4 lines max
 
@@ -174,7 +174,7 @@ Stop. Don't hover. The user will tell you what they want next.
 - **Project analysis or setup**: that's `/project-kickoff`. If the user says "analizar mi proyecto", "armar el modelo base", "arrancar uno nuevo desde cero", delegate.
 - **MCP wiring details**: that's `/pbi-connect`. bi-start just offers to dispatch it; the actual configuration work is in that skill.
 - **Report authoring**: that's `/report-design`. Same pattern.
-- **Running the update**: bi-start offers + dispatches `super upgrade`; the actual refresh path after eso (`/plugin update bi-superpowers`, `super install --yes`, o `super recharge`) is owned by `/bin/cli.js`.
+- **Running the update**: bi-start offers + dispatches `super upgrade`; the actual refresh path after eso (`/plugin update bi-superpowers`, `super install --all --yes`, o `super recharge` only for local Claude Code plugins) is owned by `/bin/cli.js`.
 
 ## Related Skills
 

package/src/content/skills/pbi-connect.md

@@ -9,10 +9,10 @@ Activate this skill when user mentions:
 - "can't connect to Power BI", "connection error", "MCP not working"
 
 ## Identity
-You are a **Power BI MCP Connection Specialist**. Your job is to help the user connect their AI agent to Power BI Desktop using the official Microsoft MCP servers shipped with bi-superpowers, with a plugin-first workflow.
+You are a **Power BI MCP Connection Specialist**. Your job is to help the user connect their AI agent to Power BI Desktop using the official Microsoft MCP servers shipped with bi-superpowers, with a user-level install workflow that works across projects.
 
 ## MANDATORY RULES
-1. **PLUGIN-FIRST.** Prefer `.mcp.json` in the Claude Code plugin root.
+1. **USER-LEVEL FIRST.** Prefer `super install --all --yes` or `super install --agent <agent> --yes`; this installs skills and MCP config under the user's home directory and applies across projects. `.mcp.json` is only for an optional repo-local Claude Code plugin.
 2. **OFFICIAL SERVERS ONLY.** Use `powerbi-modeling-mcp` (local) and `microsoft-learn` (HTTP). Do not invent or recommend unofficial MCPs.
 3. **WINDOWS LIMITATION.** Explain clearly that the local Modeling MCP is only available on Windows.
 4. **NO PORT INVENTION.** Do not suggest local port-based setups for the official Modeling MCP flow.
@@ -33,7 +33,8 @@ I'll help you connect your AI agent using the official Microsoft MCP servers.
 What do you need?
 
 1. Connect to Power BI Desktop on this machine (Windows)
-2. Verify that my plugin `.mcp.json` is configured correctly
+2. Verify that my agent MCP config is installed correctly
+3. Verify an optional local Claude Code plugin `.mcp.json`
 ```
 
 ---
@@ -56,11 +57,21 @@ Before we continue:
 
 ### If the user is on Windows and installed the extension
 
-Guide them to:
+Guide them to the user-level install:
 
-1. Run `bi-superpowers mcp-setup`
-2. Confirm `.mcp.json` contains `powerbi-modeling-mcp`
-3. Restart or refresh Claude Code
+1. Run `super install --all --yes`, or for one agent run `super install --agent codex --yes` / `super install --agent claude-code --yes` / etc.
+2. Confirm the agent config contains `powerbi-modeling-mcp` and `microsoft-learn`.
+3. Restart or refresh the AI agent so it reloads skills and MCP servers.
+
+Use these config locations:
+
+| Agent | Skill path | MCP config |
+| --- | --- | --- |
+| Claude Code | `~/.claude/skills` or `~/.agents/skills` | `~/.claude.json` |
+| GitHub Copilot | `~/.copilot/skills` | `~/.copilot/mcp-config.json` |
+| Codex | `~/.agents/skills` | `~/.codex/config.toml` |
+| Gemini CLI | `~/.gemini/skills` | `~/.gemini/settings.json` |
+| Kilo Code | `~/.kilo/skills` | `~/.kilo/mcp_settings.json` |
 
 Use this explanation:
 
@@ -72,18 +83,13 @@ and starts it with `--start`.
 
 If the user wants a config example, show:
 
-```json
-{
-  "powerbi-modeling-mcp": {
-    "type": "stdio",
-    "command": "node",
-    "args": ["${CLAUDE_PLUGIN_ROOT}/bin/mcp/powerbi-modeling-launcher.js"]
-  },
-  "microsoft-learn": {
-    "type": "http",
-    "url": "https://learn.microsoft.com/api/mcp"
-  }
-}
+```toml
+[mcp_servers.powerbi-modeling-mcp]
+command = "node"
+args = ["<package-dir>/bin/mcp/powerbi-modeling-launcher.js"]
+
+[mcp_servers.microsoft-learn]
+url = "https://learn.microsoft.com/api/mcp"
 ```
 
 ### If the user installed the executable manually
@@ -97,9 +103,11 @@ BI_SUPERPOWERS_POWERBI_MODELING_MCP_PATH
 Then re-run:
 
 ```bash
-super mcp-setup
+super install --all --yes
 ```
 
+If they are intentionally maintaining a repo-local Claude Code plugin, they can run `super mcp-setup` inside that plugin project instead.
+
 ### If the user is on macOS or Linux
 
 Say:
@@ -114,15 +122,41 @@ For live editing of a local semantic model, you need a Windows environment.
 
 ---
 
-## PHASE 2: Verify Plugin Config
+## PHASE 2: Verify Agent MCP Config
 
 If the user chooses option 2:
 
+Check the config for the agent they use:
+
+- Claude Code: `~/.claude.json`
+- GitHub Copilot: `~/.copilot/mcp-config.json`
+- Codex: `~/.codex/config.toml`
+- Gemini CLI: `~/.gemini/settings.json`
+- Kilo Code: `~/.kilo/mcp_settings.json`
+
+Confirm:
+
+- skills are installed under the agent's user-level skill directory
+- config includes `powerbi-modeling-mcp`
+- config includes `microsoft-learn`
+
+If anything is missing, recommend:
+
+```bash
+super install --agent <agent-id> --yes
+```
+
+Then restart or refresh the agent.
+
+## PHASE 3: Verify Optional Local Claude Code Plugin Config
+
+If the user chooses option 3, or explicitly says they use `super kickoff` / `claude --plugin-dir`:
+
 Check these files in order:
 
 1. `.claude-plugin/plugin.json`
 2. `.mcp.json`
-3. `.bi-superpowers.json` if present
+3. `.bi-superpowers.json`
 
 Confirm:
 
@@ -151,7 +185,8 @@ claude --plugin-dir .
 | --- | --- |
 | Modeling MCP missing on Windows | Install the Microsoft extension in VS Code or Cursor |
 | Modeling MCP installed manually | Set `BI_SUPERPOWERS_POWERBI_MODELING_MCP_PATH` |
-| Plugin not loading MCPs | Re-run `bi-superpowers mcp-setup` and restart Claude Code |
+| Agent not loading MCPs | Re-run `super install --agent <agent-id> --yes` and restart the agent |
+| Local Claude Code plugin not loading MCPs | Re-run `super mcp-setup` inside the plugin project and restart Claude Code |
 | macOS/Linux local modeling request | Use `microsoft-learn` for docs; live editing requires Windows |
 | User asks about Excel MCP | Explain Excel remains supported through skills and library content, not a default MCP |
 
@@ -163,7 +198,8 @@ claude --plugin-dir .
 | --- | --- | --- |
 | Recommend `uvx` for Modeling MCP | Not the official Microsoft installation path | Use the official executable via the local launcher |
 | Ask the user to find a localhost port | Not required in the new flow | Use the official Modeling MCP launcher |
-| Put plugin MCP config in `.claude/settings.json` first | Plugin-first flow uses `.mcp.json` | Prefer `.mcp.json` at the plugin root |
+| Run `super kickoff` for Codex/GitHub Copilot/Gemini/Kilo setup | `kickoff` creates repo-local Claude Code plugin files | Use `super install --agent <agent-id> --yes` |
+| Treat `.mcp.json` as the default install target | It is only for optional local Claude Code plugins | Use the agent's user-level MCP config |
 | Invent unofficial MCPs (remote, fabric, etc.) | This plugin only ships 2 official MCPs | Only use the 2 official MCPs we ship (`powerbi-modeling-mcp` and `microsoft-learn`) |
 
 ---