HerculeRadar for AI agents

Connect an agent

Built for agents: one endpoint, streamable HTTP, 51 tools. They call the same functions the dashboard does, so an agent can do what a human can — and nothing more. Prefer OAuth when the client supports it; otherwise the bearer token is a project API key from Developer.

ChatGPT

In ChatGPT, add a custom connector / MCP server (the menu name depends on the workspace). Paste the URL and send the key as a bearer token. If your plan does not expose MCP connectors yet, use Claude, Cursor or Codex with the same endpoint — we do not invent a ChatGPT-only path.

URL   https://herculeradar.com/mcp
Auth  Authorization: Bearer hr_live_…

Claude

Claude Desktop and Claude Code both read an MCP config. Drop this in, restart, and ask it to triage the inbox.

{
  "mcpServers": {
    "herculeradar": {
      "url": "https://herculeradar.com/mcp",
      "headers": {
        "Authorization": "Bearer hr_live_…"
      }
    }
  }
}

Codex

OpenAI Codex speaks MCP over the same streamable HTTP endpoint. Point it at https://herculeradar.com/mcp with the bearer key. The JSON block above is the shape most Codex / MCP configs expect.

{
  "mcpServers": {
    "herculeradar": {
      "url": "https://herculeradar.com/mcp",
      "headers": {
        "Authorization": "Bearer hr_live_…"
      }
    }
  }
}

Cursor

Add the server to .cursor/mcp.json in the project, or to your user MCP config, then reload MCP.

{
  "mcpServers": {
    "herculeradar": {
      "url": "https://herculeradar.com/mcp",
      "headers": {
        "Authorization": "Bearer hr_live_…"
      }
    }
  }
}

Try it without a client

curl -X POST "https://herculeradar.com/mcp" \
  -H "Authorization: Bearer hr_live_…" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Clients that prefer an authorisation flow can use the OAuth 2.1 discovery documents under /.well-known/.

What agents actually ask

  • “Show me every complaint about Acme from the last 24 hours.”
  • “Start monitoring Triple Whale as a competitor.”
  • “Mark the three highest-urgency mentions as reviewed.”

Prompts

A tool catalog tells a model what it can do. These tell it what is worth doing.

  • triage_inbox

    Review everything new and hand back a short, prioritised list of what to act on.

  • weekly_digest

    A short written summary of the week, suitable for pasting into a team channel.

  • set_up_monitoring

    Set up monitoring for a brand from scratch, including competitors.

  • find_leads

    Find people publicly asking for what this product does.

  • wake_on_mention

    How to wire a webhook so an agent only wakes when a mention is filed.

Tools

  • list_projects

    List the projects this credential can reach. Start here when you do not know the project id.

  • create_project

    Create a workspace for a brand. Only needed once per brand you monitor.

  • list_monitors

    List what is currently being watched: keywords, aliases, sources and whether each monitor is active.

  • create_monitor

    Start watching a brand, product or competitor. Include every spelling people actually use — the domain and the @handle as well as the name — because matching is literal. Optional query_mode (any/all/phrase), watch_accounts, feed_urls and review_urls.

  • update_monitor

    Change a monitor’s keywords, sources or active state. Only the fields you pass change.

  • delete_monitor

    Stops a monitor (soft-delete: active=false). Mentions stay linked for analytics. Prefer update_monitor with active:false if the user may want it back.

  • list_mentions

    The main read tool. Returns collected posts newest first, already classified. Call with no arguments for the latest, or filter by category, sentiment, urgency, source, intent, speaker or a named time window. Exact From filters use author_handle / author_name / author_url. Page with the returned nextCursor.

  • get_mention

    Fetch one mention in full, with its AI classification and a link to the original post.

  • update_mention_status

    Move a mention through triage. Use done once it has been handled and ignored when it is not really about the brand.

  • get_mention_analytics

    Counts for a window — totals, relevance rate, how many need attention, and breakdowns by category, sentiment and source. Use this to answer "how are we doing" without paging the whole feed.

  • list_alerts

    List alert rules — what triggers a notification and where it is sent.

  • create_alert

    Notify an email address or https webhook when a matching mention arrives. Empty filter arrays mean "any".

  • delete_alert

    Permanently remove an alert rule. Notifications stop immediately.

  • get_usage

    Plan and mentions used against the quota. Check before creating monitors if the user is near their limit.

  • get_project

    One project: name, plan, quota and public-dashboard flags.

  • update_project

    Rename a project or change its website / description.

  • delete_project

    Archive the project and pause every monitor. Mentions and usage stay. Before calling: explain the consequences, ask the user to confirm this specific project, then pass confirmation_name (exact current name) and confirm_deletion:true. Never infer consent from knowing the name.

  • get_public_dashboard

    Whether the read-only public page is on, and its URL if it is.

  • set_public_dashboard

    Publish or unpublish the public mentions page. Unpublishing keeps the slug.

  • get_account

    The authenticated owner and every project this credential can see.

  • update_account

    Update the owner display name on the profile.

  • list_project_members

    Seats on this project: members and pending invites. The owner is not in the list.

  • invite_project_member

    Invite someone by email as viewer or editor. Returns the invite URL.

  • update_project_member

    Change a member between viewer and editor.

  • remove_project_member

    Remove a member from the project. Invites are not this tool.

  • list_keywords

    Flattened keyword list across monitors. Prefer this when the user talks in keywords, not monitors.

  • create_keyword

    Add a term to an existing monitor, or start a new monitor if monitor_id is omitted. Mentions already collected stay.

  • update_keyword

    Rename is not supported; change the monitor keyword list via update_monitor.

  • delete_keyword

    Stop tracking one term. The last term on a monitor soft-stops it; collected mentions keep their monitor_id.

  • list_keyword_groups

    Own-brand vs competitor piles. Used for share of voice.

  • create_keyword_group

    Add a labelled pile. is_own=true counts it as the brand in share of voice.

  • update_keyword_group

    Rename a group or flip is_own.

  • delete_keyword_group

    Drop the label. Keywords filed under it become ungrouped; mentions stay.

  • mark_mention_irrelevant

    The keyword match was coincidental. Sets is_relevant=false and status=ignored so analytics stop counting it as about you.

  • search_mention_authors

    Distinct authors in this project, optionally filtered by handle or name.

  • list_categories

    Filing labels the classifier uses. Custom wording, same five enums.

  • create_category

    Categories are a closed set. Use this to enable and label one of the five enums.

  • update_category

    Change the label, description or enabled flag for a filing category.

  • delete_category

    Disable a category. Existing mentions keep the enum; new ones will not be filed as it.

  • list_mention_views

    Saved filter sets from the feed.

  • create_mention_view

    Save the current filter object under a name. Same shape as the mentions query string.

  • update_mention_view

    Rename a view or replace its filters.

  • delete_mention_view

    Delete a saved view. The mentions it pointed at are unaffected.

  • update_alert

    Change an alert rule. Only the fields you pass change.

  • list_webhooks

    Outbound endpoints. Secrets are never returned after create.

  • create_webhook

    Subscribe a public HTTPS URL. mention.created fires when a classified mention is relevant — that is the loop an agent should listen to.

  • update_webhook

    Change URL, events or pause an endpoint.

  • delete_webhook

    Stop sending events to this URL.

  • test_webhook

    Send webhook.test with a ping payload so the receiver can verify signatures.

  • list_webhook_deliveries

    Recent delivery log. Use replay_webhook_delivery on a failed row.

  • replay_webhook_delivery

    POST the original payload again. Does not invent a new mention.