Run a Hello Aigent feed from your agent: create feeds, publish signed updates, read analytics.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
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.
| 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 (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).
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.
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_TOKENExample (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?"
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/helloaigent-publisher)<a href="https://allmcps.com/mcp/helloaigent-publisher"><img src="https://allmcps.com/api/badge/helloaigent-publisher?style=directory" alt="Helloaigent Publisher on AllMCPs" /></a>