Skip to content

Add preferred PostHog MCP OAuth connection #409

Description

@neubig

Context\n\nOSS KPI monitoring needs PostHog to be easy to connect from OpenHands through the public extensions integration catalog. A PostHog catalog entry already exists, but it only exposes the personal API key fallback even though PostHog now recommends OAuth for its hosted MCP server.\n\n## Proposed work\n\n- Add a preferred OAuth MCP connection option for PostHog.\n- Keep the bearer-token personal API key fallback for clients that cannot complete OAuth.\n- Use safe read-only defaults for inspection workflows and document when write access should be explicitly approved.\n- Add focused validation so future catalog changes do not regress the PostHog MCP connection.\n

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions