
Helloaigent Publisher
io.github.helloaigent-devPublished by GitHub account helloaigent-devv0.1.1Updated Nov 3, 2026
Run a Hello Aigent feed from your agent: create feeds, publish signed updates, read analytics.
Overview
Lets an assistant create and manage Hello Aigent publisher feeds, publish signed updates to subscribers, and read audience analytics.
- What you can do
- Create and list feeds, including minting an Ed25519 keypair, publisher token and discovery file
- Publish signed updates that are delivered to subscribers, and report action outcomes
- Read analytics: KPI overview, subscribed-to-returned-to-acted funnel, and a filterable event log
- List the consent-aware subscriber audience and generate the discovery file to host at a well-known path
- When to use it
- For publishers or marketers who run an owned agent audience on Hello Aigent and want to create feeds, push updates and check subscriber engagement by talking to their assistant instead of using a console or CLI.
- Requirements
- Runs locally via npx from the npm package @helloaigent-dev/publisher on a desktop MCP client. Needs a Hello Aigent account and a workspace API key (hak_...) in HELLOAIGENT_API_KEY, or an admin token in HELLOAIGENT_ADMIN_TOKEN; a feed publish token can be set in HELLOAIGENT_TOKEN. HELLOAIGENT_API optionally overrides the API base URL. Network access to the Hello Aigent API.
Installation
In SourceWeft
- Open Helloaigent Publisher in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
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
"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 (defaulthttps://api.helloaigent.dev)HELLOAIGENT_API_KEY— your workspace API key (hak_...); required for feed management + analytics unless using the admin token. Preferred overHELLOAIGENT_ADMIN_TOKENwhen both are set.HELLOAIGENT_ADMIN_TOKEN— admin token; alternative toHELLOAIGENT_API_KEY(ops/dogfood use only)HELLOAIGENT_TOKEN— publish token (a feed's own publisher token); falls back toHELLOAIGENT_API_KEY, thenHELLOAIGENT_ADMIN_TOKEN
Example (Claude Desktop / any MCP client) — the common case, a self-serve workspace key:
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?"
Source: README.md at commit 8c944dd
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts