~/.grok/config.toml or .grok/config.toml
Grok CLI manages MCP servers in ~/.grok/config.toml (or .grok/config.toml per project). Add FeedbackJar as an HTTP MCP server and triage your feedback backlog from the Grok TUI.
# Workspace key: fj_live_...
# Export it so Grok can expand ${FEEDBACKJAR_API_KEY}:
export FEEDBACKJAR_API_KEY="fj_live_..." → Grok expands ${VAR} in url, headers, and env at load time — keep secrets out of config.toml.
grok mcp add --transport http feedbackjar \
https://api.feedbackjar.com/mcp \
--header "Authorization: Bearer ${FEEDBACKJAR_API_KEY}" → Add --scope project to write .grok/config.toml in the current repo instead of ~/.grok/config.toml.
[mcp_servers.feedbackjar]
url = "https://api.feedbackjar.com/mcp"
bearer_token_env_var = "FEEDBACKJAR_API_KEY"
enabled = true
# Or with explicit headers:
# [mcp_servers.feedbackjar]
# url = "https://api.feedbackjar.com/mcp"
# headers = { Authorization = "Bearer ${FEEDBACKJAR_API_KEY}" } → Edit ~/.grok/config.toml, or create .grok/config.toml in the project for team-shared MCP config.
grok mcp list
grok mcp doctor feedbackjar
# In the Grok TUI, open /mcps to toggle servers.
# Then ask: "What are the top open bugs in FeedbackJar?" → grok inspect shows every loaded MCP server and where it came from (config.toml, Cursor, or Claude compat).
Users report bugs through your widget. Your agent reads the top votes via MCP, ships the fix, and every voter gets notified.