Connect PostHog once. Your agent reads product events and usage on the unified profile—identity-resolved with your CRM, support, email, and website events—through one MCP server.
{
"mcpServers": {
"pathbound": {
"url": "https://mcp.pathbound.ai/mcp"
}
}
}…plus many more—more than 100 MCP tools in total, across contacts, companies, deals, events, and conversations.
Sign in with PostHog or paste a Personal API key. Drop a snippet into your MCP client. Ask a question.
Create an account at pathbound.ai. Every plan starts with 14 days free, no card.
In the dashboard, go to Integrations → PostHog → Connect. Sign in with PostHog, or paste a PostHog Personal API key with read access to persons, queries, and projects; Pathbound finds your project. Sync pulls persons and product events and resolves them to the unified contact by distinct_id and email.
Drop the snippet below into your Claude Desktop config (or in Claude.ai web: Customize → Connectors → Add custom connector → enter https://mcp.pathbound.ai/mcp). The same URL works for ChatGPT, Cursor, Cline, and any MCP client that supports OAuth.
{
"mcpServers": {
"pathbound": {
"url": "https://mcp.pathbound.ai/mcp"
}
}
}Ask the agent: “How many product events did [email protected] fire this week?” The agent calls list_events via MCP and returns the count.
A direct PostHog connector shows your agent product events. Pathbound shows your agent the customer—PostHog events stitched together with your CRM, support, email, and website events—through one unified profile served over the Model Context Protocol.
Feature usage and activation events land on the same timeline as deal stage, support tickets, and emails. Your agent sees what they did in the product next to everything else—not in a separate analytics tab.
A PostHog person (distinct_id, email) resolves to the same unified contact you have in your CRM, Gmail, and website events. A direct connector only knows PostHog’s own IDs.
PostHog powers your product team’s dashboards; Pathbound puts the same events on the contact profile your AI agent (and your AE or CSM) reads before the next action. Different consumers, same source.
Token-efficient response shapes and server-side aggregation mean agents get usage summaries and counts, not a raw event firehose that blows the context window.
Pathbound is an independent platform. We connect to PostHog via its API using a key you generate, and expose your data through one Model Context Protocol server alongside your other sources. Not affiliated with PostHog.
No. The PostHog integration is read-only—it pulls persons and product events into the unified profile and never writes anything back to PostHog.
PostHog is product analytics for your team’s dashboards and queries. Pathbound puts the same events on the per-contact profile your AI agent, AE, or CSM reads before the next action—identity-resolved with your CRM, email, and support. Different consumers, same source.
By identity resolution on distinct_id and email. A person’s product behavior lands on the same unified profile as their CRM record, conversations, and web activity.
Claude.ai, Claude Desktop, Claude Code, ChatGPT (with custom connectors), Cursor, Cline, Continue—any client that supports the Model Context Protocol with OAuth.
Tenant-isolated and OAuth-scoped per user, with connection credentials encrypted at the application layer. Pathbound does not sell customer data, and we don’t call AI providers on your behalf—your MCP client does, under your account and the AI provider’s terms.
Same MCP server, same tools—just connect a different source. See the integrations directory.
Sign up, connect one CRM or drop the events snippet, and point your MCP client at mcp.pathbound.ai/mcp.