Connecting and Context (Desktop + Service)
Good outcomes depend on two things:
- the MCP server is connected to the right model/dataset, and
- the assistant’s mental model matches reality (fresh metadata, correct assumptions).
This page gives you a reliable “connect → confirm → proceed” workflow.
UI support (supported clients)
Some clients can show a dedicated connection UI for choosing Desktop models or Service datasets. If available, it’s often the fastest way to pick the right target.
Golden rule: don't auto-select
Prompt:
“List available models/datasets and ask me which one to connect to. Do not auto-select.”Desktop vs Service: how to decide
Use Desktop when…
- you’re working on a local PBIX in Power BI Desktop,
- you need local authoring workflows.
Expected user action:
- ensure the PBIX is open in Power BI Desktop.
Use Service when…
- you need to work against a dataset in Power BI Service,
- you want workspace-level context (shared baselines/governance),
- Desktop isn’t available.
Expected prerequisites:
- Service connectivity is enabled in your environment,
- the dataset is XMLA-capable (capacity/tenant settings),
- you are authenticated (if not, the assistant will guide you).
The connection workflow (recommended)
Discover
“List available models/datasets. Group by Desktop vs Service.”Choose intentionally
“Connect to: [exact model/dataset name] (and workspace, if Service).”If there are similar names: “Show IDs/unique identifiers and ask me which is correct.”
Confirm context before doing work
“Show what we’re currently connected to (Desktop vs Service, model name/id) and confirm it matches what I expect.”Keep metadata fresh
If you made changes outside the session (Power BI Desktop UI, Tabular Editor, Service changes):
“Reload model metadata; I changed the model outside this session.”
Common scenarios and prompts
“I’m not sure which model the report uses”
“List models/datasets and help me identify the correct one based on table/measure names I provide.”“I switched PBIX / reopened Desktop”
“Confirm connection is still valid. If not, reconnect to the correct Desktop model.”“I need workspace-scoped defaults”
“Connect to the dataset in the Service workspace we’re working in, then confirm workspace context is available.”Mode and governance awareness
Your org may run the MCP server in a restricted mode:
- Full: all features (subject to license).
- Read-only: browse/query/refresh; no model edits.
- Browse-only: discovery + schema browsing only.
Ask early:
“What mode is this server in, and what does that mean for what we can do?”Troubleshooting
Confirm Power BI Desktop is running and a PBIX is open. Then ask:
“Retry discovery and explain what you found.”Ask:
“Is Service (XMLA) enabled here? Do I need to authenticate? Is this workspace XMLA-capable?”Ask:
“Show the current connected model and explain why it differs. Then reconnect to the one I choose.”Common mistakes (avoid these)
Consultant checklist (handoff-friendly)
If you’re working with a customer/team, capture these in your notes:
- Desktop vs Service target
- Workspace name (Service) and dataset name
- What restrictions apply (full/read-only/browse-only; policy enforced?)
- Whether preferences/masking are enabled and any org-approved defaults