MCP notes/limitations
What to know before you rely on the MCP Connector, including what data it can reach and its current limits.
The MCP Connector brings your reporting into an AI conversation, and there are a few things to know about what it can and cannot do.
What data is available
- Dashboard data only. The connector reads what is already on your dashboards. It does not go back to your connected platforms for anything that is not in a widget.
- Current values, by period. The connector returns the current values of your widgets for a reporting period you choose, and it can compare against the previous period or the previous year.
- How your dashboard is built. Your assistant can ask which widgets a dashboard holds, which sources feed them, and which periods it covers. Deleted sources are left out, so it will never name a source you no longer have
- Your comments. Text from comment widgets comes back with the numbers, so your assistant can build on the recap you already wrote instead of starting from scratch. If your commentary is saved per period, your assistant also knows which period it was written for, so it will not reuse an older note.
Read-only
The current MCP implementation is read-only. The connected AI assistant can view your dashboards and their values, but it cannot create, edit, or delete anything in DashThis. Your dashboards and data are never changed.
Current limitations
- Widgets that carry no readable metric. Most widgets return their values through MCP. A few still do not, because there is no metric value for the connector to read: headings, and widgets whose display format shows no metric. Your assistant is told when a widget cannot be read and why, so it will not report that widget as empty. Nothing changes in your dashboard, which displays normally.
- Dashboards and widgets with no title. A dashboard or a widget you never named is still read normally, and your assistant refers to it as “Untitled dashboard” or “Untitled widget.” If you have several untitled items, give them names so your assistant can tell them apart when it answers.
- Periods. If you do not ask for a period, your assistant uses the dashboard's own reporting period, so the numbers match what you see in DashThis. You can also ask for another one: a month, a quarter, a year, a single day, or a preset such as last 7 days, last 30 days, this month, last month, this year or last year. A period you name has to be one the dashboard actually reports on, since a dashboard's month is not always a calendar month, and when it is not, your assistant is told which periods it can ask for instead. For any other window, ask for exact dates, like January 1 to January 31, 2026. Two limits apply: nothing is read past yesterday, and exact dates reach back two years, the same as a dashboard's own date picker.
- Dashboard PDFs. Your assistant can turn a dashboard into a PDF and give you a link to it. The link works for one hour, so save the file if you want to keep it. The PDF always covers the dashboard's own reporting period. Change the period in DashThis first if you need another one.
- Usage limits. To keep the connector fast for everyone, there are fair-use limits on how often and how much it reads at once.
- Staying connected. Your connection lasts one hour and refreshes on its own while you keep using the assistant. After 14 days without use, you sign in and approve access again.
- Very large dashboards. Your assistant reads big dashboards in batches, behind the scenes. Very long widget tables may be shortened, so you may not see every row. You still get one combined answer.
Need help with the MCP Connector?
Contact our Support Team here 💪🏼
What's next?