Skip to main content
Observerbee ships a remote Model Context Protocol server. Any MCP client can read your friction findings, journeys, screens, session evidence and task specs. Clients that support the MCP Apps extension (Claude, ChatGPT, Cursor, VS Code Copilot, Goose) also render interactive views inside the conversation: a findings board, an insight card with next steps, a journey rail, a screen inspector, a task spec review and the approval queue.

Claude and ChatGPT

Connect with OAuth. Ask what is hurting checkout, open a finding, dispatch it to your engineer agent and approve the pull request without leaving the chat.

Claude Code, Codex and Cursor

Connect with an MCP token. Pull an agent-ready task spec, implement it, and verify the fix against production data.

​
What the server exposes

Human decisions (review_action_request, set_task_spec_status, promote_insight_to_triage, request_implementation, set_insight_status) are only callable from the views. The model can describe them but never trigger them; a person clicks. Every decision made through an assistant is attributed to the signed-in member and written to the same accountability trail as the dashboard.

​
Resources and prompts

  • observerbee://task-specs/{id} and observerbee://insights/{id}: Markdown documents for clients that attach context instead of calling tools.
  • fix_friction: a guarded implementation brief for a coding agent, ending with a verify_fix step.
  • triage_findings: ranks a project’s open findings and proposes which to turn into specs.