{
  "markdown": "# @helloaigent-dev/publisher\n\nHello 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`](https://www.npmjs.com/package/@helloaigent-dev/subscriber) (which lets an agent subscribe/fetch/act).\n\nA marketer operates their owned agent audience by telling their agent — no CLI, console, or developer.\n\n## Tools\n\n| Tool | Auth | What it does |\n|---|---|---|\n| `hello_aigent_create_feed` | workspace key or admin | Mint a feed + Ed25519 keypair + publisher token; returns the discovery file |\n| `hello_aigent_list_feeds` | workspace key or admin | List feeds you own |\n| `hello_aigent_publish` | publish token, workspace key, or admin | Build + server-sign an update; delivered to subscribers |\n| `hello_aigent_report_event` | publish token, workspace key, or admin | Report an action outcome (the \"acted\" analytics signal) |\n| `hello_aigent_overview` | workspace key or admin | KPI tiles, fetch sparkline, recent activity |\n| `hello_aigent_funnel` | workspace key or admin | subscribed → returned → acted funnel |\n| `hello_aigent_event_log` | workspace key or admin | Filterable, attributed audit log |\n| `hello_aigent_subscribers` | workspace key or admin | The owned-audience list (consent-aware) |\n| `hello_aigent_discovery_file` | public | Generated `hello-aigent.json` to host at `/.well-known/` |\n\n\"workspace key\" means a `hak_...` **workspace API key** — mint one from the Hello Aigent console (Settings → 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).\n\nThe **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.\n\n## Configure\n\nSet in your MCP client config (env vars):\n\n- `HELLOAIGENT_API` — API base (default `https://api.helloaigent.dev`)\n- `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.**\n- `HELLOAIGENT_ADMIN_TOKEN` — admin token; alternative to `HELLOAIGENT_API_KEY` (ops/dogfood use only)\n- `HELLOAIGENT_TOKEN` — publish token (a feed's own publisher token); falls back to `HELLOAIGENT_API_KEY`, then `HELLOAIGENT_ADMIN_TOKEN`\n\nExample (Claude Desktop / any MCP client) — the common case, a self-serve workspace key:\n\n```json\n{\n  \"mcpServers\": {\n    \"hello-aigent-publisher\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@helloaigent-dev/publisher\"],\n      \"env\": { \"HELLOAIGENT_API_KEY\": \"hak_…\" }\n    }\n  }\n}\n```\n\nThen 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?\"*\n",
  "bytes": 3191,
  "sha": "44d2b5d4a01bdcb7ac86cc9328286c3b9efbc98d67e370ae4b0a27b373a8a68b",
  "repo_slug": "helloaigent-dev/helloaigent-publisher",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_helloaigent_dev_helloaigent_pu_ce8c9fd2/readme"
}