Skip to content

posthog-mcp: declare server placement (1.0.1) - #439

Merged
minupalaniappan merged 1 commit into
mainfrom
minu/posthog-mcp-placement
Sep 25, 2026
Merged

minupalaniappan merged 1 commit into
mainfrom
minu/posthog-mcp-placement

Conversation

@minupalaniappan

@minupalaniappan minupalaniappan commented Sep 25, 2026 •

Copy link
Copy Markdown
Collaborator

Same change as #438 for the PostHog MCP plugin: adds "placement": "server" to its MCP entry so Grok Bot dials it through the hosted path, bumps to 1.0.1, changelog line. The field had been pushed to the #437 branch after that PR merged, so it never reached main. Validator passes.


Note

Low Risk
Plugin metadata and version bump only; no runtime or auth logic changes.

Overview
PostHog MCP is bumped to 1.0.1 with a small MCP manifest change so Grok Bot routes the connector correctly.

The posthog HTTP MCP entry in mcp.json now includes "placement": "server", telling clients to use the hosted MCP path instead of treating the server as undecided. The changelog documents this for the release; plugin.json version is updated to match.

Reviewed by Cursor Bugbot for commit 5e58f15. Bugbot is set up for automated code reviews on this repo. Configure here.

Same fix as #438 for the PostHog MCP plugin; the field was pushed to the #437 branch after that PR merged.
@minupalaniappan
minupalaniappan merged commit ecc249f into main Sep 25, 2026
2 checks passed
github-actions Bot added a commit to SmailG/claude-cursor-plugins that referenced this pull request Sep 26, 2026
…cursor/minu/posthog-mcp-placement

chore: sync with cursor/plugins — Merge pull request cursor#439 from cursor/minu/posthog-mcp-placement
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant