Feedback MCP Server

Customer feedback intelligence MCP — synthesize GitHub Issues, HN, and App Store reviews into ranked pain clusters. Pay-per-call via x402

Remote serverstreamable-http

What is the Feedback MCP server?

Most developer tooling work still happens through a UI a human drives. Feedback MCP server moves it into the conversation instead. Customer feedback intelligence MCP — synthesize GitHub Issues, HN, and App Store reviews into ranked pain clusters. Pay-per-call via x402 micropayments.

The short version

Stop reading through hundreds of feedback items manually. Feedback Synthesis MCP collects from multiple sources, runs a multi-pass LLM pipeline, and returns ranked pain clusters with impact scores, evidence links, and suggested actions — machine-readable for agents, human-readable for founders.

The tools it exposes

The server publishes 4 tools. What each one is for:

  • synthesize_feedback — Multi-source synthesis → ranked pain clusters with evidence
  • get_pain_points — Quick single-source pain point extraction
  • search_feedback — Full-text search across cached feedback items
  • get_sentiment_trends — Time-series sentiment across sources

What it needs from you

Configuration is passed through the environment: EVM_PRIVATE_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Feedback's toolset — synthesize_feedback, get_pain_points, search_feedback and 1 more — is a fair guide to whether it matches your workflow. It is maintained by Cortex Labs; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
synthesize_feedbackMulti-source synthesis → ranked pain clusters with evidence
get_pain_pointsQuick single-source pain point extraction
search_feedbackFull-text search across cached feedback items
get_sentiment_trendsTime-series sentiment across sources

How to install the Feedback MCP server

{
  "mcpServers": {
    "feedback-synthesis-mcp": {
      "type": "streamable-http",
      "url": "https://feedback-synthesis-mcp-production.up.railway.app/mcp/"
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
EVM_PRIVATE_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Feedback to synthesize feedback.
  • Use Feedback to get pain points.
  • Use Feedback to search feedback.

Frequently asked questions

It connects Feedback to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (synthesize_feedback, get_pain_points, search_feedback, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Feedback directly.