What the MCP connection does
Huddlekit runs an MCP (Model Context Protocol) server, so an AI coding tool can read the feedback in your workspace and act on it without you copying anything across. A typical use is pointing Claude Code at a project's open comments and letting it work through them — it can read the comment text, the element that was clicked, the page, the thread, and the screenshot, then reply, retag, reassign, or mark the comment resolved as it goes.
Connecting requires a Pro or Team plan. The setup page is visible on every plan so you can see what is involved before deciding.
Connect a client
Open MCP in your workspace sidebar. The server address is:
https://mcp.huddlekit.com/mcp
There is no API key to create or paste — the client authenticates you through your normal Huddlekit sign-in, and you choose the workspace and the access level on the approval screen.
Claude Code
Run this in your terminal, then type /mcp in Claude Code and pick huddlekit:
claude mcp add --transport http huddlekit https://mcp.huddlekit.com/mcp
Claude
Go to Settings → Connectors → Add custom connector, paste the server address, and approve access.
Cursor
Add this to ~/.cursor/mcp.json, or to .cursor/mcp.json for a single project, then reload Cursor and approve access:
{
"mcpServers": {
"huddlekit": {
"url": "https://mcp.huddlekit.com/mcp"
}
}
}
Other clients
Any client that speaks MCP over streamable HTTP with OAuth will work. Most accept either the server address or the configuration above, and discover the sign-in automatically.
What a connected tool can do
Reading — list the projects in the workspace, list comments with their status, priority, tags and assignees, and open a single comment with its full context: the element, the page URL, the device details, the reply thread, and the screenshot.
Writing — change a comment's status, post a reply, set tags, and assign people. Write access is granted separately from reading, and a reply posted this way appears under your own name and notifies people exactly as a reply typed in the app would.
A connection is scoped to one workspace. Connect again to work with another one.
Managing access
Connections are per person: each teammate connects their own client, sees only their own connections on the MCP page, and reaches only what their own Huddlekit account can reach. Each one is listed as either Read only or Read & write.
- Grant write or Make read-only — change what an already-connected tool can do. The change applies immediately, on the connection's next request.
- Revoke — disconnect a client entirely.
Removing write access and revoking a connection are always available, including on the Free plan, so you can always switch a tool off.
If your workspace moves to the Free plan, existing connections stop working until you upgrade again. Nothing is deleted.
Good to know
Guests and share links are unaffected. MCP is a workspace-member feature and exposes nothing through a share link.
