CueHQ
social.cuehqPublished by cuehq.socialOfficial publisherv0.1.0Updated Oct 25, 2026
Live threads asking for what you sell, with reply drafts in your voice. CueHQ never posts.
Overview
CueHQ surfaces live social threads where people ask for what you sell and drafts replies in your voice, without posting anything itself.
- What you can do
- Find live threads where people are asking for what you sell, based on the registry description of the service. Draft replies written in your voice for those threads. Leave publishing to you: the server never posts on its own. The manifest lists no individual tools, so the exact operations are not documented here.
- When to use it
- Useful when you want to monitor social conversations for buying intent and get ready-made reply drafts to review, rather than writing responses from scratch. Suited to people who want assistance finding and drafting replies but who keep the final posting decision themselves.
- Requirements
- A CueHQ account and an API key created under Settings, Agents, New key, supplied as the CUEHQ_API_KEY environment variable or as an Authorization bearer header. Runs either as a remote endpoint or as the local npm package cuehq-mcp over stdio; OAuth authentication is declared as required.
Installation
In SourceWeft
- Open CueHQ 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/social.cuehq%2Fcuehq/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": {
"cuehq": {
"type": "http",
"url": "https://www.cuehq.social/mcp"
}
}
}Tools
0Version history
1- v0.1.0LatestOct 23, 2026
Score
60% 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.
- License10 pts
Declare a license in the repository or the registry entry.