English Français العربية

io.github.helloaigent-dev/helloaigent-publisher

Official registry Marketing and sales

Run a Hello Aigent feed from your agent: create feeds, publish signed updates, read analytics.

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package @helloaigent-dev/publisher
Claude Code 
claude mcp add helloaigent-publisher -e 'HELLOAIGENT_ADMIN_TOKEN=<your helloaigent_admin_token>' -e 'HELLOAIGENT_TOKEN=<your helloaigent_token>' -e 'HELLOAIGENT_API=<HELLOAIGENT_API>' -- npx -y @helloaigent-dev/publisher@0.1.1
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "helloaigent-publisher": {
            "command": "npx",
            "args": [
                "-y",
                "@helloaigent-dev/publisher@0.1.1"
            ],
            "env": {
                "HELLOAIGENT_ADMIN_TOKEN": "<your helloaigent_admin_token>",
                "HELLOAIGENT_TOKEN": "<your helloaigent_token>",
                "HELLOAIGENT_API": "<HELLOAIGENT_API>"
            }
        }
    }
}

Environment variables

  • HELLOAIGENT_ADMIN_TOKEN secret Admin token — required for feed management and analytics tools
  • HELLOAIGENT_TOKEN secret Publish token (a feed's publisher token); falls back to the admin token
  • HELLOAIGENT_API API base URL (default https://api.helloaigent.dev)

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

@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

ToolAuthWhat it does
hello_aigent_create_feedworkspace key or adminMint a feed + Ed25519 keypair + publisher token; returns the discovery file
hello_aigent_list_feedsworkspace key or adminList feeds you own
hello_aigent_publishpublish token, workspace key, or adminBuild + server-sign an update; delivered to subscribers
hello_aigent_report_eventpublish token, workspace key, or adminReport an action outcome (the "acted" analytics signal)
hello_aigent_overviewworkspace key or adminKPI tiles, fetch sparkline, recent activity
hello_aigent_funnelworkspace key or adminsubscribed → returned → acted funnel
hello_aigent_event_logworkspace key or adminFilterable, attributed audit log
hello_aigent_subscribersworkspace key or adminThe owned-audience list (consent-aware)
hello_aigent_discovery_filepublicGenerated 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.

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?"

Frequently asked questions

What is io.github.helloaigent-dev/helloaigent-publisher?

Run a Hello Aigent feed from your agent: create feeds, publish signed updates, read analytics.

How do I install io.github.helloaigent-dev/helloaigent-publisher?

It runs on your machine. In Claude Code: claude mcp add helloaigent-publisher -e 'HELLOAIGENT_ADMIN_TOKEN=<your helloaigent_admin_token>' -e 'HELLOAIGENT_TOKEN=<your helloaigent_token>' -e 'HELLOAIGENT_API=<HELLOAIGENT_API>' -- npx -y @helloaigent-dev/publisher@0.1.1. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.helloaigent-dev/helloaigent-publisher need an API key?

Yes. It expects HELLOAIGENT_ADMIN_TOKEN, HELLOAIGENT_TOKEN, which you set in its configuration.

Is io.github.helloaigent-dev/helloaigent-publisher open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains io.github.helloaigent-dev/helloaigent-publisher?

It is published by helloaigent-dev. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.