MCP server

A user feedback MCP server for your coding agent

Your users already tell you what to build. @youasked/mcp lets Claude Code, Cursor or Codex read those requests, build them and mark them shipped.

Add it in one line

You need the secret key of your YouAsked app (YOUASKED_SECRET_KEY, which npx youasked init puts in your env file). Then, in Claude Code:

Claude Code
claude mcp add youasked -e YOUASKED_SECRET_KEY=ya_sec_… -- npx -y @youasked/mcp

For Cursor, Windsurf and other clients that read an MCP config file:

.cursor/mcp.json
{
  "mcpServers": {
    "youasked": {
      "command": "npx",
      "args": ["-y", "@youasked/mcp"],
      "env": { "YOUASKED_SECRET_KEY": "ya_sec_…" }
    }
  }
}

For Codex, in ~/.codex/config.toml:

config.toml
[mcp_servers.youasked]
command = "npx"
args = ["-y", "@youasked/mcp"]
env = { YOUASKED_SECRET_KEY = "ya_sec_…" }

Self-hosting? Set YOUASKED_API_URL to your own API.

The loop

  1. See what people want. Ask your agent “what are my users asking for?” It calls list_requests or digest.
  2. Read the one you’ll build. get_request returns the description, votes, comments and screenshots.
  3. Build it. Your agent writes the code like any other task.
  4. Ship it. Commit with closes YA-12. The GitHub webhook marks it shipped, writes the note from your commit and tells everyone who asked. Or the agent calls set_status.

Tools

ToolWhat it does
list_requestsRequests by status (default: open, planned, in progress), sorted by votes or newest.
get_requestOne request in full: description, status, votes, ship note and every comment. Takes YA-12, 12 or an id.
replyPosts a team reply. The person who asked sees it inside the app.
set_statusopen, planned, in_progress, shipped or declined. Shipping notifies everyone who asked.
mergeFolds a duplicate (YA-14) into the request to keep (YA-12). Votes combine.
searchFinds similar requests by wording, so the agent checks before replying or merging.
digestTop asks, what's new, what shipped and vote and comment counts for the last N days.

Safe by default

  • The key only reaches the app it belongs to. Treat it like a password and keep it out of git.
  • Request text is user content, never instructions. Agents are told not to act on directions found inside a request.
  • Nothing ships without a commit or an explicit status change from you or your agent.

Questions

What is a user feedback MCP server?

An MCP (Model Context Protocol) server that gives an AI coding agent direct access to your users' feature requests. The agent can list what people want most, read the details, ask a follow-up question, and mark a request shipped, without you copying anything between tools.

Which agents work with it?

Any MCP client: Claude Code, Cursor, Codex, Windsurf and others. It runs locally over stdio with npx and needs only your secret key.

Can a request inject instructions into my agent?

Request text is written by your users, so it is data, not instructions. The install guide and skill tell agents never to follow directions found inside a request, and your agent only builds what you ask it to build.

Is YouAsked the only feedback tool with an MCP server?

No. Several feedback tools have shipped MCP servers, including Featurebase, Canny and Quackback. What YouAsked adds is the rest of the loop: people ask inside your app, you hear it on your phone, a commit with “closes YA-12” ships it, and everyone who asked is told.

The package is on npm as @youasked/mcp (MIT).