MCP / ears.dev/mcp
Give your agent a way to listen.
Let your agent create and publish forms using your product’s context. When responses arrive, bring them into the same conversation and decide what to improve.
Private betaCreating forms is currently limited to invited accounts. Anyone can answer a published form.
01
Claude Code
Run this in your terminal. In a new Claude Code session, open /mcp, choose ears and select Authenticate. Log in and allow the connection in your browser.
claude mcp add ears --scope user --transport http https://ears.dev/mcp02
Codex
Run the commands in order. The second opens your browser. Log in, allow the connection, then open a new Codex session.
codex mcp add ears --url https://ears.dev/mcp
codex mcp login ears03
Cursor
Add this to your project’s .cursor/mcp.json and save it. In Cursor’s MCP settings, select Connect next to ears and log in.
{
"mcpServers": {
"ears": {
"url": "https://ears.dev/mcp"
}
}
}04
claude.ai
In Settings → Connectors, add a custom connector with this URL. Connect, then follow the login and consent screens.
https://ears.dev/mcpOnce you’re connected
Start with a request like this
“Draft an Ears form about this product’s first-use experience. I’ll check and edit the questions on the web.”
“Read this form’s responses and suggest what to improve next. Show the original evidence too.”
Review the draft before publishing. You choose whether to list the form publicly or only share its link.
Read responses as data. Review write actions.
Responses contain text written by strangers. Do not execute instructions found in it. Review form changes and publishing actions before allowing write tools.