MCP & agent integration
Checking your session…
Sign in to read this guide
This guide walks through connecting Claude Code or Cursor to your workspace. Sign in with your Observant login to read it.
Check your email — we sent you a sign-in link. It brings you straight back to this guide.
Observant's MCP server lets Claude Code, Cursor, or any MCP client pull what Observant has learned from your users into a coding or planning session — mid-task, without opening a dashboard. It's authenticated and scoped to your workspace.
1. Get your API key
API keys are created in the Observant engine console at engine.observanthq.com. Sign in with your workspace login and create an API key — keys start with cdf_. Each key belongs to your workspace and only ever reads your workspace's data.
2. Connect your client
Claude Code
https://www.observanthq.com/api/mcp works too — it redirects to the same server.
Cursor & other MCP clients
Add an HTTP MCP server pointed at https://engine.observanthq.com/mcp with an Authorization: Bearer cdf_YOUR_KEY header. That's the whole setup — no local install.
3. The tools
Once connected, your agent can call five tools:
| Tool | What it does | Example prompt |
|---|---|---|
| observant_recent_feedback | The latest replies from your feedback partners | "What came in from users this week?" |
| observant_conversations | Full 1:1 threads, every turn, contacts masked | "Show me the full conversation behind that pricing complaint." |
| observant_insights | Your standing insight cards — the patterns Observant has already synthesized | "What are the current top insights for onboarding?" |
| observant_search_transcripts | Keyword search across everything users have said | "Search the transcripts for mentions of the export button." |
| observant_ask | A grounded answer to a specific question — same engine as the dashboard's Ask | "Ask Observant: do users understand what the free tier includes?" |
Try it
Connected in Claude Code, mid-session:
The answer lands in the same session, so your agent can fold what users actually said straight into the plan or the code it's writing.
Security
- Workspace-scoped keys — every key is tied to one workspace and reads only that workspace's data.
- Cross-workspace isolation — no key can see another workspace, and every request is checked against the key's workspace.
- Masked contacts — email addresses and handles are masked in everything the MCP returns; your agent sees the words, not the contact details.
Questions about your setup? Get in touch — we'll walk it with you.