How to connect with MCP in Copilot
Connect GitHub Copilot to your DashThis account with MCP so you can ask about your dashboards inside your code editor.
This guide shows you how to connect Copilot to your DashThis account using the MCP Connector. Once connected, you can ask about your dashboards and get answers from your live reporting data.
Copilot covers two different product families, and they do not behave the same way. GitHub Copilot runs in your code editor on your own machine, and it connects to DashThis. Microsoft 365 Copilot runs on Microsoft's servers, and most of it cannot connect yet. The list below tells you which one you have.
Before you start
- You sign in with your usual DashThis credentials during setup.
- The DashThis address you use everywhere below is https://mcp.dashthis.com/mcp
Which Copilot products work
GitHub Copilot
- 🟢Visual Studio Code, in Copilot Chat agent mode: works.
- 🟢Visual Studio 17.14 and later: works.
- 🟢GitHub Copilot CLI: works, but only from a terminal window you are typing in.
- 🟢JetBrains, Eclipse and Xcode: expected to work the same way, but we have not tested them yet. Let us know how it goes.
- 🔴Copilot coding agent and Copilot code review: not supported. They do not work with MCP connectors that ask you to sign in.
- 🔴Copilot Chat on github.com and Windows Copilot: not available. There is no place to add a custom MCP connector.
Microsoft 365 Copilot
- 🟢Copilot Studio, in Dynamic discovery mode: expected to work, but we have not tested it yet.
- M365 declarative agents with dynamic OAuth: not confirmed yet. We are still testing this one.
- 🔴Copilot Studio in Manual mode, M365 federated connectors, M365 declarative agents with static OAuth, and Security Copilot: not supported. They ask for a type of credential DashThis does not issue, for security reasons.
Connect Visual Studio Code
- Add this entry to your .vscode/mcp.json file, or to the same setting in your user profile: { "servers": { "dashthis": { "type": "http", "url": "https://mcp.dashthis.com/mcp" } } }
- Open Copilot Chat in agent mode. VS Code asks you to authorize the server.
- Sign in to DashThis in your browser and approve access.
Connect Visual Studio 17.14 and later
- Add the DashThis server using the same address.
- Choose Dynamic Client Registration when Visual Studio asks you for a registration method.
- Sign in to DashThis and approve access.
Visual Studio then asks you to allow each tool before it runs. That prompt comes from Visual Studio, not from DashThis, and it is normal.
Connect GitHub Copilot CLI
- Open a real terminal window and start Copilot CLI there.
- Add the DashThis server using the same address.
- Approve the sign-in prompt when your browser opens.
Copilot CLI fails silently in scripts
Run Copilot CLI from a terminal window you are typing in. If you run it from a script, it skips the browser sign-in step and marks the DashThis server as unusable, without showing a clear error.
If a run looks wrong, check your Copilot CLI logs before assuming the connector is broken.
What Copilot can see
Copilot can only read the dashboards on the DashThis account you connected, and the connection is read-only, so it cannot change anything in DashThis. For the full list of what the connector can and cannot do, see MCP notes and limitations.
Need help connecting Copilot?
Contact our Support Team here 💪🏼
What's next?