Connect FeatQ to Windsurf
Windsurf supports MCP natively through its Cascade agent. MCP (Model Context Protocol) is an open standard that lets an AI agent call tools on an external server, in this case your FeatQ board. Once connected, Cascade can pull your top-voted requests and build from a generated spec.
Setup: one JSON snippet
Add this to your Windsurf MCP config file (mcp_config.json, reachable from the MCP settings in Windsurf). Replace fq_YOUR_KEY with the key from your board admin page under Agent access.
{
"mcpServers": {
"featq": {
"url": "https://featq.com/api/mcp",
"headers": {
"Authorization": "Bearer fq_YOUR_KEY"
}
}
}
}Refresh the MCP servers list in Windsurf so the featq server loads, then ask Cascade about your board.
What it looks like in practice
A typical session with Cascade looks like this:
You: What are users asking for on my FeatQ board? Cascade: [calls list_requests] 18 active requests. Want them ranked by demand? You: Yes, and spec the winner. Cascade: [calls get_ranked_requests] Top: "Keyboard shortcuts" (22 votes, 15 comments). [calls generate_spec] Spec ready: shortcut map, conflict handling, and the discoverability concerns raised in the comments. Shall I implement it? You: Go. Cascade: Done. Marked it in progress on the board via update_request_status.
One quirk to know
Windsurf reads mcp_config.json at startup. After editing the file, use the refresh button in the MCP panel (or restart Windsurf) or the featq server will not appear.
Frequently asked questions
Practical answers about agents, voting, embeds, and pricing.
MCP support is a Windsurf feature, so check your Windsurf plan. FeatQ itself does not care which client connects; any MCP client with the key can use the board.
Read requests, votes, comments, and stats; generate specs; and update request statuses. It cannot delete requests or change board settings.
Votes plus half-weight comments, fading as requests age. So it surfaces what many users want right now, not what was popular six months ago.
The key only grants access to that one board and can be rotated from the admin page. Keep the config file out of shared repositories all the same.
Still have questions? Contact us