Skip to content

feat(third_party): add PostHog MCP plugin (posthog-mcp) - #437

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

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

Conversation

@minupalaniappan

@minupalaniappan minupalaniappan commented Sep 25, 2026 •

Copy link
Copy Markdown
Collaborator

What this adds

Re-lists the URL-only PostHog connector (removed in #436) as posthog-mcp / "PostHog MCP". Same content as #431: mcp.json → https://mcp.posthog.com/mcp, README, changelog, MIT license, PostHog favicon logo. Linear PGT-4565.

Why a new name

PostHog publishes its own APPROVED plugin as posthog (id 730, from PostHog/ai-plugin, with bundled skills/commands/hooks). Two APPROVED plugins sharing a name collide in the indexer (the Coinbase stale-draft failure), so this one ships under posthog-mcp. The README states it is the URL-only connector and that users should install one or the other, not both.

Auth verification

Unchanged from #431: anonymous POST /mcp → 401 with resource_metadata; AS oauth.posthog.com with PKCE S256 + DCR; DCR returned 201 for every redirect set Cursor and Grok send, including Grok Bot mobile and grok.com.

What to review

  • The MCP server key inside mcp.json stays posthog (that is the name clients show for the connection); only the plugin name/dir/display name changed. Flag if you want the server key renamed too.
  • Real review question: do we want both PostHog cards visible in Grok Bot, or should this one carry Grok-Bot-only gating (cursor: "never") so Cursor users keep seeing only the vendor plugin?
  • node scripts/validate-plugins.mjs passes for all plugins.

Out of scope

grok.com catalog connector; hosted SERVER placement check after publish; account-based sign-in test (draft until then).


Note

Low Risk
Marketplace and connector metadata only; no changes to core plugin runtime or auth beyond pointing clients at PostHog’s hosted endpoint.

Overview
Adds a new marketplace plugin posthog-mcp / PostHog MCP under third_party/posthog-mcp, re-listing the URL-only connector to PostHog’s hosted MCP at https://mcp.posthog.com/mcp (OAuth; no bundled skills/commands).

Registers the plugin in .cursor-plugin/marketplace.json with metadata, mcp.json, README (capabilities and install notes), changelog (name chosen to avoid indexer collision with PostHog’s vendor posthog plugin), and MIT license. The MCP server key in config remains posthog while the plugin id is posthog-mcp.

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

Re-adds the URL-only PostHog connector removed in #436 under the name posthog-mcp / PostHog MCP. The bare posthog name belongs to PostHog's own approved marketplace plugin (id 730), and two APPROVED plugins with one name collide in the indexer. Same server (https://mcp.posthog.com/mcp), same OAuth via oauth.posthog.com with PKCE + DCR verified for every Cursor redirect set incl. Grok Bot mobile.
@minupalaniappan
minupalaniappan marked this pull request as ready for review September 25, 2026 22:02
@minupalaniappan
minupalaniappan merged commit 14253df into main Sep 25, 2026
2 checks passed
theacrat pushed a commit to theacrat/pstack-generic that referenced this pull request Sep 26, 2026
Same fix as cursor#438 for the PostHog MCP plugin; the field was pushed to the cursor#437 branch after that PR merged.
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