CueHQ for agents
Your cues, in your agent. Connect once, then ask it to find who is asking for what you sell, draft the reply in your voice, and log what you posted. Nothing is posted for you and no account is connected.
- Sign in. Where the client supports it, you sign in with your CueHQ account and allow the agent. Nothing to copy.
- An API key. Everywhere else, make a key in Settings → Agents and send it as
Authorization: Bearer cuehq_sk_…. A key acts as you, so keep it out of shared files.
Claude Code
claude mcp add --transport http cuehq --scope user https://www.cuehq.social/mcp claude mcp add --transport http cuehq --scope user https://www.cuehq.social/mcp \
--header "Authorization: Bearer cuehq_sk_…" Claude (web and desktop)
Go to Customize, then Connectors. Select + Add, then Add custom connector.
Name it CueHQ and enter https://www.cuehq.social/mcp, then Continue.
Under Authentication, pick Sign in now and sign in with your CueHQ account.
Or with an API key: pick No sign in, and under Request headers add Authorization with the value Bearer cuehq_sk_…
On Team and Enterprise plans an owner adds the connector in Organization settings, and everyone shares a request header, so use sign in there.
Codex CLI
codex mcp add cuehq --url https://www.cuehq.social/mcp
codex mcp login cuehq [mcp_servers.cuehq]
url = "https://www.cuehq.social/mcp"
bearer_token_env_var = "CUEHQ_API_KEY" Then set CUEHQ_API_KEY to your key in the shell you run Codex from.
Cursor
{
"mcpServers": {
"cuehq": {
"url": "https://www.cuehq.social/mcp"
}
}
} {
"mcpServers": {
"cuehq": {
"url": "https://www.cuehq.social/mcp",
"headers": {
"Authorization": "Bearer ${env:CUEHQ_API_KEY}"
}
}
}
} Add to Cursor Then replace YOUR_KEY with your key in Cursor's MCP settings.
The command behind that link, cuehq-mcp, is on npm and in the MCP registry.
Gemini CLI
gemini mcp add --scope user --transport http cuehq https://www.cuehq.social/mcp gemini mcp add --scope user --transport http \
--header "Authorization: Bearer cuehq_sk_…" \
cuehq https://www.cuehq.social/mcp Grok
On grok.com: go to grok.com/connectors, select New connector, then Custom, and enter https://www.cuehq.social/mcp. Grok asks you to sign in.
grok mcp add --transport http cuehq https://www.cuehq.social/mcp [mcp_servers.cuehq]
url = "https://www.cuehq.social/mcp"
headers = { "Authorization" = "Bearer ${CUEHQ_API_KEY}" } Muse Code
{
"schema_version": 1,
"mcp_servers": {
"cuehq": {
"transport": "streamable_http",
"url": "https://www.cuehq.social/mcp"
}
}
} {
"schema_version": 1,
"mcp_servers": {
"cuehq": {
"transport": "streamable_http",
"url": "https://www.cuehq.social/mcp",
"headers": { "Authorization": "Bearer cuehq_sk_…" }
}
}
} ChatGPT
On the web, go to chatgpt.com/plugins, select the plus button, then Add custom MCP server.
Name it CueHQ, enter https://www.cuehq.social/mcp as the server URL, and choose OAuth for authentication.
Accept the risk note, create it, then sign in with your CueHQ account.
Any client
Point it at https://www.cuehq.social/mcp (Streamable HTTP). A client that supports MCP sign in finds it on its own. If yours does not, send your key on every request:
Authorization: Bearer cuehq_sk_… What it can do
-
brandsYour brands and their plan -
list_cuesYour cues, by tab: all, priority, mentions, competitors -
get_cueOne cue with its top replies and drafts -
draft_replyDrafts in your voice -
mark_repliedLog what you posted, so we can track how it grows -
skip_cueSkip a cue -
weekly_reportThis week, next to last week