Connect FeatQ to Grok
Grok is xAI’s assistant, and how it connects to FeatQ depends on which Grok client you use. There is no first-party MCP support we can point you at across the board: some community Grok CLIs speak MCP (the Model Context Protocol, the standard coding agents use to call FeatQ tools), and the xAI API supports function calling. The path that works everywhere is simplest: pull your ranked spec from the FeatQ API and paste it into Grok.
Setup: paste a spec, or wire up tools
Universal route: run this and paste the output into any Grok conversation. It returns a build-ready spec for your current top-ranked request. Get your fq_ key from your board admin page under Agent access.
curl -H "Authorization: Bearer fq_YOUR_KEY" https://featq.com/api/v1/top-specBuilding on the xAI API? Grok supports function calling, so you can define functions that call the FeatQ v1 endpoints (top-requests and top-spec) with your Bearer key and let Grok decide when to fetch board data.
If your Grok client supports MCP servers (some community CLIs do; check yours), point it at the FeatQ server with this config.
{
"mcpServers": {
"featq": {
"url": "https://featq.com/api/mcp",
"headers": {
"Authorization": "Bearer fq_YOUR_KEY"
}
}
}
}What it looks like in practice
The paste-a-spec route looks like this:
You: [paste the FeatQ spec for "Team invites", your top request with 29 votes and 7 comments] Review this spec and plan the implementation. Grok: The spec asks for email invites with role selection, a pending-invite list, and the expiry behavior raised in the comments. Suggested order: data model, invite endpoint, then UI. Want the code for the endpoint first? You: Yes. Grok: [writes the invite endpoint] Here is the handler with token generation and the 7-day expiry from the acceptance criteria. You: [ship it, then mark "Team invites" done on FeatQ. FeatQ updates your changelog and emails the 29 voters.]
One quirk to know
Grok clients vary a lot: the web and mobile apps, the xAI API, and community CLIs all have different tool support. Before assuming MCP works, check your specific client’s docs. The curl-and-paste route above works in every one of them, so start there.
Frequently asked questions
Practical answers about agents, voting, embeds, and pricing.
It depends on the client. Some community Grok CLIs support MCP servers and work with the FeatQ config above. We do not claim native first-party MCP support; verify what your client offers.
Define functions that hit the FeatQ v1 endpoints (top-requests for the ranked list, top-spec for a build-ready spec) with your Bearer key. Grok then pulls board data when your prompt calls for it.
By votes plus half-weight comments, with the score fading as requests age. The top-spec endpoint always returns a spec for the current leader.
It is more manual but the output is the same spec. MCP saves you the copy-paste and lets the agent update request statuses; the spec content does not change.
Still have questions? Contact us