@helloaigent-dev/publisher
An MCP server for operating a Hello Aigent publisher feed, from feed creation through signed publishing and audience analytics.
Create a feed and mint an Ed25519 signing keypair plus a one-time publisher token, returning a discovery file.
List feeds you own with IDs, titles, topics, latest sequence, and discovery URLs.
Publish server-signed updates (
offer,announcement,restock,content) with summaries, Markdown bodies, structured data, and callable actions.Report action outcomes to power the “acted” analytics signal.
View feed overview KPIs, fetch sparkline, recent activity, subscribed→returned→acted funnel, filterable event log, and consent-aware subscriber list.
Generate the public
hello-aigent.jsondiscovery file for hosting at/.well-known/.Per schema auth: admin token required for feed management and analytics; publisher token or admin token for publishing/reporting; discovery file is public.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@helloaigent-dev/publisher Create a feed for my newsletter and publish a signed update"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@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
Tool | Auth | What it does |
| workspace key or admin | Mint a feed + Ed25519 keypair + publisher token; returns the discovery file |
| workspace key or admin | List feeds you own |
| publish token, workspace key, or admin | Build + server-sign an update; delivered to subscribers |
| publish token, workspace key, or admin | Report an action outcome (the "acted" analytics signal) |
| workspace key or admin | KPI tiles, fetch sparkline, recent activity |
| workspace key or admin | subscribed → returned → acted funnel |
| workspace key or admin | Filterable, attributed audit log |
| workspace key or admin | The owned-audience list (consent-aware) |
| public | Generated |
"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.
Related MCP server: Paragraph MCP
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:
{
"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?"
Available Tools
9 toolshello_aigent_create_feedA
Create a Hello Aigent feed (a stream agents subscribe to). Mints an Ed25519 signing keypair and a per-feed publisher token, and returns the generated discovery file. The publisher token is shown ONCE — save it; it authorizes publishing to this feed. Requires the admin token.
Inputs: title (required), description (required), publisher_name (required), publisher_site (required), +2 more.
hello_aigent_discovery_fileA
Get the generated discovery file (hello-aigent.json) for a feed — host it at your site's /.well-known/hello-aigent.json so agents can find and subscribe. Public; no token needed.
Inputs: feed (required).
hello_aigent_event_logA
Filterable audit of feed events (subscribe/fetch/action/unsubscribe), newest first, agent-attributed. Requires the admin token.
Inputs: feed (required), type, limit.
hello_aigent_funnelA
The subscribed → returned → acted cohort funnel for a feed over a window, with return-rate and act-rate. Requires the admin token.
Inputs: feed (required), window.
hello_aigent_list_feedsA
List the feeds you own (id, title, topics, latest_seq, discovery URL). Requires the admin token.
Inputs: no named parameters.
hello_aigent_overviewA
Overview for a feed: subscribers, fetches today, 7-day return rate, signed-update count, a fetch sparkline, and recent agent-attributed activity. Requires the admin token.
Inputs: feed (required).
hello_aigent_publishA
Publish a signed update to a feed. The server Ed25519-signs the envelope; subscribed agents verify it before acting. Uses the feed's publisher token (or the admin token). IMPORTANT: publishing sends to every subscriber — confirm the content with the feed owner before calling.
Inputs: feed (required), type (required), title (required), summary (required), +3 more.
hello_aigent_report_eventA
Report an action outcome for a subscription — the "acted" signal that powers the analytics funnel. Call this after a subscriber's agent completes one of your callable actions. Uses the feed's publisher token (or the admin token).
Inputs: feed (required), action_name (required), subscription_id (required), update_id.
hello_aigent_subscribersB
The feed's subscriber list — the audience you own: agent, principal, topics, consent scope, last fetch, and status (active/dormant/revoked). Requires the admin token.
Inputs: feed (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
Each tool targets a distinct resource or action: feed creation, listing, publishing, event reporting, subscriber data, event log, analytics overview, funnel, and discovery file. There is no overlap or ambiguity between them.
All tools share the hello_aigent_ prefix, which provides strong consistency. However, the second part mixes noun-only names (event_log, subscribers, overview, funnel, discovery_file) with verb_verb_noun patterns (create_feed, list_feeds, report_event), making the convention slightly inconsistent.
Nine tools is well within the ideal 3-15 range and each tool serves a clear, non-redundant purpose for a feed management and analytics domain. The count feels appropriate and not bloated.
The tool set covers the core lifecycle of a feed: creation, publishing, event reporting, and analytics (overview, funnel, subscribers, event log). Minor gaps exist such as feed deletion or metadata update, but these are not critical to the primary publisher workflow.
Maintenance
Related MCP Connectors
A hosted MCP server for planning, scheduling, media, analytics, and social publishing.
MCP server for mandates, delegation, policy-gated execution, credential grants, and audit.
MCP server for Ably — channel history, presence, occupancy, stats, publish, and app management.
MCP server for building and testing AI agents with multi-model experimentation and insights.
Related MCP Servers
- AlicenseAqualityCmaintenanceLocal-first MCP server for per-agent key management, generating and using signing keys without external KMS.812 npm1MIT

Paragraph MCPofficial
AlicenseNot gradedqualityFmaintenanceMCP server that connects AI agents to your Paragraph publication, enabling post management, subscriber analytics, and search across posts and publications.1MIT- AlicenseNot gradedqualityCmaintenanceMCP server for the FreeFeed social network API. Enables reading timelines, posts, comments, and attachments, as well as writing posts, comments, and managing subscriptions.1MIT
- AlicenseAqualityCmaintenanceAn MCP server for managing and querying RSS/news feeds, enabling real-time fetching, searching, and retrieval of feed items.511 npm1MIT