MCP: dashboard-get fails when tile has null insight (text tiles)
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 7h 27m
- Merged PRs (30d)
- 222
Description
Bug
dashboard-get tool fails with a validation error when a dashboard contains a text tile (or any tile where insight is null).
Reproduction
- Create a dashboard with a text tile (header/description)
- Call
dashboard-getwith that dashboard ID via MCP
Error
Response validation failed on GET .../dashboards/1280858/:
[{
"code": "invalid_type",
"expected": "object",
"received": "null",
"path": ["tiles", 0, "insight"],
"message": "Expected object, received null"
}]
Expected
The tool should handle tiles with null insight (text tiles, placeholder tiles) gracefully — either skip them or return them with insight: null.
Context
- MCP endpoint:
https://mcp.posthog.com/mcp - Tool:
dashboard-get - The API response itself is valid (response keys include
tiles), but the MCP tool's Zod schema rejects it because it expectsinsightto always be an object.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the dashboard-get MCP tool and the response Zod schema that validates dashboard tiles, then reproduce the failure with a text tile or another tile whose insight is null. Trace the tiles.insight validation and confirm the tool accepts null while continuing to validate ordinary insight objects.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100