Remove XP/FF MCP beta tag (no slop edition) - #220
Conversation
- Updated docs/mcp.mdx Mintlify-Source: dashboard-editor
Confidence Score: 4/5The PR appears safe to merge, though the cohort-editing warning should be clarified to avoid contradicting the available-tools table. The changes are documentation-only; the sole accepted issue is a non-blocking ambiguity about whether cohort CRUD is supported. Files Needing Attention: docs/mcp.mdx
|
| Filename | Overview |
|---|---|
| docs/mcp.mdx | Removes MCP beta labels and cleans up formatting, but makes the existing cohort-capability contradiction less clearly scoped. |
Reviews (1): Last reviewed commit: "Updated mintlify pages" | Re-trigger Greptile
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
|
|
||
| <Warning> | ||
| **Experiments and Feature Flags tools are in open beta** and available to all users. Audience targeting and cohort editing are not yet supported via MCP — use the Mixpanel UI instead. | ||
| Audience targeting and cohort editing are not yet supported via MCP — use the Mixpanel UI instead. |
There was a problem hiding this comment.
The revised warning says cohort editing is unsupported, while the same page lists Create-Cohort, Update-Cohort, and Delete-Cohort as available tools. Removing the Experiments and Feature Flags context makes these capability statements contradictory, leaving readers unable to determine whether cohort CRUD is supported.
Source Used: Linear — Docs: MCP cohort support is described two different ways (beta callout vs tool table)
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
1 participant
Mintlify
0 threads from 0 users in Mintlify