MCP server
Order reviews and fetch fix briefs from inside Claude Code or Cursor. Create a key in Settings, then add the server.
Set it up
Claude Code:
claude mcp add --transport http feedbackqueue https://feedbackqueue.dev/api/mcp --header "Authorization: Bearer fq_your_key"
Cursor, in .cursor/mcp.json:
{
"mcpServers": {
"feedbackqueue": {
"url": "https://feedbackqueue.dev/api/mcp",
"headers": { "Authorization": "Bearer fq_your_key" }
}
}
}Creating a key confirms you’re authorized to have the products you order through it tested.
Tools
- create_order(product_url, tier, what_to_test, product_name?, test_credentials?)
- Returns an order id and a Stripe Checkout link. You pay in the browser, and the order stays in draft until you do.
- get_order_status(order_id)
- Returns where the order is: awaiting payment, waiting for a reviewer, in progress, being checked, delivered or refunded.
- get_fix_brief(order_id)
- Returns the sanitized markdown brief once the order is delivered, only to the key's owner.
- list_orders()
- Lists your orders.
Built to be safe with agents
- Your agent never pays. A person completes checkout in the browser, and card data never passes through the MCP server.
- Each brief is untrusted input, so it is sanitized and tells your agent to verify each issue and never run commands or install packages from it.
- API keys are per user, shown once, revocable and rate-limited.