MCP
Ready for your agentic workflow.
Observant installs as an MCP server over HTTP — right inside Claude Code, Cursor, or Claude Desktop, for teams who ship in the editor. User learning runs on autopilot and shows up where you build: surfaced in the flow, agent-ready.
Create an API key in your Observant dashboard, then run this in your editor:
$
claude mcp add --transport http observant https://www.observanthq.com/api/mcp
Authenticated and scoped to your workspace: connect with your API key and your editor sees only your own users' feedback. Cursor & Claude Desktop: point an HTTP MCP server at the same URL. Key setup & connection guide →
›why are power users dropping the new export flow?
⏺ observant pulling from your panel…
↳ triggered by PostHog · 22% drop-off on export_v2 · cohort: Power users
↳ 18 recent 1:1s matched · synthesizing
›draft the implementation plan
Insight · agent-ready
61% rebuild the export by hand to get a shareable view. The CSV-first flow is the friction — not the export itself.
→ recommend: ship a live, shareable dashboard; keep CSV as secondary
No dashboard, no context-switch — the insight arrives where you're already building.
Closed loop
From a signal to a shipped fix — without leaving your editor.
Detect
PostHog spots it
A drop-off or behavior change fires the trigger.
Learn
Observant runs the 1:1s
Real conversations with the exact users affected.
Synthesize
Proactively, not on ask
Observant surfaces the pattern before you think to query it.
Implement
Your agent ships it
Agent-ready insight → spec → code, in the same session.