Helloaigent Publisher

io.github.helloaigent-dev由 GitHub 账号 helloaigent-dev 发布v0.1.1更新于 Nov 3, 2026

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

已验证STDIO仅桌面数据与分析商业与电商

概览

AI 生成的概览

让助手创建和管理 Hello Aigent 发布者 feed、向订阅者发布签名更新,并查看受众分析数据。

可以做什么
  • 创建和列出 feed,包括生成 Ed25519 密钥对、发布者令牌和发现文件
  • 发布签名更新并投递给订阅者,以及上报操作结果
  • 查看分析数据:KPI 概览、从订阅到回访再到行动的漏斗,以及可筛选的事件日志
  • 列出遵循同意机制的订阅者名单,并生成可托管在 well-known 路径下的发现文件
适用场景
适合在 Hello Aigent 上运营自有智能体受众的发布者或营销人员,希望通过对话让助手创建 feed、推送更新并查看订阅者互动情况,而无需使用控制台或命令行。
运行要求
通过 npx 从 npm 包 @helloaigent-dev/publisher 在桌面 MCP 客户端本地运行。需要 Hello Aigent 账号,并在 HELLOAIGENT_API_KEY 中提供工作区 API 密钥(hak_...),或在 HELLOAIGENT_ADMIN_TOKEN 中提供管理员令牌;可在 HELLOAIGENT_TOKEN 中设置 feed 的发布令牌。HELLOAIGENT_API 可覆盖 API 基础地址。需要访问 Hello Aigent API 的网络。
安装前请注意
需要机密凭据:HELLOAIGENT_API_KEY、HELLOAIGENT_ADMIN_TOKEN 或 HELLOAIGENT_TOKEN。管理员令牌不受限制,可操作所有 feed 而非仅自己的,建议优先使用工作区密钥。发布会向真实订阅者推送更新,上报事件会写入分析数据。创建 feed 会返回私有的 Ed25519 密钥对和发布者令牌,应妥善保管。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Helloaigent Publisher,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

@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:

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

来源:README.md,提交 8c944dd

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v0.1.1最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分