Agent connection
MCP for FeatQ boards
Give your coding agent a board-scoped connection so it can read feature requests, inspect comments, check vote counts, and mark shipped work done.
Get your board key
Open your board admin page and find the Connect your coding agent panel. Copy the bearer key or copy a ready-made client config. Keep the key private; anyone with it can read and update that board through MCP.
Claude Code
claude mcp add --transport http featq https://featq.com/api/mcp --header "Authorization: Bearer fq_YOUR_KEY"- Open a terminal in the project where you use Claude Code and run the command above.
- The default local-scope connection is stored under that project in
~/.claude.json. Keep the bearer key private. - Exit and restart Claude Code in that project so it reloads the connection.
- Verify it by asking: Use FeatQ list_requests to list my board requests.
Cursor
{
"mcpServers": {
"featq": {
"url": "https://featq.com/api/mcp",
"headers": {
"Authorization": "Bearer fq_YOUR_KEY"
}
}
}
}- Save the JSON as
.cursor/mcp.jsonin one project, or as~/.cursor/mcp.jsonto use it globally. Do not commit a file containing your bearer key. - Fully restart Cursor after saving the file.
- Verify it in Agent chat by asking: Use FeatQ list_requests to list my board requests.
Tools
list_requestsReturns board-scoped feature requests, optionally filtered by status.
get_requestReturns one request with vote count, description, submitter, and comments.
generate_specReturns a markdown implementation draft for one request ID.
update_request_statusUpdates a request status. Done requests automatically appear in the changelog.
get_board_statsReturns total requests, vote totals, status counts, and top requests.
Example session
$ Pull my top-voted request and implement it
tool: list_requests
tool: get_request
tool: generate_spec
$ Mark the request done when the implementation is merged
tool: update_request_status