Huddlekit
com.huddlekitPublished by huddlekit.comOfficial publisherv1.0.0Updated Oct 24, 2026
Read client feedback left on your website, with its screenshot and page, then reply and resolve.
Overview
Lets an assistant read client feedback submitted on your website, including its screenshot and page, and reply to or resolve it.
- What you can do
- Huddlekit connects an assistant to client feedback left on your website. According to the registry description, the assistant can read each item together with its screenshot and the page it came from, then reply to the feedback and mark it resolved. No individual tools are listed in the manifest, so the exact operations are not documented here.
- When to use it
- Useful when feedback from a website is handled in Huddlekit and you want an assistant to triage, answer, or close items without switching to the web app. It fits teams that already collect client feedback through Huddlekit and want replies and resolutions handled in the same conversation as other work.
- Requirements
- A remote MCP endpoint at mcp.huddlekit.com over streamable HTTP; nothing is installed locally. Authentication is OAuth and is required, so a Huddlekit account with access to the relevant feedback is needed. No environment variables or headers are declared.
Installation
In SourceWeft
- Open Huddlekit in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.huddlekit%2Fhuddlekit/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"huddlekit": {
"type": "http",
"url": "https://mcp.huddlekit.com/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestSep 28, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.