> ## Documentation Index
> Fetch the complete documentation index at: https://help.suggix.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 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](https://www.suggix.com/_/settings/developer), then find the **MCP API Keys** section.

<img src="https://mintcdn.com/suggix/wDmAk6xCKDvNW9jH/images/mcp_apikey.png?fit=max&auto=format&n=wDmAk6xCKDvNW9jH&q=85&s=084c380ca3b0646b8e41240d3ffd8e1b" alt="MCP API key settings" width="1134" height="596" data-path="images/mcp_apikey.png" />

1. Select **Create Key**.
2. Enter a recognizable name for the client or environment, such as `Claude Code - Development` or `Cursor - Production`.
3. Copy the generated API key and store it in a password manager or environment variable.
4. 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.
</Warning>

## Connect to the MCP server

Suggix provides a remote HTTP MCP endpoint:

```text theme={null}
https://mcp.suggix.com/mcp
```

Authenticate every request with your workspace MCP API key:

```text theme={null}
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.
</Tip>

## Configure your AI client

<CardGroup cols={2}>
  <Card title="Claude Code" icon="terminal" href="/mcp/claude-code">
    Connect Suggix to Claude Code with a project or user MCP configuration.
  </Card>

  <Card title="Codex" icon="bot" href="/mcp/codex">
    Add Suggix to your Codex configuration file.
  </Card>

  <Card title="Antigravity" icon="sparkles" href="/mcp/antigravity">
    Configure a remote MCP server in Antigravity.
  </Card>

  <Card title="GitHub Copilot" icon="github" href="/mcp/github-copilot">
    Use Suggix tools in GitHub Copilot Chat for VS Code.
  </Card>

  <Card title="Cursor" icon="mouse-pointer" href="/mcp/cursor">
    Add Suggix to Cursor globally or for a specific project.
  </Card>
</CardGroup>