Skip to main content
Glama

@helloaigent-dev/publisher

Hello Aigent publisher MCP — an MCP server that lets an agent run a publisher's feed: create feeds, publish signed updates, and read analytics. The producer-side counterpart to @helloaigent-dev/subscriber (which lets an agent subscribe/fetch/act).

A marketer operates their owned agent audience by telling their agent — no CLI, console, or developer.

Tools

Tool

Auth

What it does

hello_aigent_create_feed

workspace key or admin

Mint a feed + Ed25519 keypair + publisher token; returns the discovery file

hello_aigent_list_feeds

workspace key or admin

List feeds you own

hello_aigent_publish

publish token, workspace key, or admin

Build + server-sign an update; delivered to subscribers

hello_aigent_report_event

publish token, workspace key, or admin

Report an action outcome (the "acted" analytics signal)

hello_aigent_overview

workspace key or admin

KPI tiles, fetch sparkline, recent activity

hello_aigent_funnel

workspace key or admin

subscribed → returned → acted funnel

hello_aigent_event_log

workspace key or admin

Filterable, attributed audit log

hello_aigent_subscribers

workspace key or admin

The owned-audience list (consent-aware)

hello_aigent_discovery_file

public

Generated hello-aigent.json to host at /.well-known/

"workspace key" means a hak_... workspace API key — mint one from the Hello Aigent console (Feeds → Give your agent access, or System → API keys) once you've signed up. It scopes every tool above to your own workspace: create_feed creates in your workspace, list_feeds/analytics/subscribers only ever see feeds your workspace owns, and publish/report_event only work on feeds your workspace owns. It is not admin-equivalent — it cannot create, list, or revoke API keys (that requires signing in to the console itself).

The admin token is a separate, unrestricted, ops-only credential (not something a self-serve signup ever receives) — it still works everywhere a workspace key does, for every feed, not just your own.

Related MCP server: Paragraph MCP

Configure

Set in your MCP client config (env vars):

  • HELLOAIGENT_API — API base (default https://api.helloaigent.dev)

  • HELLOAIGENT_API_KEY — your workspace API key (hak_...); required for feed management + analytics unless using the admin token. Preferred over HELLOAIGENT_ADMIN_TOKEN when both are set.

  • HELLOAIGENT_ADMIN_TOKEN — admin token; alternative to HELLOAIGENT_API_KEY (ops/dogfood use only)

  • HELLOAIGENT_TOKEN — publish token (a feed's own publisher token); falls back to HELLOAIGENT_API_KEY, then HELLOAIGENT_ADMIN_TOKEN

Example (Claude Desktop / any MCP client) — the common case, a self-serve workspace key:

{
  "mcpServers": {
    "hello-aigent-publisher": {
      "command": "npx",
      "args": ["-y", "@helloaigent-dev/publisher"],
      "env": { "HELLOAIGENT_API_KEY": "hak_…" }
    }
  }
}

Then just ask your agent: "Create a feed for my coffee shop and publish a restock update," or "How many agents subscribed this week, and what's the return rate?"

Available Tools

9 tools
hello_aigent_create_feedA

Create a Hello Aigent feed (a stream agents subscribe to). Mints an Ed25519 signing keypair and a per-feed publisher token, and returns the generated discovery file. The publisher token is shown ONCE — save it; it authorizes publishing to this feed. Requires the admin token.

Inputs: title (required), description (required), publisher_name (required), publisher_site (required), +2 more.

hello_aigent_discovery_fileA

Get the generated discovery file (hello-aigent.json) for a feed — host it at your site's /.well-known/hello-aigent.json so agents can find and subscribe. Public; no token needed.

Inputs: feed (required).

hello_aigent_event_logA

Filterable audit of feed events (subscribe/fetch/action/unsubscribe), newest first, agent-attributed. Requires the admin token.

Inputs: feed (required), type, limit.

hello_aigent_funnelA

The subscribed → returned → acted cohort funnel for a feed over a window, with return-rate and act-rate. Requires the admin token.

Inputs: feed (required), window.

hello_aigent_list_feedsA

List the feeds you own (id, title, topics, latest_seq, discovery URL). Requires the admin token.

Inputs: no named parameters.

hello_aigent_overviewA

Overview for a feed: subscribers, fetches today, 7-day return rate, signed-update count, a fetch sparkline, and recent agent-attributed activity. Requires the admin token.

Inputs: feed (required).

hello_aigent_publishA

Publish a signed update to a feed. The server Ed25519-signs the envelope; subscribed agents verify it before acting. Uses the feed's publisher token (or the admin token). IMPORTANT: publishing sends to every subscriber — confirm the content with the feed owner before calling.

Inputs: feed (required), type (required), title (required), summary (required), +3 more.

hello_aigent_report_eventA

Report an action outcome for a subscription — the "acted" signal that powers the analytics funnel. Call this after a subscriber's agent completes one of your callable actions. Uses the feed's publisher token (or the admin token).

Inputs: feed (required), action_name (required), subscription_id (required), update_id.

hello_aigent_subscribersB

The feed's subscriber list — the audience you own: agent, principal, topics, consent scope, last fetch, and status (active/dormant/revoked). Requires the admin token.

Inputs: feed (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: feed creation, listing, publishing, event reporting, subscriber data, event log, analytics overview, funnel, and discovery file. There is no overlap or ambiguity between them.

    Naming Consistency4/5

    All tools share the hello_aigent_ prefix, which provides strong consistency. However, the second part mixes noun-only names (event_log, subscribers, overview, funnel, discovery_file) with verb_verb_noun patterns (create_feed, list_feeds, report_event), making the convention slightly inconsistent.

    Tool Count5/5

    Nine tools is well within the ideal 3-15 range and each tool serves a clear, non-redundant purpose for a feed management and analytics domain. The count feels appropriate and not bloated.

    Completeness4/5

    The tool set covers the core lifecycle of a feed: creation, publishing, event reporting, and analytics (overview, funnel, subscribers, event log). Minor gaps exist such as feed deletion or metadata update, but these are not critical to the primary publisher workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      F
      maintenance
      MCP server that connects AI agents to your Paragraph publication, enabling post management, subscriber analytics, and search across posts and publications.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for the FreeFeed social network API. Enables reading timelines, posts, comments, and attachments, as well as writing posts, comments, and managing subscriptions.
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      An MCP server for managing and querying RSS/news feeds, enabling real-time fetching, searching, and retrieval of feed items.
      5
      11 npm
      1
      MIT