Allows an AI agent to manage publisher feeds, publish signed updates, and access audience analytics.
Also known as helloaigent-dev/helloaigent-publisher, @helloaigent-dev/publisher
- Stars
- 0
- Tools
- 9
- Downloads, 30 days
- —
- Latest version
- 0.1.1
- Last commit
- Oct 22, 2026
- License
- MIT
What is helloaigent-publisher MCP?
helloaigent-publisher allows an AI agent to manage publisher feeds, publish signed updates, and access audience analytics. It exposes 9 tools, such as hello_aigent_create_feed, hello_aigent_list_feeds, hello_aigent_publish.
Summary generated from the project's README
About helloaigent-publisher MCP server
Managing publisher feeds and audience analytics through an AI agent is what this server enables for marketers. Instead of using a command line or a developer console, users can direct an agent to handle the entire lifecycle of a feed, from initial creation to publishing signed updates. This tool acts as the producer-side counterpart to the subscriber MCP, allowing for a complete loop of content delivery and performance tracking.
To use this server, you must configure your MCP client with a workspace API key starting with hak_ or an admin token. The server uses these credentials to scope all actions to your specific workspace, ensuring you only manage feeds and view analytics that you own. It provides specific tools like hello_aigent_create_feed for minting new feeds with Ed25519 keypairs and hello_aigent_publish for delivering signed updates to subscribers. You can also monitor performance through tools like hello_aigent_funnel and hello_aigent_overview to track subscriber conversion rates and recent activity.
What you can do with it
- 1Create and launch new feedsAsk your agent to set up a new feed and generate the necessary security keys and discovery files.
- 2Distribute signed content updatesInstruct an AI to build and send a signed update to all current subscribers.
- 3Analyze audience conversion metricsRequest a report on how many users move from subscribing to actually acting on your updates.
- 4Audit audience engagement and logsHave your agent retrieve a filtered list of events to see how users are interacting with your feed.
Written from the project's README. Every use case is checked against a quote from it.
How to install helloaigent-publisher MCP
Formats verified 10 Nov 2026Install helloaigent-publisher MCP in Claude Code
$ claude mcp add --env HELLOAIGENT_ADMIN_TOKEN=<YOUR_HELLOAIGENT_ADMIN_TOKEN> --env HELLOAIGENT_TOKEN=<YOUR_HELLOAIGENT_TOKEN> helloaigent-publisher -- npx -y @helloaigent-dev/publisherInstall helloaigent-publisher MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"helloaigent-publisher": {
"command": "npx",
"args": [
"-y",
"@helloaigent-dev/publisher"
],
"env": {
"HELLOAIGENT_ADMIN_TOKEN": "<YOUR_HELLOAIGENT_ADMIN_TOKEN>",
"HELLOAIGENT_TOKEN": "<YOUR_HELLOAIGENT_TOKEN>"
}
}
}
}Install helloaigent-publisher MCP in VS Code
.vscode/mcp.json
{
"servers": {
"helloaigent-publisher": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@helloaigent-dev/publisher"
],
"env": {
"HELLOAIGENT_ADMIN_TOKEN": "<YOUR_HELLOAIGENT_ADMIN_TOKEN>",
"HELLOAIGENT_TOKEN": "<YOUR_HELLOAIGENT_TOKEN>"
}
}
}
}Install helloaigent-publisher MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"helloaigent-publisher": {
"command": "npx",
"args": [
"-y",
"@helloaigent-dev/publisher"
],
"env": {
"HELLOAIGENT_ADMIN_TOKEN": "<YOUR_HELLOAIGENT_ADMIN_TOKEN>",
"HELLOAIGENT_TOKEN": "<YOUR_HELLOAIGENT_TOKEN>"
}
}
}
}Install helloaigent-publisher MCP in Codex
~/.codex/config.toml
[mcp_servers.helloaigent-publisher] command = "npx" args = ["-y", "@helloaigent-dev/publisher"] [mcp_servers.helloaigent-publisher.env] HELLOAIGENT_ADMIN_TOKEN = "<YOUR_HELLOAIGENT_ADMIN_TOKEN>" HELLOAIGENT_TOKEN = "<YOUR_HELLOAIGENT_TOKEN>"
Install helloaigent-publisher MCP in Gemini CLI
~/.gemini/settings.json
{
"mcpServers": {
"helloaigent-publisher": {
"command": "npx",
"args": [
"-y",
"@helloaigent-dev/publisher"
],
"env": {
"HELLOAIGENT_ADMIN_TOKEN": "<YOUR_HELLOAIGENT_ADMIN_TOKEN>",
"HELLOAIGENT_TOKEN": "<YOUR_HELLOAIGENT_TOKEN>"
}
}
}
}helloaigent-publisher MCP tools 9
Detected from the READMEhello_aigent_create_feedhello_aigent_list_feedshello_aigent_publishhello_aigent_report_eventhello_aigent_overviewhello_aigent_funnelhello_aigent_event_loghello_aigent_subscribershello_aigent_discovery_file
| hello_aigent_create_feed | — | |
| hello_aigent_list_feeds | — | |
| hello_aigent_publish | — | |
| hello_aigent_report_event | — | |
| hello_aigent_overview | — | |
| hello_aigent_funnel | — | |
| hello_aigent_event_log | — | |
| hello_aigent_subscribers | — | |
| hello_aigent_discovery_file | — |
Configuration
HELLOAIGENT_ADMIN_TOKENSecretAdmin token — required for feed management and analytics tools
HELLOAIGENT_TOKENSecretPublish token (a feed's publisher token); falls back to the admin token
HELLOAIGENT_APIAPI base URL (default https://api.helloaigent.dev)
HELLOAIGENT_API_KEY
| Name | Description | |
|---|---|---|
| HELLOAIGENT_ADMIN_TOKEN | Admin token — required for feed management and analytics tools | Secret |
| HELLOAIGENT_TOKEN | Publish token (a feed's publisher token); falls back to the admin token | Secret |
| HELLOAIGENT_API | API base URL (default https://api.helloaigent.dev) | |
| HELLOAIGENT_API_KEY | — |
Automated checks
Ran Nov 13, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSNot checked
- Destructive tools are labelledPass
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHub@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 |
|---|---|---|
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 (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:
{
"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?"
helloaigent-publisher MCP questions
How do I add helloaigent-publisher MCP to Claude Code?
Run claude mcp add --env HELLOAIGENT_ADMIN_TOKEN=<YOUR_HELLOAIGENT_ADMIN_TOKEN> --env HELLOAIGENT_TOKEN=<YOUR_HELLOAIGENT_TOKEN> helloaigent-publisher -- npx -y @helloaigent-dev/publisher in your terminal. Add --scope user to make it available in every project.
How do I add helloaigent-publisher MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does helloaigent-publisher MCP provide?
It exposes 9 tools, including hello_aigent_create_feed, hello_aigent_list_feeds, hello_aigent_publish, hello_aigent_report_event, hello_aigent_overview.
How do I create a new feed?
You can use the hello_aigent_create_feed tool, which requires a workspace key or admin token to mint a feed, an Ed25519 keypair, and a publisher token.
What is a workspace key?
A workspace key is a 'hak_...' API key minted from the Hello Aigent console that scopes tools to your specific workspace.
Can a workspace key be used to manage other people's feeds?
No, a workspace key only allows you to see and manage feeds that your own workspace owns.