You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/guides/posthog-github-continuous-ai.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -128,7 +128,7 @@ You only need to configure the PostHog MCP credential - it automatically handles
128
128
organization
129
129
- It automatically uses your default project (no project ID
130
130
needed)
131
-
- If you have multiple projects, use `mcp__posthog__switch-project` to
131
+
- If you have multiple projects, use `switch-project` to
132
132
change
133
133
- The MCP connects via `https://mcp.posthog.com/sse` using your account context.
134
134
@@ -300,7 +300,7 @@ The main workflow above focuses on analyzing session recordings to identify UX i
300
300
301
301
```bash
302
302
# Get all feature flags and analyze them
303
-
cn "Use PostHog MCP to fetch all feature flags with mcp__posthog__feature-flag-get-all. Then analyze each flag to identify: 1) Flags that are 100% rolled out and could be removed, 2) Flags that haven't been updated in 90+ days, 3) Flags with complex targeting that might need simplification, 4) Experimental flags that should be cleaned up."
303
+
cn "Use PostHog MCP to fetch all feature flags with feature-flag-get-all. Then analyze each flag to identify: 1) Flags that are 100% rolled out and could be removed, 2) Flags that haven't been updated in 90+ days, 3) Flags with complex targeting that might need simplification, 4) Experimental flags that should be cleaned up."
304
304
305
305
# Create cleanup issues for identified flags
306
306
cn "For each problematic feature flag identified, create a GitHub issue using gh CLI:
0 commit comments