Suggix
Connect Claude, ChatGPT, Cursor, Codex, or any MCP-compatible client to Suggix. Search feedback, manage feature requests, update your roadmap, and publish changelogs with natural language.
Hosted MCP Server
npx add-mcp 'https://mcp.suggix.com/mcp'Installs into Claude Code, Codex, Cursor and more
Documentation
Suggix MCP Overview
Connect your AI client to Suggix feedback, roadmap, changelog, and workspace data through MCP.
Suggix MCP connects supported AI clients to the feedback data in one Suggix workspace. After connecting, your AI client can use Suggix context while helping your team review feedback, plan roadmap work, summarize changelogs, and understand users.
Before you start
You need:
- A Suggix workspace.
- Permission to manage workspace developer settings.
- An AI client that supports remote HTTP MCP servers.
Create an MCP API key
Open Developer Settings, then find the MCP API Keys section.
- Select Create Key.
- Enter a recognizable name for the client or environment, such as
Claude Code - DevelopmentorCursor - Production. - Copy the generated API key and store it in a password manager or environment variable.
- Add the key to your AI client's MCP configuration.
Warning
The raw MCP API key is shown only once. Treat it like a password: do not commit it to source control, paste it into prompts, or share it in screenshots.
Connect to the MCP server
Suggix provides a remote HTTP MCP endpoint:
https://mcp.suggix.com/mcp
Authenticate every request with your workspace MCP API key:
Authorization: Bearer sgx_mcp_...
Each API key is bound to one workspace. Create separate keys for different AI clients, team members, or environments so you can revoke access independently when needed.
Available Suggix context
The first MCP release provides access to:
- Feedback posts
- Roadmap, which is the feedback view grouped by post status
- Changelog entries
- Users
- Workspace context, including read-only workspace settings, boards, statuses, and tags
- Read-only comments for a feedback post
Votes are not available through MCP in this release.
Manage keys safely
Developer Settings lists the name, creation time, and last-used time for each MCP API key. Delete a key immediately if it is no longer needed or may have been exposed. Revocation takes effect immediately.
Tip
Use a distinct key for each client. A descriptive key name makes it much easier to identify and revoke the correct connection later.