earshot
← All docs

Cursor

Cursor talks to Earshot through the hosted MCP at https://mcp.earshotbot.com/mcp. Once configured, Cursor's chat agent can install the Earshot widget into your project, push project context, and triage feedback from inside the IDE.

1. Get a project key

  1. Sign in at app.earshotbot.com.
  2. Create a team (if you don't have one) and a project. Copy the pk_* key — Project Settings shows it once.

2. Wire Cursor to the MCP

Drop the following into .cursor/mcp.json in your repo (or ~/.cursor/mcp.json to enable it globally):

{
  "mcpServers": {
    "earshot": {
      "url": "https://mcp.earshotbot.com/mcp",
      "headers": {
        "Authorization": "Bearer pk_your_project_key"
      }
    }
  }
}

Reload MCP servers in Cursor (Settings → MCP → Reload). The earshot server should turn green with the available tools listed.

3. Drop the Cursor rules

Save the file below at .cursor/rules/earshot.mdc in your repo. It tells Cursor's agent when to call which Earshot tool (triage the inbox, push project context, mark resolved, etc.). The full reference lives in the Earshot skill source.

---
description: Earshot voice-first user feedback. Triage, resolve, push project context via MCP.
globs: "**/*"
alwaysApply: false
---

(See the linked file for the body — too long to inline, but it's plain Markdown and safe to copy verbatim.)

4. Let Cursor install the widget

In Cursor chat, prompt:

> install Earshot in this app

Cursor reads the skill, detects your framework (Next.js / Remix / SvelteKit / Vue / Nuxt / vanilla), drops the snippet into your <head>, wires Earshot.identify() into your auth callback, and adds the pk_* to your .env.local. Wall-clock target: under 5 minutes.

The widget bundle itself is served from https://cdn.earshotbot.com/v1/earshot.iife.js — no build step on your side.

5. Use Earshot from Cursor

After install, ask Cursor anything that mentions feedback:

  • "What's in the inbox?" → calls list_feedback.
  • "Show me feedback fb_abc123" → calls get_feedback.
  • "Mark fb_abc123 resolved — fixed in PR #4421" → calls resolve_feedback.
  • "Tell Earshot about this codebase" → calls set_project_context after summarizing the repo.

Full tool reference: MCP.

Limits

  • The pk_* key is project-scoped. Tools that need a user identity (create_team, create_project, rotate_api_key, list_projects) require OAuth, which is in progress. Use the dashboard for those operations today.
  • Cursor must support HTTP MCP transport with bearer-auth headers (any recent Cursor version does).
  • If Cursor surfaces 401 from MCP calls, the pk_* is wrong or has been rotated. Pull the current key from Project Settings and reload MCP servers.