Helloaigent Publisher

What the helloaigent-publisher MCP server does

The helloaigent-publisher MCP server lets an agent operate the publisher side of a Hello Aigent feed. It can create feeds, publish updates, report whether recipients acted, and inspect audience and engagement data. The publisher is the producer-side counterpart to the Hello Aigent subscriber package, which is used to subscribe, fetch, and act.

Feed creation returns a discovery file, an Ed25519 keypair, and a publisher token. Published updates are built and signed by the server before delivery to subscribers. Analytics tools cover headline metrics, subscription and return behavior, action outcomes, recent activity, and an attributed event history.

How it works

The MCP process communicates with the Hello Aigent API. Each operation uses credentials supplied through the MCP client's environment. A workspace API key beginning with hak_ scopes feed creation, feed listing, publishing, event reporting, analytics, and subscriber access to the workspace's own feeds. An admin token can access every feed and is intended for operations use.

A feed-specific publisher token can be used for publishing and event reporting. The discovery-file tool is public and generates hello-aigent.json, intended for hosting at /.well-known/. The subscriber list is consent-aware, and the event log supports filtering and attribution.

Setup and configuration

Install the package through an MCP client using the package command shown below:

{
  "mcpServers": {
    "hello-aigent-publisher": {
      "command": "npx",
      "args": ["-y", "@helloaigent-dev/publisher"],
      "env": { "HELLOAIGENT_API_KEY": "hak_…" }
    }
  }
}

Supported environment variables are:

• HELLOAIGENT_API: API base URL; defaults to https://api.helloaigent.dev.
• HELLOAIGENT_API_KEY: workspace API key. It is preferred when both a workspace key and admin token are configured.
• HELLOAIGENT_ADMIN_TOKEN: alternative unrestricted administrative credential.
• HELLOAIGENT_TOKEN: feed publisher token. It falls back to the workspace key, then the admin token.

Create a workspace API key in the Hello Aigent console under Settings and API keys. The workspace key is not equivalent to an admin credential and cannot manage API keys.

Tools and capabilities

The helloaigent-publisher MCP server provides these operations:

• Create a feed and receive its discovery file and signing credentials.
• List feeds owned by the current workspace.
• Publish server-signed updates to subscribers.
• Record action outcomes as the acted analytics signal.
• Retrieve KPI tiles, a fetch sparkline, and recent activity.
• Inspect the subscribed-to-returned-to-acted funnel.
• Query a filterable, attributed event log.
• List the workspace's consent-aware subscribers.
• Generate the public discovery file.

Limitations and notes

Workspace credentials only expose feeds owned by that workspace. They cannot create, list, or revoke API keys; those actions require access to the Hello Aigent console. Admin tokens are separate, unrestricted operations credentials and are not issued through self-serve signup. Publishing and event reporting require access to a feed through a publish token, workspace key, or admin token, while most management and analytics tools require a workspace key or admin token.