Direct answer: PostHog's hosted MCP server exposes product analytics, SQL, dashboards, experiments, feature flags, error tracking, and other project tools. Finta's catalog uses PostHog's official endpoint with bearer authentication, which the provider supports through a personal API key using the MCP Server preset. A verified connection can help prepare investor-update evidence, but metric definitions and claims still require human review.
This guide is for teams using Finta as relationship intelligence around a capital, investor, customer, or company-building workflow. PostHog remains the source system for its records. Aurora can use only the context and actions exposed to the connected account.
How the PostHog connection works
| Connection detail | Current Finta guidance |
|---|---|
| Classification | Catalog MCP |
| Configured endpoint | https://mcp.posthog.com/mcp |
| Authentication and transport | User-supplied bearer or personal access token; Streamable HTTP |
| Source of truth | PostHog remains authoritative for provider records, permissions, and action results. |
| Human control | Review external communication, record changes, financial actions, publishing, deletion, and other consequential work before execution. |
What you can use it for
- Explore event, action, property, person, group, dashboard, insight, and schema context permitted by the PostHog project.
- Run provider-supported analytics, dashboard, or SQL queries for a defined metric and time window.
- Review experiments, feature flags, errors, surveys, or session-replay metadata when exposed by the selected tool set.
- Prepare metric evidence for an investor update with the query, project, period, and definition attached.
These uses summarize the current provider documentation and Finta catalog purpose. The exact tool inventory varies by provider version, plan, workspace, user permissions, region, and authorization scopes.
Relationship intelligence workflows for PostHog
Investor update metric evidence pack
Outcome: A small set of reproducible growth or engagement metrics with definitions, periods, and PostHog source context.
- Confirm the correct PostHog project, metric definition, cohort, and reporting window.
- Run the narrow provider-supported query and preserve the query or insight reference.
- Prepare the investor-update paragraph with caveats, comparison basis, and source links.
Human decision: A metric owner validates definitions, data quality, and every external claim.
Product diligence question review
Outcome: A source-backed answer to a specific investor question about adoption, retention, feature use, or product quality.
- Translate the investor question into a bounded metric, cohort, and time period.
- Retrieve the relevant schema, insight, experiment, error, or session evidence.
- Explain what the data supports, what it does not support, and which assumptions remain.
Human decision: Product and finance owners approve interpretation and disclosure before sharing.
How to connect PostHog to Aurora
- In PostHog, create a personal API key using the MCP Server preset for the intended project.
- In Aurora's Apps tray, select PostHog and enter the key through Finta's bearer credential flow.
- Prefer a project-pinned and read-only configuration for reporting workflows when Aurora supports those provider options.
- Discover the live tool set and restrict it to the analytics features needed for the page proof.
- Run one known read query and compare the result with the PostHog UI.
Open the official Finta apps directory to confirm the catalog entry before authorizing a provider account.
Permissions and approval boundary
PostHog exposes both read and write tools, and provider documentation warns about prompt injection. Use project-scoped credentials and read-only or filtered tool modes where possible. A human must approve queries that expose sensitive data and any dashboard, flag, experiment, survey, project, or customer-data mutation.
Limitations to understand
- Standard PostHog API limits and underlying product usage charges still apply.
- Some AI-powered tools require AI data processing to be enabled and can create PostHog AI spend.
- The provider has hundreds of tools, so tool filtering and project pinning are important for context and blast-radius control.
- Analytics results depend on implementation quality, identity resolution, event definitions, filters, and date windows.
Verification checklist
- Confirm https://mcp.posthog.com/mcp and bearer auth in the live catalog.
- Create a scoped MCP Server preset key without exposing it in logs or CMS content.
- Connect Aurora, discover tools, and confirm the intended PostHog project.
- Run one known read-only insight or schema query and compare it with PostHog.
- Test read-only or feature-filtered operation if the Aurora connector supports provider headers or query parameters.
- Have the metric owner validate the exact result before public copy claims an investor-update workflow.
Verification status: On 2026-08-22, Finta confirmed that this connector appears in the enabled production Aurora catalog and reviewed the configured endpoint, authentication type, and first-party sources listed below. This is not a claim that every provider tool or an authenticated end-to-end action has been tested for every account.
Official provider sources
- PostHog official MCP documentation (posthog.com)
- PostHog official MCP documentation 2 (posthog.com)
- PostHog official MCP documentation 3 (posthog.com)